Scrum Processes – II (Implement, Review and Retrospect)
Scrum processes address the specific activities and flow of a Scrum project. The main processes can be summarized as Initiate, Plan and Estimate, Implement, Review and Retrospect, Release.
The last three phases; “Implement, Review and Retrospect, Release” will be introduced in this article.
- Create Deliverables
- Conduct Daily Quick Review
- Organize Prioritized Product Backlog
4. Review and Retrospect:
- Assemble Scrum of Scrums
- Establish and Validate Sprints
- Reexamine Sprint
- Ship Deliverables
- Retrospect Project
The Scrum Team focuses on the Sprint Backlog to create Sprint Deliverables. The work and activities, which have been carried out, usually are tracked via a Scrumboard. The Scrum Team should update the issues or problems being faced in an Impediment Log.
Conduct Daily Quick Review:
Everyday, a highly and time-boxed Daily Standup Meeting is conducted. This meeting can be considered as the forum for the Scrum Team to update each other on their progress and any holdbacks they may be facing.
Organıze Prioritized Product Backlog:
The Prioritized Product Backlog is continuously revised and maintained. A Prioritized Product Backlog Review Meeting may be held, in which any changes or updates to the backlog are discussed and combined into the Prioritized Product Backlog.
Review and Retrospect
Assemble Scrum of Scrums:
Scrum of Scrums (SoS) Meetings are conducted with the Scrum Team representatives in predetermined intervals and whenever required to cooperate and track respective progress, holdbacks, and dependencies across teams. This is relevant only for large projects where multiple Scrum Teams are involved.
Establish and Validate Sprint:
A Sprint Review Meeting’s main focus is the Scrum Team to demonstrate the Sprint Deliverables to the Product Owner and relevant stakeholders. The purpose of this meeting is to secure approval and acceptance from the Product Owner for the Deliverables created in the Sprint.
Throughout the Sprint, the Scrum Master and Scrum Team meet to identify the lessons learned topics. This information is documented to be used for future Sprints. As a result of this discussion, there may be Agreed Actionable Continues Improvements or Updated Scrum Guidance Body Recommendations.
The Accepted Deliverables are presented or transitioned to the relevant stakeholders. A formal “Working Deliverables Agreement” proofs the successful completion of the Sprint.
The project is completed at this stage. Organizational stakeholders and Scrum Core Team members convene to retrospect the project and identify, document, and internalize the lessons learned.