Skip to main content

Have you written a Manifesto lately?

What is it lately - everyone wants to get into the Manifesto authorship racket.  When I was growing up - only commies and the unibomber wrote manifestos.

Well after taking a stroll through the internet, there are quite a few nice manifestos out there.  Here are a few that I subscribe to...

The Agile Manifesto - four comparative value statements and 12 principles for how to build better software.  With an industry failure rate of 72% boy do we need a manifesto!

The ScrumMaster Manifesto - because this is a group of people that are downtrodden every day.  Sitting in a seat for 2 days straight without nodding off is no bais for a system of government - to paraphrase Dennis - come see the violence inherent in the system.


The Manifesto for Software Craftsmanship - because we need the bar raised.

The Mother [bleep] ing Manifesto for Programming Mother [bleep] ers - because sometime a four letter word says more than a well crafted phrase.

The MoreAgile Manifesto... because incremental improvement beats the alternative.

The Holstee Manifesto - because it is my life - and I will do what I love.


The Gangplank Manifesto, creating community changing culture, walk the plank.

The Cult of Done Manifesto - enough said.

Having a motivation problem?  The BootStart Manifesto might help you - but you must fall in love with your problem (not the solutions).

The After the Agile Manifesto, Stop Writing Any More. Please. A really long list of manifesto, and a plea to stop it already.  Oh!  Maybe I should end it here.

And now the PMO has a Manifesto (don't you just hear the resonance).

What would happen if a Manifesto were written as a scientific experiment - starting with a null hypothesis? Bob Marshall's Agile H0.


--------------

Well I haven't updated this Manifesto page in a number of months... haven't found anything worth the trouble until today (Feb 1, 2017) a day that may change my carrer journey... Agile Transition Guide may get a rev. version number soon. Thanks to the Manifesto for Agile Company Development by Agile 102: (reprinted below). Credit for this wonderful work goes to: Matt the Agile Coach on twitter @MattAgileCoach.

Manifesto for Agile Company Development

We are discovering new ways of transforming corporate processes, activities and structures by helping companies take better advantage of Agile software development techniques. Throughout this journey we have recognised it is better to:
  • Create streams of business value rather than end-to-end projects.
  • Structure organisations for pace rather than for complexity.
  • Model and experiment rather than describe and document.
  • Create processes to empower people rather than to constrain them.
  • Promote cross-functional collaboration rather than singular accountability.
  • Discover and prioritise customer needs rather than deliver internal vision.
We recognise that all of these may not be entirely achievable within the constraints of some industries; however promoting the positive values from within each one will enable more agility in any organisation.


I just saw this today and it instantly resonates with me as that thing that many people have desired - What comes next after Agile? I've decide that a journey is the prize, not some destination. However this manifesto might set the goal for many of us that are not working on our "own" companies... but trying to help with another's company.

Now had I been invited to the chalet to collaborate on the manifesto - I'd like to polish the word "company" into a broader term "organization". To include groups that are not-for-profit and weirdos that might find they fit within the realm of "The People's Scrum" by Tobias Mayer.

----

Nov, 2017 a colleague sent me this manifesto:
I, David Jayakaran, am uncovering ways to cut through the crap of religiosity and get to the purpose for all of creation including human existence. Through this journey I have come to value: 
          Relationship with Jesus over reason or logic
          Heart transformation over behavior modification
          Truth/reality over facts
          Life experience over ideology, philosophy or belief system 
That is, while there may be value in the items on the right, I value the items on the left much more.
Having interacted with David for a few months - he's expressively living his manifesto. RESPECT.


2 comments

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Team Performance Model - by Drexler and Sibbet

Many of you have all heard of the Tuckman model of team dynamics (Forming, Storming, Norming, Performing).  It was created in 1966 and has become the most popular model for describing team behavior.  Is it time to level up in your mental model of team dynamics?  Are you ready for a richer more functional model?



Introducing the Team Performance Model by Drexler and Sibbet



Orientation - Why am I here?
"Orientation is about understanding the purpose of a team and assessing what it will mean to be a member.  you need to understand the reason the team exist, what will be expected of you and how you will benefit from membership.  In a new team, these are individual concerns, because the group is only potentially a team.  that is why these concerns are illustrated as occurring in your imagination at an intuitive level.  As a team leader it is important to provide time and space for people to answer these internal questions themselves."

Keys to when Orientation challenges are resolve…