Process

Scrum's regular cycle is focused on delivering the highest value, production quality code every month. This section discusses the elements that make up this regular process.

At the beginning of a Sprint, we start with the Product Owner ensuring that we have a prioritised and up-to-date Product Backlog. This allows the team to select an achievable set of the highest priority backlog and work out how to build it in the Sprint Planning meeting. The team then proceeds to work through the Sprint Backlog tasks on a daily basis, synchronising their activity in a daily Scrum Meeting. At the end of the Sprint the team have built a Product Increment which they demonstrate to the Product Owner, business users and other interested stakeholders in the Sprint Review. Feedback from the Sprint Review will be added to the Product Backlog and prioritised by the Product Owner. Before starting the next Sprint the team discuss their performance and make improvements in the way they work in the Sprint Retrospective.

The team will continue Sprinting until they have developed a sufficiently useful system that can be put into production in a Release Sprint.