Scrum Body of Knowledge Phases

Initiate Phase:

  • Create Project Vision (8.1)
  • Identify Scrum Master and Stakeholder(s) (8.2)
  • Form Scrum Team (8.3)
  • Develop Epic(s) (8.4)
  • Create Prioritized Product Backlog (8.5)
  • Conduct Release Planning (8.6)

Plan and Estimate Phase:

  • Create User Stories (9.1)
  • Approve, Estimate, and Commit User Stories (9.2)
  • Create Tasks (9.3)
  • Estimate Tasks (9.4)
  • Create Sprint Backlog (9.5)

Implement Phase:

  • Create Deliverables (10.1)
  • Conduct Daily Standup (10.2)
  • Groom Prioritized Product Backlog (10.3)

Review and Retrospect Phase:

  • Convene Scrum of Scrums (11.1)
  • Demonstrate and Validate Sprint (12.1)
  • Retrospect Sprint (11.3)

Release Phase:

  • Ship Deliverables (12.1)
  • Retrospect Project (12.2)

Note: Asterisks (*) denote a “mandatory” input, tool, or output for the corresponding process.

Figure 8-1: Initiate Overview Figure 8-2: Initiate Overview (Essentials) Figure 8-3: Create Project Vision—Inputs, Tools, and Outputs

Create Project Vision (8.1)

INPUTS

  • [ ] Project Business Case*
  • Program Product Owner
  • Program Scrum Master
  • Program Stakeholder(s)
  • Chief Product Owner
  • Program Product Backlog
  • Trial Project
  • Proof of Concept
  • Company Vision
  • Company Mission
  • Market Study
  • Scrum Guidance Body Recommendations

Recommendations

TOOLS

  • [ ] Project Vision Meeting*
  • JAD Sessions
  • SWOT Analysis
  • Gap Analysis: Figure 8-5: The Gap Analysis Process

OUTPUTS

  • [ ] Identified Product Owner*
  • [ ] Project Vision Statement*
  • Project Charter
  • Project Budget

Identify Scrum Master and Stakeholder(s) (8.2)

Figure 8-6: Identify Scrum Master and Stakeholder(s)—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Project Vision Statement*
  • Stakeholder(s)
  • Program Product Backlog
  • Approved Change Requests
  • Unapproved Change Requests
  • Program and Portfolio Risks
  • Laws and Regulations
  • Applicable Contracts
  • Previous Project Information
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] User Group Meetings*
  • User Story Workshops
  • Focus Group Meetings
  • User or Customer Interviews
  • Questionnaires
  • Risk Identification Techniques
  • Scrum Guidance Body Expertise

INPUTS

  • [ ] Product Owner*
  • [ ] Project Vision Statement*
  • Program Product Owner
  • Program Scrum Master
  • Chief Product Owner
  • Chief Scrum Master
  • Program Stakeholder(s)
  • People Requirements
  • People Availability and Commitment

Commitment

  • Organizational Resource Matrix
  • Skills Requirement Matrix
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Selection Criteria*
  • Expert Advice from HR
  • Training and Training Costs
  • Resource Costs

OUTPUTS

  • [ ] Identified Scrum Master*
  • [ ] Identified Stakeholder(s)*

Form Scrum Team (8.3)

Figure 8-8: Form Scrum Team—Inputs, Tools, and Outputs

INPUTS

  • [ ] Product Owner*
  • [ ] Scrum Master*
  • [ ] Project Vision Statement*
  • Chief Product Owner
  • People Requirements
  • People Availability and Commitment
  • Organizational Resource Matrix
  • Skills Requirement Matrix
  • Resource Requirements
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Scrum Team Selection*
  • Expert Advice from HR
  • People Costs
  • Training and Training Costs
  • Resource Costs

OUTPUTS

  • [ ] Identified Scrum Team*
  • Back-up Persons
  • Collaboration Plan
  • Team Building Plan

Develop Epic(s) (8.4)

Figure 8-10: Develop Epic(s)—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Project Vision Statement*
  • Stakeholder(s)
  • Program Product Backlog
  • Approved Change Requests
  • Unapproved Change Requests
  • Program and Portfolio Risks
  • Laws and Regulations
  • Applicable Contracts: Incremental Delivery Contract, Joint Venture Contract, Development in Phases Contract, Incentive and Penalty Contract
  • Previous Project Information
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] User Group Meetings*
  • User Story Workshops
  • Focus Group Meetings
  • User or Customer Interviews
  • Questionnaires
  • Risk Identification Techniques
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Epic(s)*
  • [ ] Personas*: Creating a Persona
  • Approved Changes
  • Identified Risks

