Our Process

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.