How to Determine Which Processes Should Be Used for Better Delivery of Scrum Projects
Create a Project Vision., Identify Scrum Master and Stakeholder(s)., Form a Scrum Team., Develop Epic(s)., Create Prioritized Product Backlog., Conduct Release Planning., Create User Stories., Approve, Estimate, and Commit User Stories., Create...
Step-by-Step Guide
-
Step 1: Create a Project Vision.
In this process, the Project Business Case is reviewed to create a Project Vision Statement that will serve as the inspiration and provide focus for the entire project.
The Product Owner is identified in this process. -
Step 2: Identify Scrum Master and Stakeholder(s).
In this process, the Scrum Master and Stakeholders are identified using specific Selection Criteria. , In this process, Scrum Team members are identified.
Normally the Product Owner has the primary responsibility of selecting team members, but often does so in collaboration with the Scrum Master. , In this process, the Project Vision Statement serves as the basis for developing Epics.
User Group Meetings may be held to discuss appropriate Epics. , In this process, Epic(s) are refined, elaborated, and then prioritized to create a Prioritized Product Backlog for the project.
The Done Criteria is also established at this point. , In this process, 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 in this process. , In this process, User Stories and their related User Story Acceptance Criteria are created.
User Stories are usually written by the Product Owner and are designed to ensure that the customer’s requirements are clearly depicted and can be fully understood by all stakeholders.
User Story Writing Exercises may be held which involves Scrum Team members creating the User Stories.
User Stories are incorporated into the Prioritized Product Backlog. , In this process, 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. , In this process, the Approved, Estimated, and Committed User Stories are broken down into specific tasks and compiled into a Task List.
Often a Task Planning Meeting is held for this purpose. , In this process, 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. , In this process, the Scrum Core Team holds Sprint Planning Meetings where the group creates a Sprint Backlog containing all tasks to be completed in the Sprint. , In this process, the Scrum Team works on the tasks in the Sprint Backlog to create Sprint Deliverables.
A Scrum board is often used to track the work and activities being carried out.
Issues or problems being faced by the Scrum Team could be updated in an Impediment Log. , This is the forum for the Scrum Team to update each other on their progress and any impediments they may be facing. , In this process, the Prioritized Product Backlog is continuously updated and maintained.
A Prioritized Product Backlog Review Meeting may be held, in which any changes or updates to the backlog are discussed and incorporated into the Prioritized Product Backlog as appropriate , In this process, Scrum Team representatives convene for Scrum of Scrums (SoS) Meetings in predetermined intervals or whenever required to collaborate and track their respective progress, impediments, and dependencies across teams.
This is relevant only for large projects where multiple Scrum Teams are involved. , In this process, the Scrum Team demonstrates the Sprint Deliverables to the Product Owner and relevant stakeholders in a Sprint Review Meeting.
The purpose of this meeting is to secure approval and acceptance from the Product Owner for the Deliverables created in the Sprint. , In this process, the Scrum Master and Scrum Team meet to discuss the lessons learned throughout the Sprint.
This information is documented as lessons learned which can be applied to future Sprints.
Often, as a result of this discussion, there may be Agreed Actionable Improvements or Updated Scrum Guidance Body Recommendations. , In this process, Accepted Deliverables are delivered or transitioned to the relevant stakeholders.
A formal Working Deliverables Agreement documents the successful completion of the Sprint. , In this process, which completes the project, organizational stakeholders and Scrum Core Team members assemble to retrospect the project and identify, document, and internalize the lessons learned.
Often, these lessons lead to the documentation of Agreed Actionable Improvements, to be implemented in future projects. -
Step 3: Form a Scrum Team.
-
Step 4: Develop Epic(s).
-
Step 5: Create Prioritized Product Backlog.
-
Step 6: Conduct Release Planning.
-
Step 7: Create User Stories.
-
Step 8: Approve
-
Step 9: Estimate
-
Step 10: and Commit User Stories.
-
Step 11: Create Tasks.
-
Step 12: Estimate Tasks.
-
Step 13: Create Sprint Backlog.
-
Step 14: Create Deliverables.
-
Step 15: Conduct Daily Standup—In this process
-
Step 16: everyday a highly focused
-
Step 17: Time-boxed meeting is conducted referred to as the Daily Standup Meeting.
-
Step 18: Groom Prioritized Product Backlog.
-
Step 19: Convene Scrum of Scrums.
-
Step 20: Demonstrate and Validate Sprint.
-
Step 21: Retrospect Sprint.
-
Step 22: Ship Deliverables.
-
Step 23: Retrospect Project.
Detailed Guide
In this process, the Project Business Case is reviewed to create a Project Vision Statement that will serve as the inspiration and provide focus for the entire project.
The Product Owner is identified in this process.
In this process, the Scrum Master and Stakeholders are identified using specific Selection Criteria. , In this process, Scrum Team members are identified.
Normally the Product Owner has the primary responsibility of selecting team members, but often does so in collaboration with the Scrum Master. , In this process, the Project Vision Statement serves as the basis for developing Epics.
User Group Meetings may be held to discuss appropriate Epics. , In this process, Epic(s) are refined, elaborated, and then prioritized to create a Prioritized Product Backlog for the project.
The Done Criteria is also established at this point. , In this process, 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 in this process. , In this process, User Stories and their related User Story Acceptance Criteria are created.
User Stories are usually written by the Product Owner and are designed to ensure that the customer’s requirements are clearly depicted and can be fully understood by all stakeholders.
User Story Writing Exercises may be held which involves Scrum Team members creating the User Stories.
User Stories are incorporated into the Prioritized Product Backlog. , In this process, 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. , In this process, the Approved, Estimated, and Committed User Stories are broken down into specific tasks and compiled into a Task List.
Often a Task Planning Meeting is held for this purpose. , In this process, 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. , In this process, the Scrum Core Team holds Sprint Planning Meetings where the group creates a Sprint Backlog containing all tasks to be completed in the Sprint. , In this process, the Scrum Team works on the tasks in the Sprint Backlog to create Sprint Deliverables.
A Scrum board is often used to track the work and activities being carried out.
Issues or problems being faced by the Scrum Team could be updated in an Impediment Log. , This is the forum for the Scrum Team to update each other on their progress and any impediments they may be facing. , In this process, the Prioritized Product Backlog is continuously updated and maintained.
A Prioritized Product Backlog Review Meeting may be held, in which any changes or updates to the backlog are discussed and incorporated into the Prioritized Product Backlog as appropriate , In this process, Scrum Team representatives convene for Scrum of Scrums (SoS) Meetings in predetermined intervals or whenever required to collaborate and track their respective progress, impediments, and dependencies across teams.
This is relevant only for large projects where multiple Scrum Teams are involved. , In this process, the Scrum Team demonstrates the Sprint Deliverables to the Product Owner and relevant stakeholders in a Sprint Review Meeting.
The purpose of this meeting is to secure approval and acceptance from the Product Owner for the Deliverables created in the Sprint. , In this process, the Scrum Master and Scrum Team meet to discuss the lessons learned throughout the Sprint.
This information is documented as lessons learned which can be applied to future Sprints.
Often, as a result of this discussion, there may be Agreed Actionable Improvements or Updated Scrum Guidance Body Recommendations. , In this process, Accepted Deliverables are delivered or transitioned to the relevant stakeholders.
A formal Working Deliverables Agreement documents the successful completion of the Sprint. , In this process, which completes the project, organizational stakeholders and Scrum Core Team members assemble to retrospect the project and identify, document, and internalize the lessons learned.
Often, these lessons lead to the documentation of Agreed Actionable Improvements, to be implemented in future projects.
About the Author
Kevin Jordan
Professional writer focused on creating easy-to-follow practical skills tutorials.
Rate This Guide
How helpful was this guide? Click to rate: