Transfer from: http: //www.scrumcn.com/agile/scrum-knowledge-library/scrum.html#tab-id-15
Scrum is an iterative and incremental approach to product development, Scrum Sprint to achieve by iterations. Refers to a Sprint a one week iteration four weeks, it is a time box. Once the length of Sprint, remains unchanged. Sprint's output is "done", available, potentially publishable product increment. Sprint cycle consistent throughout the development process. The new Sprint commence immediately after the completion of a Sprint. Sprint includes Sprint planning meeting by a day the station will, development, and Sprint Review Meeting Sprint Retrospective meeting constituted.
Scrum is an iterative incremental way, because demand is emerging, our understanding of the product and demand is progressive, the longer the length of Sprint, the more we need to predict the complexity will increase, the risk will increase, so Sprint length of not more than 4 weeks. More and more teams use two weeks of Sprint, a lot of changes in the market faster, highly competitive areas, such as the Internet and mobile Internet product development team will also use 1-week iterations.
Sprint In the process, the following changes can occur:
- Sprint's goal
- Sprint's quality goals and acceptance criteria
- The composition of the development team
Concentrate superior forces to crush one
During the execution of the Sprint, the team to avoid a carrot a pit way of working, a team to collaborate, and to concentrate superior forces separately.
According to team work swarming formula (Swarming), the team first concentrated in a few work above demand, collaborate on them, and then at the beginning of a number of requirements. In this way on the one hand can enhance teamwork, while also conducive to the early completion of a number of needs, so that these needs early acceptance.
Cancel a Sprint
Sprint can be canceled before the end of the Sprint time box. Only the Product Owner has the authority to cancel the Sprint talent, but he made such a decision may also be subject to the interests of the stakeholders, the impact of the team or Scrum Master.
If a Sprint goal out of date, you need to cancel the Sprint. For example, the case of the company's direction, or the market and technology changes, these changes are likely to result in cancellation of Sprint. In general, if a Sprint for its lost value and meaning in the environment, then it should be canceled. However, since Sprint cycle is short, so it is rarely the case of cancellation of Sprint occur.
When a Sprint is canceled, any finish and "done" Product-do list entries need to review. If some of the items may have the potential to deliver that product owner will buy into it. All incomplete entries will be put back into product-do list, and re-evaluated. Who spend their working depreciate quickly, so they need frequent reassessment.
Cancel Sprint will consume resources, since everyone needs to re-start another Sprint in the Sprint planning meeting held in the new. Sprint team will usually terminate devastated, so this case is very rare.