The Scrum Body of Knowledge (SBOK™) provides guidelines for the successful implementation of Scrum—the most popular Agile project management and product development methodology. It provides a comprehensive framework that includes the principles, aspects, and processes of Scrum. Scrum, as defined in the SBOK™, is applicable to the following: • Portfolios, programs, and/or projects in any…
The Scrum Body of Knowledge (SBOK™) provides guidelines for the successful implementation of Scrum—the most popular Agile project management and product development methodology. It provides a comprehensive framework that includes the principles, aspects, and processes of Scrum.
Scrum, as defined in the SBOK™, is applicable to the following:
• Portfolios, programs, and/or projects in any industry
• Products, services, or any other results to be delivered to stakeholders
• Projects of any size or complexity
The term “product” in this Body of Knowledge may refer to a product, service, or other deliverable. Scrum can be applied effectively to any project in any industry—from small projects or teams with as few as six team members to large, complex projects with up to several hundred team members.
This first chapter describes the purpose and framework of the SBOK™ and provides an introduction to the key concepts of Scrum. It contains a summary of Scrum principles, Scrum aspects and Scrum processes. Chapter 2 expands on the six Scrum principles which are the foundation on which the Scrum framework is based. Chapters 3 through 7 elaborate on the five Scrum aspects that must be addressed throughout any project: organization, business justification, quality, change, and risk. Chapters 8 through 12 cover the 19 Scrum processes involved in carrying out a Scrum project. These processes are part of the 5 Scrum phases: Initiate; Plan and Estimate; Implement, Review and Retrospect; and Release. These phases describe in detail the associated inputs and outputs of each process, as well as the various tools that may be used in each. Some inputs, tools, and outputs are mandatory and are indicated as such; others are optional depending on the specific project, organizational requirements, and/or guidelines set forth by the organization’s Scrum Guidance Body (SGB). Finally, Appendix A contains an overview of The Agile Manifesto (Fowler and Highsmith, 2001) and a discussion of various Agile methods for those who want more information about Agile.
In the mid 80’s, Hirotaka Takeuchi and Ikujiro Nonaka defined a flexible and all-inclusive product development strategy where the development team works as a unit to reach a common goal. They described an innovative approach to product development that they called a holistic or “rugby” approach, “where a team tries to go the distance as…
Although there are similarities in Scrum and traditional project management methods with regard to definition of ‘quality’ (i.e., the ability of the product to meet the agreed Acceptance Criteria and achieve the business value expected by the customer), differences exist in terms of how the approaches address the implementation and achievement of the required quality…
There are a number of HR theories that are useful in an organization that applies Scrum. The following is a discussion on some popular HR theories relevant to Scrum. Tuckman’s Model of Group Dynamics The Scrum approach and method may initially seem quite different and difficult for a new Scrum Team. A new Scrum Team,…
The Release Phase has two processes: Ship Deliverables: 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. Retrospect Project: In this process, which completes the project, organizational stakeholders and Scrum Core Team members assemble to retrospect the project and…
Scrum is flexible, transparent and iterative, making it very different from complex traditional project management methodologies. In this article, we will look at the various areas in which Scrum differs from other methods. Organization structure and definition of roles and associated responsibilities are some of the areas where Scrum differs in a major way from…
After a project is over, it is important that the Scrum team and the stakeholders look back and discuss the lessons learnt during the course of the project. This in itself is a process, called the Retrospect project, which comes right after the deliverables are shipped. The Release phase emphasizes delivering the Accepted Deliverables to…
In the previous posts, we discussed the roles in Scrum, and their desired traits. Now let’s have a summary of the responsibilities of each role in a Scrum project. The table given below provides a crisp outline of responsibilities of the Scrum roles. Role Responsibilities Scrum Guidance Body Establishes overall guidelines and metrics for…
How is the Retrospect Sprint Meeting related to the ‘inspect-adapt’ aspect of Scrum? The Retrospect Sprint Meeting is an important element of the ‘inspect-adapt’ Scrum framework and it is the final step in a Sprint. All Scrum Team members attend the meeting, which is facilitated or moderated by the Scrum Master. It is recommended, but…
