Scrum sprint cycle 8 steps


This paper briefly introducesScrum framework。 Scrum is an iterative and incremental software development method. There are three main in scrumroleProduct ownerScrum MasterandScrum team。 Scrum projects typically consist of multipleSprint composition, each sprint usually lasts two to four weeks. The key elements of Scrum are: scrum roleworkpieceAnd rituals, as well as some guidelines and rules.

To start a scrum project, the product owner creates a project calledProduct backlogList your wish list items and prioritize them. adoptSprint planning meeting, the scrum team decides how many backlog projects can be developed in sprint. Every day in sprint, the team gets together to do a project calledDaily Scrum MeetingMy stationmeeting。 During sprint, the scrum master tries to remove any obstacles and obstacles so that the scrum team can continue to work. At the end of sprint, the team shows the developed features to the team and other stakeholders, which may be candidates for release. At the end of sprint, atReview meetingOne moreSprint Review。[](https://www.visual-paradigm.c…)

Scrum sprint cycle 8 steps

Scrum sprint cycle 8 steps

Scrum sprint cycle 8 steps

The best scrum software needed for every project

A powerful scrum software that supports scrum project management. It has scrum tools such as user story map, product to-do management, sprint to-do management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint review tool, burnout, obstacles, stakeholders and team management.

Learn more

Scrum role:

  • Product owner
  • Scrum master
  • Development team
  • stakeholder

Scrum artifacts

Scrum ceremony

Scrum process explanation

  1. First, we need to determine a product backlog (product demand list sorted by priority), which is the responsibility of the product owner
  2. The scrum team estimates and arranges the workload according to the product backlog list in the product backlog refining meeting
  3. With the product backlog list, we need to hold a sprint planning meeting to define the sprint goal of this iteration (the time period of a sprint is usually 1-4 weeks), and then select a user story list to form the upcoming sprint for which the sprint backlog can achieve the sprint goal.
  4. The sprint backlog is completed by the scrum team, and each member is subdivided into smaller tasks according to the sprint backlog (the workload of each task can be completed in a few days)
  5. In sprint, a daily scrum meeting needs to be held, and the time of each meeting is limited to about 15 minutes. Everyone should speak, interact with all members face to face, report what they did yesterday and what they want to accomplish today, and you can ask questions about obstacles or unsolvable problems. Then, update your sprint burn out chart.
  6. Realize daily integration, that is, there should be a version that can be compiled successfully and demonstrated every day; Many people may not have used automated day-to-day integration. If passed, execute the unit test code immediately. If all of these pass, release the version.
  7. When all user stories are completed, that is, the sprint backlog is completed, it means that a sprint is completed. At this time, we need to conduct a sprint review meeting (also known as review meeting). Product owners and customers must be involved. Every member of the scrum team will show them the work software they have completed. This meeting is very important and cannot be cancelled.
  8. Finally, the sprint retrospective is held after the sprint review at the end of each sprint. During the review, the team identifies the process elements that are effective or ineffective during the sprint, as well as potential solutions. The review usually lasts 90 minutes and helps us integrate continuous improvement into our team culture and sprint rhythm.


Scrum is an iterative and incremental framework for managing product development. It defines a flexible and holistic product development strategy in which the development team works closely to achieve common goals. It enables teams to organize themselves by encouraging physical co location or close online collaboration among all team members, as well as daily face-to-face communication between all team members and related disciplines.