Create Prioritized Product Backlog (8.5)

Figure 8-12: Create Prioritized Product Backlog—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Epic(s)*
  • [ ] Personas*
  • Stakeholder(s)
  • Project Vision Statement
  • Program Product Backlog
  • Business Requirements
  • Approved Change Requests
  • Identified Risks
  • Applicable Contracts
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] User Story Prioritization Methods*: MoSCoW Prioritization scheme, Paired Comparison, 100-Point Method, Kano Analysis
  • User Story Workshops
  • Planning for Value
  • Risk Assessment Techniques
  • Estimation of Project Value
  • User Story Estimation Methods
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Prioritized Product Backlog*: Value, Risk and Uncertainty, Dependencies, Estimates
  • [ ] Done Criteria*

Conduct Release Planning (8.6)

Figure 8-14: Conduct Release Planning—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Stakeholder(s)*
  • [ ] Project Vision Statement*
  • [ ] Prioritized Product Backlog*
  • [ ] Done Criteria*
  • Program Product Owner
  • Program Scrum Master
  • Chief Product Owner
  • Program Product Backlog
  • Business Requirements
  • Holiday Calendar
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Release Planning Sessions*
  • [ ] Release Prioritization Methods*

OUTPUTS

  • [ ] Release Planning Schedule*
  • [ ] Length of Sprint*
  • Target Customers for Release
  • Refined Prioritized Product Backlog

Create User Stories (9.1)

Figure 9-1: Plan and Estimate Overview Figure 9-2: Plan and Estimate Overview (Essentials) Figure 9-3: Create User Stories—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Prioritized Product Backlog*
  • [ ] Done Criteria*
  • [ ] Personas*
  • Stakeholder(s)
  • Epic(s)
  • Business Requirements
  • Laws and Regulations
  • Applicable Contracts
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] User Story Writing Expertise*
  • User Story Workshops
  • User Group Meetings
  • Focus Group Meetings
  • Customer or User Interviews
  • Questionnaires
  • User Story Estimation Methods
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] User Stories*
  • [ ] User Story Acceptance Criteria*
  • Updated Prioritized Product Backlog
  • Updated or Refined Personas

Approve, Estimate, and Commit User Stories (9.2)

Figure 9-5: Approve, Estimate, and Commit User Stories—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] User Stories*
  • [ ] User Story Acceptance Criteria*
  • Scrum Guidance Body

Recommendations

TOOLS (User Story Estimation Methods)

  • [ ] User Group Meetings*
  • Planning Poker
  • Fist of Five
  • Points for Cost Estimation
  • Other Estimation Techniques: (Wideband Delphi, Relative Sizing/Story Points, Affinity Estimation, Estimate Range)
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Approved, Estimated, and Committed User Stories*

Create Tasks (9.3)

Figure 9-7: Create Tasks—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Approved, Estimated, and Committed User Stories*

TOOLS

  • [ ] Task Planning Meetings*: Figure 9-9: Task Planning Meetings (a.k.a Sprint Planning Meeting, similar to Task Estimation Meeting)
  • Index Cards
  • Decomposition
  • Dependency Determination: (Mandatory dependencies, Discretionary dependencies, External dependencies, Internal dependencies)

OUTPUTS

  • [ ] Task List*
  • Updated Approved, Estimated, and Committed User Stories
  • Dependencies

Estimate Tasks (9.4)

Figure 9-10: Estimate Tasks—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Task List*
  • User Story Acceptance Criteria
  • Dependencies
  • Identified Risks
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Task Estimation Meetings*
  • [ ] Estimation Criteria*
  • Planning Poker
  • Fist of Five
  • Other Task Estimation Techniques

OUTPUTS

  • [ ] Effort Estimated Task List*
  • Updated Task List

Create Sprint Backlog (9.5)

Figure 9-12: Create Sprint Backlog—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Task List*
  • User Story Acceptance Criteria
  • Dependencies
  • Identified Risks
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Task Estimation Meetings*
  • [ ] Estimation Criteria*
  • Planning Poker
  • Fist of Five
  • Other Task Estimation Techniques

OUTPUTS

  • [ ] Effort Estimated Task List*
  • Updated Task List
  • [ ] Length of Sprint*
  • Previous Sprint Velocity
  • Dependencies
  • Team Calendar

TOOLS

  • [ ] Sprint Planning Meetings*
  • Sprint Tracking Tools: Velocity, Business Value Delivered, Number of Stories, ect
  • Sprint Tracking Metrics

OUTPUTS

  • [ ] Sprint Backlog*
  • [ ] Sprint Burndown Chart*

Create Deliverables (10.1)

