Agile Process - Scrum Overview
- A product owner creates a prioritized wish list called a Product Backlog.
- During Sprint planning, the team pulls a small chunk from the top of that wish list, a Sprint Backlog, and decides how to implement those pieces.
- The team has a certain amount of time, called a Sprint (usually two to four weeks), to complete its work, but it meets each day to assess its progress (daily Scrum).
- Along the way, the Scrum Master keeps the team focused on its goal.
- At the end of the Sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or present to a stakeholder.
- The Sprint ends with a Sprint Review and Retrospective.
- As the next Sprint begins, the team chooses another chunk of the Product Backlog and begins working again.
ISO uses the Plan-Do-Check-Act (PDCA) cycle as the basis of a quality management system.
Here’s how PDCA is similar to the way we do Sprints.
- We plan for the current Sprint and the future Sprint through Backlog grooming and Sprint planning.
- We execute the Sprint through the Sprint Backlog.
- We review the Sprint through the Sprint Review and Retrospective.
- We act on retrospective outcomes and plans for continuous improvements.
How Scrum Aligns to ISO 9001:2015
ISO talks about the Plan-Do-Check-Act (PDCA) cycle as the basis of the quality management systems. Let me first summarize how PDCA is similar to the way we do sprints.
We plan for the current sprint and the future sprint through backlog grooming and sprint planning. We execute the sprint through the sprint backlog. We review and retrospect the sprint through the sprint review and retrospective. We act on retrospective outcomes and plans for continuous improvements.
Azimuth works with its clients to plan, develop, execute and report on the success of our initiatives using the scrum process, with ISO 9001:2015 and agility that ensures that efficiencies are found and dynamic processes can be implemented..