22 November 2009

Planning versus Experience

Here is a thought; Suppose the more experience you have with a particular knowledge domain, the less you need to plan the work?

I picked this planning versus experience concept up from a Jim Coplien piece on InfoQ a few months ago. The idea was basically this; If you have 20 years experience doing roughly the same work you should acknowledge that the 20 years means you have a lot of your plan pre thought through before you even turn up.

In the piece I was watching (it was a video) the argument was being used to discuss the degreeof planning for "Agile" projects.  How much is too much planning and how much is not enough? The answer lies in the experience of the team.
  • Have they worked in this domain before?
  • Have they worked together before?
  • How much and how well?
  • etc
So if I follow this logic I start to see that highly experienced teams and people need to spend less time on planning.  In fact, if the are investing months into pre-project planning they are perhaps wasting money.

At the inexperienced end of the spectrum the idea is almost reversed, but not quite.  Yes you do need to spend more time planning, but not too much because, frankly, your inexperience means you'll make heaps of planning errors.  Instead go for short milestones and correct along the way.  Of course an inexperienced team does need to plan, and one of the things it should plan to do is get mentoring or coaching from someone with the appropriate knowledge and skills.

And in the middle of the experience spectrum the trap is analysis paralysis where the knowledge planning brings keeps teasing you to go just a little bit further.  In this space you'd be better off starting with a clear focus on the next deliverable and reviewing the plan as you go.


Search This Blog