advertisement
Types of Scrum process
The Scrum Process
The Scrum process consists of the following phases:
- Pregame
- Game
- Post-game
1. Pregame
Planning is the process of defining a new release based on a currently known backlog with an estimate of its schedule and cost. When a new system is being developed, the planning phase consists of both conceptualization and analysis. For the enhancement of an existing system, the planning phase consists of limited analysis.
Steps in planning:
- Preparation of a comprehensive backlog list.
- Definition of the functionality and delivery date of one or more releases.
- Prioritizing the functionalities according to importance.
- Mapping of product packets for backlog items in the selected release.
- Definition of project teams for the development of the new release.
- Assessment of risk and risk controls.
- Review and modification of backlog items.
- Estimation of release costs, including development, marketing, and training. Rollout, and collateral material.
- Verification of infrastructure and development tools.
- Confirmation of management approval and funding.
The architecture phase includes system architecture modification and high-level design. Steps in architecture:
- Review assigned backlog items.
- Identify changes necessary to implement backlog items.
- Analyze domains to develop, modify, or update domain models to reflect the new system context and requirements.
- Modify the system architecture to support new requirements.
- Identify issues with developing or implementing the changes.
- Design review meeting, with each team putting forth their strategies and plans to implement the backlog items.
2. Game
A development sprint is the development of new functionality, concerning the variables of time, requirements, quality, cost, and competition. There are multiple iterative development sprints used in the evolution of the system.
1. Steps in a Development Sprint:
In the development phase, development work is done in an iterative cycle. Management determines whether time, competition, quality, or functionality are met and iterations are completed. This approach is also known as concurrent engineering.
Development consists of the following processes:
- Meeting with teams to review release plans.
- Review and improvement of the standards that the product needs to adhere to.
- Plan iterative sprints, until the product is ready for dispatch.
Rick is continuously assessed and sufficient risk controls and responses are put in place. Each sprint consists of the following steps:
2. Develop:
Defining changes needed for implementing the backlog requirements into packets, analyzing them, designing, developing, implementing, testing, and documenting the ns Development consists of discovery, invention, and implementation.
- Wrap: Closing the packets and creating an executable version of the changes to implement backlog requirements.
- Review: All involved teams meet to present their progress, raise and sort out issues, and update the backlog list. Risk is also reviewed and appropriate action is taken.
- Adjust: Including the information from the review meeting into appropriate packets, and including new properties as needed.
Each sprint is followed by a review, where:
- The whole team and product management participated.
- Customers, sales, marketing, and others may participate.
- Functional and executable systems that include the objects assigned to that team and the changes made to implement the backlog items are reviewed.
- New requirements may be introduced and assigned to teams.
- The time of the next review is decided based on progress and complexity.
3. Postgame
The preparation for release, final documentation, pre-release testing, and release happen during the closure phase.
The management team declares a release 'closed' when the variables of time, competition, requirements, cost, and quality meet the requirements. Closure includes tasks such as integration, system test documentation, training material preparation, and marketing material preparation.
advertisement
Conversation
Your input fuels progress! Share your tips or experiences on prioritizing mental wellness at work. Let's inspire change together!
Join the discussion and share your insights now!
Comments 0