In the agile development process, a product or a release version is usually implemented by multiple sprints, each sprint incremental delivery system functions can be operated to achieve customer value. Each sprint begins at the sprint planning, the team members agreed with the objectives and sprint clear delivery system functions, and sprint execution, system functions, and then view the product features and implementation process through review and sprint review, expected in the next during a sprint to the product features and process improvement and perfection.
Sprint Process
Including sprint sprint planning , sprint execution , Sprint Review , Sprint Retrospective four process. Sprint is planning from the start, team members must reach a consensus on this sprint goals and plans, and ran all the members of this goal in accordance with established plans throughout the sprint course, a day of achievements and problems faced communicate discussion. End sprint stage, to convene the relevant stakeholders in the sprint assessment activities together demonstrate product features and to obtain feedback from the product obtained is an important source list and the next stage sprint planning content. In the sprint retrospectives, all team members to view and process execution sprint discussion, seize the existing problems and discuss optimization, improvements in the next sprint and optimized to achieve optimization and upgrade the efficiency of the process sprint sprint.
Sprint planning
Under normal circumstances, is at the beginning of each sprint planning sprint, because at this point in time, can take full advantage of information already mastered the most optimal decisions. Length sprint planning process according to the length of time depending sprint, occupies the entire sprint about 5% is more reasonable time, such as two weeks sprint should be controlled within 4 hours, month sprint should be controlled within 8 hours.
Sprint planning process should be done in collaboration by the entire team, product owner to select items from a list of existing product inventory list, the preliminary target sprint, and is responsible for the development team to explain any questions raised by the list of items for the selected product. Development work within the sprint team on the list of deliverables to assess and make final commitments at the end of planning. Scrum Master as a coach, participate and observe the entire process, made possible risks point to guide and help the development team to make effective commitments.
In the sprint planning process, the basic process is:
At the end of the sprint planning process, the ultimate goal of obtaining sprint and sprint inventory, the development team to make a commitment to this goal and task lists, and work towards this goal in the next sprint execution.
Sprint execution
Sprint to perform all the work, including the delivery of an incremental release of the product and must be completed, which itself is like a super-small project implementation process sprint sprint takes up most of the time, such as two-week sprint, the sprint execution occupancy 10 8 days days, so the implementation process is critical to the successful completion of the sprint sprint goals. Execution of a sprint planning, management, execution and communication work:
01 Plan
Sprint execution plan can be important sprint in the list of work items sort of dependency, but do not require a detailed implementation plan, such as a Gantt chart, as this may be a waste of time. Team not only a waste of time to make plans, but also a waste of time trying to plan more adjusted to reflect the actual implementation. The implementation of the principle of sprint planning is to play it by ear, gradually clear mission planning, this activity is a continuous, throughout the implementation process sprint.
02 Management
Sprint executive management is to ensure that management activities carried out to achieve the sprint goal. Determine the characteristics of the development team management style. Sprint Executive Management specifically to address the following questions:
It should work in parallel several items? Too many parallel work items, team members can switch between different work items, resulting in waste; parallel work items too little will cause waste of resources, the number of parallel right amount, and strive to make full use of the production capacity of the team, but will not too heavy to achieve a reasonable balance, which requires each team according to their abilities and characteristics to practice and explore.
Which work item from the start? The easiest way should be a priority of the sort in descending turn, but in the implementation process may encounter various problems lead to high priority work items temporarily unable to start, you can also start times in this case high-priority work.
By whom? The most obvious answer is to do the best that can be completed fastest man. But each team has its own considerations, such as the most suitable person may be busy with other work not open itself, or he might be on holiday, even from the perspective of the development team to consider, you can give other members of the training opportunities in order to achieve team members on the skills overlap and complement each other.
Daily meetings is a key daily views - tuning activities, time control in less than 15 minutes, the main purpose is to review, adjust and synchronize daily work plan to help the team do a better job.
03 execution
Scrum agile software development carried out, some of the team members require skilled application software development practices such as continuous integration, automated testing, refactoring, test-driven development, the development team will practice these techniques put forward higher requirements, would in the short term the development team resulting in pressure or other aspects of progress, but in the long run, only the active use of these good technical practice, in order to effectively experience the benefits of agile.
04 Communication
Agile teams generally small enough team, a small communication team members do not need complicated graphs and reports to communicate progress, we recommend the following methods and tools:
Task Panel: displays a list with task status sprint time.
Sprint burndown: displaying the remaining curved work uncompleted tasks.
FIG combustion Sprint: displaying a graph to achieve workload goals during the sprint completed.
Sprint Review
Sprint Review overshoot the focus is product that is the result of concern on the results of the work accomplished during the sprint execution view, the people involved, including Scrum team, internal stakeholders and external stakeholders are and so on. An important preparatory work before the start of the assessment is to identify sprint work is completed, the work is done by the product owner, his final sprint in the list of work items is completed, the timing is not confirmed until the last minute before the review can sprint During execution confirmation as soon as possible, it will identify problems early, win redress time.
The method employed in the sprint review process comprises:
01 summary
Usually work this sprint will be responsible for general description of the product and show the sprint and sprint target list, the basic information of the finished product increment.
02 demo
Demonstration by the development team members completed system functions, for not so easy to demonstrate the functions (such as program running in the background) to provide at least some of the test program to demonstrate the work done to meet the person in charge of product requirements. Note that the presentation is not an end in itself, the purpose of the presentation is to stimulate thinking crash team members, proposed a more constructive suggestions and feedback.
03 discussions
Incremental product demo guide participants to comment on aspects such as product features or goals, establish and properly discussed, such as the need to discuss the issue more in-depth program should be another meeting independently.
04 adjustment
Through presentations and discussions will produce some changes or additions to the needs of sprint list of those changes and the list of products and demand will bring the next phase of adjustment, after combing through, each time the end of the sprint will be updated products inventory, timely response to changes in the next sprint.
Sprint Review
Sprint Retrospective concern is the product build process itself, that is concerned with the process. Recalling what happened with the team sprint process, analyze their own work to identify problems that may exist, propose improvements and plans for improvement. Before each sprint review, we can define the key elements of the review, in order to avoid fragmentation. In the review meeting, the need to ensure that create an atmosphere of "not the person", the review aims to improve the process, rather than an accused person. At the end of review, team members follow up and implement improvement measures, making the team sprint in the next more efficient.
to sum up
Sprint includes most of the time and activities throughout the product or project development and management, are the main aspects of the product functions implemented. This paper attempts from the sprint planning, sprint execution, sprint review and sprint retrospective point of view of four processes, explore the full range of all activities and work content sprint involved, hoping to inspire and assist in the implementation process in the sprint for agile teams.
Author: Li Hao
Other high-quality articles
How companies plan DevOps floor and evolution?
ZooKeeper | installation deployment scenarios, the development of docking API
[Bank] landing platform operation and maintenance management, big step towards the Bank 4.0