ThePlanningGame

UserPreferences

"Quickly determine the scope of the next release by combining business priorities and technical estimates. As reality overtakes the plan, update the plan." (Beck,Fowler) See ReleasePlanning and IterationPlanning.

What is it?

• analysis
• scope management
• prioritization
• estimation
• scheduling
• 2 types: IterationPlanning and ReleasePlanning

If this is a "best practice", then why don't people do it?

• They do, to varing extents. They have found a level that seems to be good enough. It's a matter of degrees.

How is it any different if done "eXtreme"?

• more fine grained
• more estimates
• more prioritization
• more disciplined / rigorous
• kept up-to-date

What other practices support this practice?

• CommonVocabulary helps communication
• OnSiteCustomer
• PairProgramming and CollectiveOwnership improve accuracy of estimates and schedules

What other practices are supported by this one?

• prioritization supports SmallReleases
• prioritization helps us produce high value with a SustainablePace
• this kind of planning makes the OnSiteCustomer happy
• discovers test data for UnitTesting

How do I get started?

• Read "Planning Extreme Programming", by Beck and Fowler.

Next: SmallReleases

-- AndrewFuqua - 31 Mar 2002 <br />