Figure 10-1: Implement Overview Figure 10-2: Implement Overview (Essentials) Figure 10-3: Create Deliverables—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Sprint Backlog*
  • [ ] Scrumboard*
  • [ ] Impediment Log*
  • Release Planning Schedule
  • Dependencies
  • Scrum Guidance Body Recommendations

TOOLS

  • [ ] Team Expertise*
  • Software
  • Other Development Tools: (Refactoring, Design Patterns)
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Sprint Deliverables*
  • [ ] Updated Scrumboard*
  • [ ] Updated Impediment Log*
  • Unapproved Change Requests
  • Identified Risks
  • Mitigated Risks
  • Updated Dependencies

Conduct Daily Standup (10.2)

INPUTS

  • [ ] Scrum Team*
  • [ ] Scrum Master*
  • [ ] Sprint Burndown Chart*
  • [ ] Impediment Log*
  • Product Owner
  • Previous Work Day Experience
  • Scrumboard
  • Dependencies

Recommendations

  • [ ] Daily Standup Meeting*
  • [ ] Three Daily Questions*
  • War Room
  • Video Conferencing

OUTPUTS

  • [ ] Updated Sprint Burndown Chart*
  • [ ] Updated Impediment Log*
  • Motivated Scrum Team
  • Updated Scrumboard
  • Unapproved Change Requests OUTPUTS
  • Identified Risks
  • Mitigated Risks
  • Updated Dependencies

Conduct Daily Standup (10.2) TOOLS ???????

  • [ ] Daily Standup Meeting*
  • [ ] Three Daily Questions*

Groom Prioritized Product Backlog (10.3)

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Prioritized Product Backlog*
  • Rejected Deliverables
  • Approved Change Requests
  • Unapproved Change Requests
  • Identified Risks
  • Updated Program Product Backlog
  • Retrospect Sprint Log(s)
  • Dependencies
  • Release Planning Schedule
  • Scrum Guidance Body

TOOLS

  • [ ] Prioritized Product Backlog Review Meetings*
  • Communication Techniques
  • Other Prioritized Product Backlog Grooming Techniques

OUTPUTS

  • [ ] Updated Prioritized Product Backlog*
  • Updated Release Planning Schedule

Figure 10-5: Scrumboard

Conduct Daily Standup (10.2)

Figure 10-6: Conduct Daily Standup—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Team*
  • [ ] Scrum Master*
  • [ ] Sprint Burndown Chart*
  • [ ] Impediment Log*
  • Product Owner
  • Previous Work Day Experience
  • Scrumboard
  • Dependencies

TOOLS

  • [ ] Daily Standup Meeting*
  • [ ] Three Daily Questions*
  • War Room
  • Video Conferencing

OUTPUTS

  • [ ] Updated Sprint Burndown Chart*
  • [ ] Updated Impediment Log*
  • Motivated Scrum Team
  • Updated Scrumboard
  • Unapproved Change Requests
  • Identified Risks
  • Mitigated Risks
  • Updated Dependencies

Three Daily Questions* Daily Standup Meeting What did I complete yesterday? What will I complete today? What impediments or obstacles (if any) am I currently facing?

Groom Prioritized Product Backlog (10.3)

Figure 10-8: Groom Prioritized Product Backlog—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Prioritized Product Backlog*
  • Rejected Deliverables
  • Approved Change Requests
  • Unapproved Change Requests
  • Identified Risks
  • Updated Program Product

Backlog

  • Retrospect Sprint Log(s)
  • Dependencies
  • Release Planning Schedule
  • Scrum Guidance Body

Recommendations

Recommendations TOOLS

  • [ ] Prioritized Product Backlog Review Meetings*
  • Communication Techniques
  • Other Prioritized Product Backlog Grooming Techniques

OUTPUTS

  • [ ] Updated Prioritized Product Backlog*
  • Updated Release Planning Schedule

Other Prioritized Product Backlog Grooming Techniques Some other Prioritized Product Backlog Grooming tools include many of the same tools used for the following processes: Develop Epic(s)—Described in section 8.4.2. Create Prioritized Product Backlog—Described in section 8.5.2. Conduct Release Planning—Described in section 8.6.2. Create User Stories—Described in section 9.1.2. Approve, Estimate, and Commit User Stories—Described in section 9.2.2. Create Tasks—Described in section 9.3.2. Estimate Tasks—Described in section 9.4.2.

Convene Scrum of Scrums (11.1)

