SBOK Scrum Body of Knowledge

Reference manual of SCRUM Body of Knowledge

Get Started. It's Free
or sign up with your email address
Rocket clouds
SBOK Scrum Body of Knowledge by Mind Map: SBOK Scrum Body of Knowledge

1. Aspects

1.1. Organization

1.1.1. Core Roles

1.1.1.1. Product Owner

1.1.1.1.1. Responsible for achieving maximum business value for project

1.1.1.1.2. Articulates customer requirements

1.1.1.1.3. Maintains business justification for a project

1.1.1.1.4. Represent customer's voice

1.1.1.2. Scrum Master

1.1.1.2.1. Ensures that Scrum Team has an appropriate environment

1.1.1.2.2. Guides, facilitates and teaches Scrum practices

1.1.1.2.3. Clears impediments for the team

1.1.1.2.4. Ensures that Scrum processes are being followed

1.1.1.3. Scrum Team

1.1.1.3.1. Responsible for understanding Product Owner specified requirements

1.1.1.3.2. Creating the project deliverables

1.1.2. Non Core Roles

1.1.2.1. Stakeholders

1.1.2.1.1. Customers, Users and Sponsors

1.1.2.1.2. Interface with the Scrum Core Team

1.1.2.1.3. Influence the project throughout

1.1.2.1.4. Project produces the collaborative benefits

1.1.2.2. Scrum Guidance Body (SGB)

1.1.2.2.1. Set of Documents or group of experts

1.1.2.2.2. Involved with defining objectives

1.1.2.2.3. Guides the work carried out by the Product Owner, Scrum Master, Scrum Team

1.1.2.3. Vendors

1.1.2.3.1. External Individuals or Internal Organization

1.1.2.3.2. Provice products and services that are not within the core competencies of the project organization

1.1.2.4. Chief Product Owner

1.1.2.4.1. In bigger projects has multiple Scrum Teams

1.1.2.4.2. Responsible for coordinating work of multiple Product Owners

1.1.2.5. Chief Scrum Master

1.1.2.5.1. Coordinates Scrum-related activities in large projects which requires multiple Scrum teams to work in parallel

1.2. Business Justification

1.2.1. Value-driven delivery

1.2.2. Uncertain of results or outcomes

1.2.3. Impossible to guarantee Project's success and completion

1.2.4. Scrum attempts to start delivering results as early in the project as possible

1.2.5. This provides an opportunity for reinvestment

1.2.6. Allows the Project's objectives and processes to change in case of business justification changes

1.3. Quality

1.3.1. Scrum adopts an approach of continuous improvement

1.3.2. The team learns from experience and stakeholder engagement to constantly keep the Prioritized Product Backlog

1.3.3. The Prioritized Product Backlog is simply never complete until the closure or termination of the project

1.3.4. Changes to requirements reflect changes in the internal and external business environment

1.3.5. Requires work to be completd in an incremental fashion through Sprints

1.3.6. Due to this, errors are fixed right away

1.3.7. Quality-related tasks are completed as part of the same Sprint

1.3.8. Ensures that quality is inherent in any deliverable created as part of a Sprint

1.3.9. Continuous improvement with repetitive testing optimizes the probability of achieving the expected quality levels

1.3.10. Constant discussions between the Scrum Core Team and stakeholders including customers and users

1.3.11. Ensures that the gap between customers expectations from the project ans actual deliverables produced in constantly reduced

1.4. Change

1.4.1. Stakeholder may change thir mind about what they want during the course of the project

1.4.2. It is not always feasible for stakeholdres to define requirements during project initiation

1.4.3. SCRUM welcomes change by using short iterative sprints

1.4.4. It enables customers to regularly interact with Scrum Team members and view deliverables as they are ready and event o change requirements if needed

1.5. Risk

1.5.1. Positive impact / Opportunities

1.5.2. Negative impact / Threats

1.5.3. Managing risk must be done proactively

1.5.4. It is an iterative process that should begin at project initiation and continue throughout the project's lifecycle

1.5.5. Risk management should follow standardized steps to ensure risks

1.5.5.1. Identified

1.5.5.2. Evaluated

1.5.5.3. Proper course of action is determined upon and acted upon

1.5.6. Risks should be identified, assessed, and responded to, based on two factors. Risk with a high probability and impact value are determined by multiplying both factors. Once a risk is identified, it is important to understand the risk.

1.5.6.1. The possible impact in the event of such occurrence

1.5.6.2. The probability of each risk's occurrence

2. Principles

2.1. Empirical Process Control

2.1.1. Transparency

2.1.1.1. Artifacts

2.1.1.1.1. Project Vision Statement

2.1.1.1.2. Prioritized Product Backlog

2.1.1.1.3. Release Planning Schedule

2.1.1.2. Meetings

2.1.1.2.1. Sprint Review Meetings

2.1.1.2.2. Daily Standup Meetings

2.1.1.3. Information Radiators

2.1.1.3.1. Burndown Chart

2.1.1.3.2. Scrumboard

2.1.2. Inspection

2.1.2.1. Scrumboard

2.1.2.2. Frequent Feedback

2.1.2.3. Final inspection

2.1.3. Adaptation

2.1.3.1. Daily Standup Meetings

2.1.3.1.1. Scrum Team members openly discuss impediments to completing their taks

2.1.3.1.2. After the meeting the Scrum Master coordinate help from other team members

2.1.3.1.3. Mentor those with relatively less experience in knowledge of the project or technology

2.1.3.1.4. When the needed resource does not reside within the team, the Scrum Master will acquire it externatlly

2.1.3.2. Constant Risk Identification

2.1.3.2.1. Create Prioritized

2.1.3.2.2. Groom Prioritized Product Backlog

2.1.3.2.3. Create Sprint Backlog

2.1.3.3. Change Requests

2.1.3.3.1. Develop Epic (s)

2.1.3.3.2. Create Prioritized Product Backlog

2.1.3.3.3. Groom Prioritized Product Backlog processes

2.1.3.4. Scrum Guidance Body

2.1.3.4.1. Create User Stories

2.1.3.4.2. Estimate Tasks

2.1.3.4.3. Create Deliverables

2.1.3.4.4. Groom Prioritized Product Backlog processes

2.1.3.4.5. Guidance and also provide expertise as required for the team to adapt do necessary changes and challenges

2.1.3.5. Retrospect Sprint Meetings

2.1.3.6. Retrospect Project Meetings

2.2. Self Organization

2.2.1. Focuses on Today's workers

2.2.2. Self-organize rather than command and control

2.2.3. Goals of a Self-organized Team

2.2.3.1. Understand the Project Vision

2.2.3.2. Leverage on cross functional team expertise

2.2.3.3. Proactively seek work

2.2.3.4. Execute work themselves

2.2.3.5. Open to learning new things

2.2.3.6. Continuously upgrade knowledge and skills

2.2.3.7. Delivery tangible results

2.3. Collaboration

2.3.1. Awareness

2.3.2. Articulation

2.3.3. Appropriation

2.3.4. Advocates project management as a shared value-creation process

2.4. Value based Priorization

2.4.1. Maximum business value

2.5. Time-Boxing

2.5.1. Sprints

2.5.2. Daily Standup Meetings

2.5.3. Sprint Planning Meetings

2.5.4. Sprint Review Meetings

2.6. Iterative Development

2.6.1. Manage changes better

2.6.2. Build projects that satisfy customer needs

3. Processes

3.1. Initiate

3.1.1. 1 - Create Project Vision

3.1.1.1. Project Business is reviewed to create Project Vision Statement

3.1.1.2. Product Owner is Identified

3.1.2. 2 - Identify Scrum Master and Stakeholder

3.1.2.1. Scrum Master is Identified

3.1.3. 3 - Form Scrum Team

3.1.3.1. Scrum Team members are identified

3.1.3.2. Product Owner responsible for selecting team members, often does so in collaboration with the Scrum Master

3.1.4. 4 - Develop Epics

3.1.4.1. Project Vision Statement serves as the basis for developing Epic

3.1.4.2. User Group Meetings may be held to develop Epic(s)

