In Extreme Programming , The planning game is a planning meeting between the R & D team and stakeholders , It consists of two parts ： Release plan and iteration plan . Customers and all developers on the team are expected to attend .
Extreme programming planning game with Scrum It's a very similar meeting , The release plan and iteration plan of the planning game both include exploration 、 Commitment and guidance 3 Stages .
In the exploration phase , Customers organize user stories , On the user story card . Developers estimate the amount of work required per user story , And write the estimate on the story card . If individual user stories cannot be estimated , After the customer decomposes again , And then the developer estimates .
In the commitment phase , Customers sort user stories according to their business value , Developers sort user stories by risk , And confirm the development speed .
Finally, it is up to the customer to choose when the next version is released , User stories to complete . In the coaching phase , Developers and customers can adjust 、 Revise the plan . For example, the priority of user stories may change 、 There may be deviations in the estimation . This is an opportunity to adjust the plan accordingly
Iteration planning is a further plan for the release plan , In the exploration phase , The team discusses each user story and breaks it down into tasks , Then estimate the work hours for the task .
In the commitment phase , Each R & D personnel voluntarily receives their own tasks , And make a final estimate of what you're responsible for , Assess whether you are over committed .
In the coaching phase , The developer in each subsequent iteration , Through pair programming 、 Continuous integration 、 Practice such as test driven development implements each task , And finally, functional tests are carried out .
Proponents of extreme programming believe that ： The continuous change of software requirements is inevitable in software project development 、 It is also a natural phenomenon that should be readily accepted ; They believe , And the traditional way of defining all requirements at the beginning of a project , And painstaking efforts to control change compared to ,XP Support each other through multiple practices , Adapt to change at any stage of the project cycle , Will be a more effective way .
for example ： The team works through good pair programming 、 Code specification 、 Code collective ownership 、 Continuous integration and other practices , It's easier to refactor code . Interested partners , Welcome to the previous video of the Extreme Programming Series , Learn more about practice .
More wonderful video sharing ：https://www.zentao.net/page/college.html/?u=uplu&f=bky