Skip to main content

Be or Be Not; there is no Do in Agile

Why do we practice this thing we call Agile?  Is it for the results it provides? 

I've been working with companies and people that use the "A" word in many different ways.  Sometime the word is used as if it were a method of working.
"We are doing Agile on this project, but the team has 34% story carry over each iteration."
Sometimes it is used as a bludgeon to beat someone not behaving as one would like them to behave.
Sales:  "I'd like you to work on this severity one bug, it just came in and the customer while not really blocked is considering a purchase of our SuperWidget and if you just sneak this in today they will be really happy."  
Team Member:  "Sorry, talk to the PO we have sprint commitments." 
Sales:  "Well, that's not very Agile!"  
While at other times it is a promised land, a utopia of project management where we all live in harmony.  Many times it is used as a technique to achieve some other purpose, a differentiator that will achieve some other objective.  Objectives such as speed to market, doubling revenue in five years, raising quality while lowering cost, there are many other business objectives for "installing the agile".

I am not surprise when department managers say their groups are doing Agile.  I typically bit my tongue and run through this test in my head.

  • Show me your teams interacting with each other, the customers, and product owner more than they are working with the tools, process, etc.  
  • Individuals and interactions over processes and tools
  • Great you must have working software, show me your last iteration demo on the staging server, now.  
  • Working software over comprehensive documentation
  • Which one of these people is the customer?  
  • Customer collaboration over contract negotiation
  • What feed back did the customer give in the last month or two that cause you to deliver higher value than initially planned?  
  • Responding to change over following a plan

Is there just one process way to do these things?  No.  There are thousands of ways to do these things.

Those things are the definition of Agile.  Agile is not a method, it is a way of being.  It is a synergy of many things we do, and many things we do not do.  It is in the decision we make and it is mostly in the underlying reasons - why - we make those decisions.

One could do Scrum or XP, those are processes (or frameworks or techniques) - but one cannot do Agile.  However, one could be Agile.  Agility is a path, either you are on it, or off it - there is no Agile destination.


Yoda teaching young Skywalker "Do or do not, there is no try."

But why should one attempt to be Agile?  Answering this question is getting to the core purpose.  It is not about all the outcomes that might result in a group or organization being Agile.  If being Agile is the goal, then we are surely going to disappoint someone.  Perhaps ourselves, perhaps our customers. Customers don't want us to responded to their change request - they want products that met their discovered needs (true needs) with the ability to sustain the continual deliver of meeting their needs in the future.

Simon Sinek TED Talk: How great leaders inspire action

I think we must be Agile for our selves.  Then align our values of being Agile within the context of the purpose of the organization we choose to work with.  If this alignment is too difficult, the friction too high, options exist.  Explore those options.

An agile enterprise is one that has achieved a level of operational excellence that enables it to make changes at the same pace that it discovers a need for them. -- Tim Snyder

Tim explains with great clarity why Agile is a proper goal for an organization (not all companies - but some).  Agile is a slightly unique type of goal - a system-optimizing goal.



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…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

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, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …