Content deleted Content added
Undid revision 720432139 by 122.15.171.149 (talk) |
Italicized level 2 sub-headings since styling unfortunately is the same as for level 3 ones |
||
Line 11:
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 shortlist 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.
Line 31:
}}</ref> The Planning Game approach has also been adopted by non-software projects and teams in the context of [[business agility]].<ref>Leybourn, E. (2013). Directing the Agile Organisation: A Lean Approach to Business Management. London: IT Governance Publishing: 146–150.</ref>
==== ''Release planning'' ====
===== Exploration phase =====
Line 83:
Within the steering phase the programmers and business people can "steer" the process. That is to say, they can make changes. Individual user stories, or relative priorities of different user stories, might change; estimates might prove wrong. This is the chance to adjust the plan accordingly.
==== ''Iteration planning'' ====
Considering team velocity storypoints to be planned. Iteration duration can be 1 to 3 weeks.
| |||