Scrum Processes – I (Initiate, Plan and Estimate)
Scrum processes address the specific activities and flow of a Scrum project. The main processes can be summarized as Initiate, Plan and Estimate, Implement, Review and Retrospect, Release.
The first two phases: “Initiate, Plan and Estimate” will be introduced in this article.
- Create Project Vision
- Identify Scrum Master and Stakeholder(s)
- Form Scrum Team
- Develop Epic(s)
- Create Prioritized Product Backlog
- Conduct Release Planning
2. Plan and Estimate:
- Create User Stories
- Approve, Estimate, and Commit User Stories
- Create Tasks
- Estimate Tasks
- Create Sprint Backlog
The processes in each phase are described in detail including their associated inputs, tools, and outputs. Inputs, tools, and outputs are important for the successful implementation of Scrum in any organization.
Create Project Vision:
The Project Business Case is reviewed to create a Project Vision Statement that will serve as the main scope and provide focus for the entire project. The Product Owner is identified in this stage.
Identify Scrum Master and Stakeholder:
The Scrum Master and Stakeholders are identified using specific Selection Criteria.
Form Scrum Team:
Scrum Team members are identified. Normally the Product Owner has the primary responsibility of selecting team members, but often works with Scrum Master during selection stage.
Developing Epics is based on The Project Vision Statement. User Group Meetings may be needed to discuss appropriate Epics.
Create Prioritized Product Backlog:
Epic(s) are refined, fine-tuned, and then prioritized to create a Prioritized Product Backlog for the project. The Done Criteria is also established at this point.
Conduct Release Planning:
The Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule, which is essentially a phased deployment schedule that can be shared with the project stakeholders. Length of Sprint is also determined at this point.
Plan and Estimate
Create User Stories:
User Stories and related User Story Acceptance Criteria are determined. User Stories are mainly written by the Product Owner and are designed to ensure that the customer’s requirements are clearly defined and can be fully understood by all stakeholders. Scrum team members will be focusing to create the User Stories during User Story Writing Exercises sessions. User Stories are integrated into the Prioritized Product Backlog.
Approve, Estimate, and Commit User Stories:
The Product Owner approves User Stories for a Sprint. Then, the Scrum Master and Scrum Team estimate the effort required to develop the functionality described in each User Story, and the Scrum Team commits to deliver the customer requirements in the form of Approved, Estimated, and Committed User Stories.
The Approved, Estimated, and Committed User Stories are broken down into specific tasks and accumulated into a Task List. Often a Task Planning Meeting must be held for this purpose.
The Scrum Core Team, in Task Estimation Meetings, estimate the effort required to accomplish each task in the Task List. The result of this process is an Effort Estimated Task List.
Create Sprint Backlog:
The Scrum Core Team holds Sprint Planning Meetings where the group creates a Sprint Backlog containing all tasks to be completed in the Sprint.