Scrum development process steps and phases

Scrum methodology process could be divided into a couple of phases. Main phases are pregame, game and postgame.

Planning is the first phase in Scrum process. First step in this phase is to create a backlog list and set date of upcoming release. Functionality is also an important factor – should be considered as well in the first steps. Team has to select appropriate release for further development and assess risk and risk controls.
Another step is to map product packets for backlog items in current release and also to define project teams responsible for building next release.
Further steps are:

• review and adjust backlog items and packets;
• validate and research tools and infrastructure;
• estimate release costs;
• final verification, confirmation regarding funding and approval.

Architecture and High Level Design is the next phase. In this phase there are six main steps to perform, such as:

- retrospect relevant backlog items;

- pinpoint necessary changes for backlog items implementation;

- analysis, adjust, enhance and update the domain models (for the new system context reflection and requirements fulfilment);

- revamp the system structure to support new context and requirements;

- identify issues in the change development stage;

- retrospective design meeting arranged – each team represent a way to change and implement backlog items.

The key phase is the Development phase, also known as the Sprint. Sprint is an iterative cycle – Concurrent Engineering – that stops when certain requirements are completed, such as quality and functionality for example. This phase also has steps which are:

- teams are gathered to discuss release plans;

- debate about how to distrubite and adjust the standards which the product will adapt;

- finally iterative Sprints until the product is free of any issues and ready to distribute.

Typical Sprint lasts for from one to four weeks. During that time multiple tasks are being conducted. Length of that iteration period is based on the state of complexity and risk assessment. Each Sprint offers following tasks:

- development: implementation of changes for the packets, opening the packets, analysis, testing;

- wrap: wrapping the changes into an executable example illustrating improvement;

- review: all team debate to present and review progress, adding new requirements into backlog, solving problems;

- adjust: implementing the new requirements from the review part into the packets.

Before another Sprint there is always a review of what has been done so far, update and adjust current release. In this review every member of the team participate, even Product Manager – new ideas can be proposed into new backlog, shaping new way of content and direction of deliverables.

Last phase of this process is called Closure. Closure occurs when all requirements are met. This is the last phase before releasing the product with all documentation. Final tests are done at this point and at the end - the release itself is final

Read more about Scrum development