Figure 11-1: Review and Retrospect Overview Figure 11-2: Review and Retrospect Overview (Essentials) Figure 11-3: Convene Scrum of Scrums—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Master or Scrum Team Representatives*
  • Chief Scrum Master
  • Chief Product Owner
  • Meeting Agenda
  • Impediment Log
  • Dependencies
  • Outputs from Retrospect Sprint

TOOLS

  • [ ] Scrum of Scrums Meeting*
  • [ ] Four Questions per Team*
  • Video Conferencing
  • Meeting Room
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Better Team Coordination*
  • Resolved Issues
  • Updated Impediment Log
  • Updated Dependencies

11.1.2.2 Four Questions per Team* Each Scrum Team representative will provide updates from his or her team in turn. These updates are usually provided in the form of answers to four specific questions. 1) What has my team been working on since the last meeting? 2) What will my team do until the next meeting? 3) What were other teams counting on our team to finish that remains undone? 4) What is our team planning on doing that might affect other teams?

Demonstrate and Validate Sprint (11.2)

Figure 11-5: Demonstrate and Validate Sprint—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Core Team*
  • [ ] Sprint Deliverables*
  • [ ] Sprint Backlog*
  • [ ] Done Criteria*
  • [ ] User Story Acceptance Criteria*
  • Stakeholder(s)
  • Release Planning Schedule
  • Identified Risks
  • Dependencies
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Sprint Review Meetings*
  • Earned Value Analysis
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Accepted Deliverables*
  • Rejected Deliverables
  • Updated Risks
  • Earned Value Analysis Results
  • Updated Release Planning Schedule
  • Updated Dependencies

Retrospect Sprint (11.3)

Figure 11-7: Retrospect Sprint—Inputs, Tools, and Outputs

INPUTS

  • [ ] Scrum Master*
  • [ ] Scrum Team*
  • [ ] Outputs from Demonstrate and Validate Sprint*
  • Product Owner
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Retrospect Sprint Meeting*
  • ESVP (Explorer—Shopper—Vacationer—Prisoner (ESVP))
  • Speed Boat
  • Metrics and Measuring (See List)
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Agreed Actionable Improvements*
  • Assigned Action Items and Due Dates
  • Proposed Non-Functional Items for Prioritized Product Backlog
  • Retrospect Sprint Log(s)
  • Scrum Team Lessons Learned
  • Updated Scrum Guidance Body Recommendations

11.3.2.1 Retrospect Sprint Meeting* 1) Things the team needs to keep doing: best practices 2) Things the team needs to begin doing: process improvements 3) Things the team needs to stop doing: process problems and bottlenecks

Ship Deliverables (12.1)

Figure 12-2: Release Overview (Essentials) Figure 12-3: Ship Deliverables—Inputs, Tools, and Outputs

INPUTS

  • [ ] Product Owner*
  • [ ] Stakeholder(s)*
  • [ ] Accepted Deliverables*
  • [ ] Release Planning Schedule*
  • Scrum Master
  • Scrum Team
  • User Story Acceptance Criteria
  • Piloting Plan
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Organizational Deployment Methods*
  • Communication Plan

OUTPUTS

  • [ ] Working Deliverables Agreement*
  • Working Deliverables
  • Product Releases (Release Content, Release Notes)

Retrospect Project (12.2) ??????

Figure 12-1: Release Overview

INPUTS

  • [ ] Product Owner*
  • [ ] Stakeholder(s)*
  • [ ] Accepted Deliverables*
  • [ ] Release Planning Schedule*
  • Scrum Master
  • Scrum Team
  • User Story Acceptance Criteria
  • Piloting Plan
  • Scrum Guidance Body

Recommendations

TOOLS

  • [ ] Organizational Deployment Methods*
  • Communication Plan

OUTPUTS

  • [ ] Working Deliverables Agreement*
  • Working Deliverables
  • Product Releases

Retrospect Project (12.2) ???????

Figure 12-5: Retrospect Project—Inputs, Tools, and Outputs

  • [ ] Scrum Core Team(s)*
  • Chief Scrum Master
  • Chief Product Owner
  • Stakeholder(s)
  • Scrum Guidance Body Recommendations

TOOLS

  • [ ] Retrospect Project Meeting*
  • Other Tools for Retrospect Project
  • Scrum Guidance Body Expertise

OUTPUTS

  • [ ] Agreed Actionable Improvements*
  • [ ] Assigned Action Items and Due Dates*
  • Proposed Non-Functional Items for Program Product Backlog and Prioritized Product Backlog
  • Updated Scrum Guidance Body Recommendations

12.2.2.2 Other Tools for Retrospect Project Explorer—Shopper—Vacationer—Prisoner (ESVP) exercise Speed Boat Metrics and Measuring Techniques

results matching ""

    No results matching ""