Planning Game
The main planning process within extreme programming is called the Planning Game. The game is a meeting that occurs once per iteration, typically once a week. The planning process is divided into two parts:
-
Release Planning : this is focused on determining what requirements are included in which near-term releases, and when they should be delivered.
The customers and developers are both part of this. Release Planning consists of three phases:
- Exploration Phase: In this phase the customer will provide a short list of high-value requirements for the system. These will be written down on user story cards.
- Commitment Phase: Within the commitment phase business and developers will commit themselves to the functionality that will be included and the date of the next release.
- Steering Phase: In the steering phase the plan can be adjusted, new requirements can be added and/or existing requirements can be changed or removed.
-
Iteration Planning : this plans the activities and tasks of the developers.
In this process the customer is not involved. Iteration Planning also consists of three phases:
- Exploration Phase: Within this phase the requirement will be translated to different tasks. The tasks are recorded on task cards.
- Commitment Phase: The tasks will be assigned to the programmers and the time it takes to complete will be estimated.
- Steering Phase: The tasks are performed and the end result is matched with the original user story.
The purpose of the Planning Game is to guide the product into delivery. Instead of predicting the exact dates of when deliverables will be needed and produced,
which is difficult to do, it aims to "steer the project" into delivery using a straightforward approach.
From Wikipedia, the free encyclopedia.
Resources
We would like to suggest you the following list of usefull resources on the topic:
|