Sprints
There are several steps needed to set up a project for success. Once it is set up, the team will use sprints to work their way through achieving goals and delivering value.
Setup
One of the first things that should be done is to identify the Product Owner. Their role is crucial to determine the goals and priorities for the project. The Product Owner can begin the process of building the Product Backlog. Next, identify the Scrum Master and Team Members for the project. The Scrum Master will begin working with the Product Owner to organize the Product Backlog, and set up the tools and documentation. The Team Members will be helpful in ensuring that the Backlog Items are well-planned and that they do not have any open questions or concerns about the goals being identified.
Usually the Scrum Master will help set up much of the project in Scrumly, however it will be valuable for the Product Owner and Team Members to become familiar with the tools.
Usually the Scrum Master will help set up much of the project in Scrumly, however it will be valuable for the Product Owner and Team Members to become familiar with the tools.
Sprint Cycles
A Sprint is referred to as a cycle or an iteration because the team will usually repeat the Sprint process over and over for the duration of the project. There is no limit to the number of sprints a project may span. A sprint has three basic phases: Planning, Active and Complete. The planning phase is all about making sure the time period has been determined, the backlog items are identified and reasonable for the given time period, and that all the backlog items are fully planned and ready to be worked on. The active phase is generally where the Team Members complete the work needed to accomplish the goals of the backlog items. The backlog items are considered done when the Product Owner has validated that the work meets the Acceptance Criteria. Once all the work is done, hopefully within the predetermined time period, the sprint is complete.
At the completion of a sprint, it is customary to have a meeting to discuss the performance of the team during the sprint. It can be helpful to identify any problems that occurred during the sprint and how to avoid the same problems from occurring on the next sprint. This meeting is called a Retrospective. It is the looking-back on the sprint just completed with the hope to improve the team performance on the future sprints. This is also known as a Continuous Improvement process, and is critical if the team wants to be successful.
After the retrospective meeting, the sprint cycle starts again by planning and starting the next sprint.
At the completion of a sprint, it is customary to have a meeting to discuss the performance of the team during the sprint. It can be helpful to identify any problems that occurred during the sprint and how to avoid the same problems from occurring on the next sprint. This meeting is called a Retrospective. It is the looking-back on the sprint just completed with the hope to improve the team performance on the future sprints. This is also known as a Continuous Improvement process, and is critical if the team wants to be successful.
After the retrospective meeting, the sprint cycle starts again by planning and starting the next sprint.