Agile FAQs
  About   Slides   Home  

 
Managed Chaos
Naresh Jain's Random Thoughts on Software Development and Adventure Sports
     
`
 
RSS Feed

Recent Thoughts
Tags
Recent Comments

Introducing Churn

How to destroy a team by introducing various forms of churn?

  • Have the Product Management change high-level vision and priority frequently.
  • Stop the teams from collaborating with other teams, Architects and important stakeholders.
  • Make sure testing and integration is done late in the cycle.
  • As soon as a team member gains enough experience on the team move him/her out of the team to play other roles.
  • In critical areas of the system, force the team to produce a poor implementation.
  • Structure the teams architecturally to ensure there is heavy inter-dependencies between them.
  • Very closely monitor team’s commitment and ensure they feel embarrassed for estimating wrongly.
  • Ensure the first 15-30 mins of every meeting is spent on useless talk, before getting to the crux of the matter.
  • Measure Churn and put clear process in place to minimize churn ;)
  • http://profiles.google.com/davearonson Dave Aronson

    Great post as usual, but I’ve noticed something over your last couple posts.  The use of an alternate color plus underlining, to highlight a word or phrase, makes it look as though it might be a link.  I suggest you use bold or italic instead of underlines.

    • http://blogs.agilefaqs.com Naresh Jain

      Good point. Thanks for your advice. Appreciate it.


    Licensed under
Creative Commons License