Scrum phases

The first phase - pregame- is concerned about two things which are planning and architecture. Planning includes a definition of a new release. It is based on backlog that is currently known and with an estimate of its schedule and cost. Further activity depends whether a new system is being developed or if an already existing system is being improved. If a new system is being developed then this phase consists of conceptualization and analysis. If the latter is the case and a system is improved then this phase is narrowed to limited analysis. The second point of this phase is architecture. It is concerned about how the backlog item will be implemented. It consists of two steps: system architecture modification and high level design.

The second phase, called game, is about development sprints. It concerns development of new release functionality with constant attention paid to certain variables, namely: time, requirements, quality, cost and competition. The end of this phase is defined by interaction with these variables. To evolve the system certain multiple, iterative development sprints, also called circles, are used.

The last phase is postgame, in other terms closure. It is concerned with preparation for release and includes final documentation, pre- release stage testing and eventually release.

To explain it in further detail, each of the above mentioned phases has certain, typical for itself, steps. Planning consists of the following steps: development of a backlog list that needs to be comprehensive; definition of such factors as the delivery date and functionality of one or more releases; most appropriate selection of the release for the purpose of immediate development; once the release is selected, mapping of product objects for backlog items should be conducted; next step is a definition of a project team or teams for the building of the new release; appropriate risk controls and assessment of risk; backlog items and packets should be reviewed and checked for possible adjustment; then development tools and infrastructure should be validated and reselected; the second last step is to estimate release cost including development as well as collateral material, marketing, training and finally rollout; the last step in this phase is to verify management approval and funding.

The Architecture and High Level Design phase consists of the following steps: assigned backlog items should be reviewed; changes that are necessary to implement backlog items are to be identified; next domain analysis should be performed in order to extent the required to build, enhance or update the domain models to reflect the new system context and requirements; the second last thing to do is to identify any possible problems in implementing or developing the changes; the last step is doing the design review meeting on which every team has to present approach and changes in order to implement each backlog item; then changes should be reassigned as required.

The Development (Sprint) phase is also known as Concurrent Engineering . It consists of the following macro processes: reviewing the release plans on meetings with teams; distribution, review and adjustment of the standards with which the product will conform; the last step are Iterative Sprints carried out until the product is estimated ready for distribution.

As we can see the Scrum methodology is very well organized and very effective. Whats else worth mentioning that the whole Scrum process is limited in time. If the time of the sprint has ended the process has to be stopped. It makes the process more resolute , people work at the most important things and don't waist their time for unnecessary .

Read more on scrum phases on the scrummethodology.org SCRUM portal