In Stage 1, the product owner identifies the product vision.
The product vision is a definition of what your product is, how it will support your company’s or organization’s strategy, and who will use the product. On longer projects, revisit the product vision at least once a year.
In Stage 2, the product owner and business stakeholders create a product roadmap.
The product roadmap is a high-level view of the product requirements, with a loose time frame for when you will develop those requirements. Identifying product requirements and then prioritizing and roughly estimating the effort for those requirements are a large part of creating your product roadmap. On longer projects, revise the product roadmap at least twice a year.
In Stage 3, the product owner creates a release plan.
The release plan identifies a high-level timetable for the release of product. An agile project will often have many releases, with the highest-priority features launching first. Create a release plan at the beginning of each release.
In Stage 4, the product owner, the scrum master, and the development team plan sprints and starts creating the product within those sprints.
Sprint planning sessions take place at the start of each sprint, where the scrum team determines what requirements will be in the upcoming sprint, and the development team breaks those requirements into specifics tasks necessary to create the functionality.
In Stage 5, during each sprint, the development team has daily scrum meetings.
In the daily scrum meeting, you spend no more than 15 minutes organizing the priorities of the day and discussing what you completed yesterday, what you will work on today, and any roadblocks you have.
In Stage 6, the team holds a sprint review.
In the sprint review, at the end of every sprint, the scrum team demonstrates the working product created during the sprint to the product stakeholders.
In Stage 7, the team holds a sprint retrospective.
The sprint retrospective is a meeting where the scrum team discusses how the sprint went and plans for improvements in the next sprint. Like the sprint review, you have a sprint retrospective at the end of every sprint.