3.1.5. 5 - Create a Prioritized Product Backlog

3.1.5.1. Epic(s) and Unrefined User Stories refined and elaborated and prioritized to create a Prioritized Product Backlog

3.1.5.2. Done Criteria is also established

3.1.6. 6 - Conduct Release Planning

3.1.6.1. Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule

3.2. Project Plan and Estimate

3.2.1. 7 - Create User Stories

3.2.1.1. User Stories and their related User Story Acceptance Criteria are created

3.2.1.2. Usually written by the Product Owner

3.2.1.3. Designed to ensure that the customer's requirement are clearly depicted and understood

3.2.1.4. Involves Scrum Team members creating User Stories

3.2.1.5. Users Stories are incorporated in Prioritized Product Backlog

3.2.2. 8 - Approve, Estimate and Commit User Stories

3.2.2.1. Product Owner approves User Stories for a sprint

3.2.2.2. Scrum Master and Scrum Team estimate the effort required

3.2.2.3. Scrum Team commits to develop the customer requirements in the form of Approved, Estimated, and Committed User Stories

3.2.3. 9 - Create Tasks

3.2.3.1. The approved, Estimated, and User Stories are broken down and compiled into a Task List

3.2.3.2. Task Planning Meeting is held

3.2.4. 10 - Estimate Tasks

3.2.4.1. Scrum Core Team, in a Task Estimation Workshop, estimates effort required to a accomplish each in the Task List

3.2.4.2. Restult of this process is an Effort Estimated Task List

3.2.5. 11 - Create Sprint Backlogs

3.2.5.1. The Scrum Core Team holds Sprint Planning Meetings

3.2.5.2. Sprint Backlog containing all tasks to be completed in the sprint is created

3.3. Implement

3.3.1. 12 - Create Deliverables

3.3.1.1. Scrum Team works on the tasks in the Sprint Backlog to create Sprint Deliverables

3.3.1.2. Scrumboard is often used to track the work and activities being carried out

3.3.1.3. Issues or problems being faced by the Scrum Team could be updated in an Impediment Log

3.3.2. 13 - Conduct Daily Standup

3.3.2.1. Every day a highly focused time-boxed meeting is conducted referred to as the Daily Standup meeting

3.3.2.2. It's a forum for the Scrum Team update each other on their progress and impediments

3.3.3. 14 - Groom Prioritized Product Backlog

3.3.3.1. The Prioritized Product Backlog is continuously updated and maintained

3.3.3.2. Prioritized Product Backlog Review Meeting may be held

3.3.3.3. Any changes or updates to the backlog are discussed and incorporated into the Prioritized Product Backlog

3.4. Review and Retrospect

3.4.1. 15 - Convene Scrum of Scrums

3.4.1.1. Scrum Teams representatives convene for Scrum of Scrum Meetings

3.4.1.2. They collaborate and track their respective progress, impediments and dependencies across teams

3.4.1.3. Relevant only for large projects where multiple Scrum Teams are involved

3.4.2. 16 - Demonstrate and Validate Sprint

3.4.2.1. Scrum Team demonstrates the Sprint Deliverables

3.4.2.2. The purpose of this meeting is to secure approval and acceptance of the product or service by the product owner

3.4.3. 17 - Retrospect Sprint

3.4.3.1. Scrum Master and Scrum Team meet to discuss the lessons learned

3.4.3.2. Discuss negative and positive points observed on the last Sprint

3.4.3.3. Information is recorded as lessons learned which can be applied to future Sprints

3.4.3.4. There may be Agreed Actionable Improvements or Update Scrum Guidance Body Recommendations

3.5. Release

3.5.1. 18 - Ship Deliverables

3.5.1.1. Accepted Deliverables are delivered or transmitted

3.5.1.2. A formal Working Deliverables Agreement documents the successful completion of the Sprint

3.5.2. 19 - Retrospect Project

3.5.2.1. Organizational stakeholders and Scrum Core Team members assemble to retrospect the project

3.5.2.2. Identify, document and internalize the lessons learned

3.5.2.3. Lessons led to documentation of Agreed Actionable Improvements to be implemented in future projects