Agile Coaching, Good Question!

NOT done!

One of the principles behind the Agile Manifesto is maximizing the amount of work NOT done! If you really manage to do it, it is very liberating. It actually sounds very easy but is really hard to get it started and keep it going.

tasks-not-done

In meetings I again and again find myself trapped in the role of a project manager: Collect as many assigned ToDos as possible, be happy if you leave the meeting with a long list of ToDos and if you have produced MORE work (mostly for others…).

Thinking a lot about the Agile Manifesto and the Lean Disciplines I started to measure the success of a planning or status meeting in a different way now:

  • How many cards with User Stories or tasks have been ripped into pieces at the end of the meeting?
  • How many items of the backlog have been deleted (b/c “not relevant anymore”, “nice to have and will never have time for that”, “what was this about anyway”)?
  • How many minutes could we end the meeting earlier by stopping useless discussions and meanigless monologues?
  • How many tasks or tickets that have not been changed in your issue tracking system since 60 days (or longer) can we delete? (If the task or ticket is really important it will pop up again via a new task or ticket anyway.)
  • How many tasks or tickets of your team that are not completly clear have we bounced to the person responsible (most probably your product owner or project manager)?

This list is to be continued…

Advertisements