What Is A Sprint (Agile Software Development)? Definition From ...

Sprint workflow and process

The sprint workflow is intended to help team members evaluate their work and communicate with each other throughout the entire process. The workflow is followed for each sprint and usually includes these steps:

1. Create the product backlog, and define the product goal. Create a list of tasks that must be completed before the product is released. The product goal, which describes the future state of the product under development, is included in the product backlog. The backlog is built by the product owner, who provides a list of prioritized items to the Scrum master and Scrum team. The backlog is based on user stories, which focus on features that consider the type of end user, what they want in the product and why. It is refined as needed during the sprint.
2. Plan sprint. The team discusses top-priority user stories and decides what can be delivered in the sprint.
3. Create a sprint backlog, and define the sprint goal. Agreed upon by the entire team, the sprint backlog is a list of items that finalizes and defines what the development team will complete during the sprint. This provides the focus necessary to successfully complete the sprint and its backlog items.
4. Execute the sprint. The time frame in which the work defined in the sprint backlog must be completed. Ideally, the period should be long enough to give the team flexibility and freedom to do the work. It should also be short enough to minimize complexity and risk and to facilitate frequent feedback and fast changes.
5. Hold a daily scrum. Led by the Scrum master, the team comes together for short daily meetings, in which they discuss what they have completed, what they are working on and any issues that are blocking the work.
6. Determine the outcome. The outcome of a sprint is a hypothetically usable product. The product owner can decide if the product is ready for release or if additional features are needed.
7. End sprint. At the end of a sprint, two meetings are held:

1. Sprint review. The team shows their work to the product owner.
2. Sprint retrospective. The team, along with the Scrum master and product manager, discuss what they can do to improve processes. An important goal is to facilitate continuous improvement.