📖 About this Domain
This domain details the core and non-core roles within the Scrum framework as prescribed by the SBOK® Guide. It defines the specific responsibilities and authority levels for the Product Owner, Scrum Master, and Scrum Team. Understanding these role distinctions is fundamental for Scrum project execution.
🎓 What You Will Learn
- You will learn the Product Owner's function in maximizing business value and managing the Prioritized Product Backlog.
- You will understand the Scrum Master's role as a servant-leader, facilitator, and impediment remover.
- You will comprehend the characteristics of the Scrum Team as a self-organizing and cross-functional unit.
- You will identify non-core roles like Stakeholders and the Scrum Guidance Body and their interaction points.
🛠️ Skills You Will Build
- You will build the skill to accurately differentiate the accountabilities between the Product Owner and Scrum Master.
- You will develop the ability to recognize and apply servant-leadership principles in a Scrum context.
- You will learn to map stakeholder requirements and communication to the correct core Scrum role.
- You will acquire the skill to foster team empowerment by respecting the boundaries of a self-organizing team.
💡 Top Tips to Prepare
- Memorize the precise list of responsibilities for each core role directly from the SBOK® Guide.
- Study the collaboration patterns between the Product Owner, Scrum Master, and Scrum Team.
- Use flashcards to distinguish between core roles (mandatory) and non-core roles (optional).
- Practice exam questions that present scenarios and ask you to identify the responsible role.
📖 About this Domain
The Implement Phase details the processes for creating the product's deliverables. In this phase, the Scrum Team executes tasks from the Sprint Backlog to develop a potentially shippable product increment.
🎓 What You Will Learn
- The Create Deliverables process, where the Scrum Team works on tasks to generate the Sprint Deliverables.
- How to Conduct the Daily Standup, a time-boxed meeting for team synchronization and impediment tracking.
- The Groom Prioritized Product Backlog process, an ongoing activity to refine and estimate items for future Sprints.
🛠️ Skills You Will Build
- Managing the Scrumboard and Sprint Burndown Chart to monitor Sprint progress.
- Facilitating the Daily Standup meeting to ensure it remains within its 15-minute time-box.
- Maintaining the Impediment Log to track and remove blockers identified by the Scrum Team.
- Applying estimation techniques during Prioritized Product Backlog Grooming sessions.
💡 Top Tips to Prepare
- Master the Inputs, Tools, and Outputs (ITOs) for the Create Deliverables and Conduct Daily Standup processes.
- Clearly distinguish the role of the Scrum Master as a facilitator, not a manager, during this phase.
- Understand the three core questions answered by the Scrum Team during the Daily Standup.
- Focus on how the Groom Prioritized Product Backlog process ensures the backlog is ready for the next Sprint Planning Meeting.
📖 About this Domain
The Initiate phase is the first phase in a Scrum project as per the SBOK Guide, encompassing processes related to project initiation. It establishes the business justification, creates a project vision, and secures initial funding and commitment.
🎓 What You Will Learn
- You will learn the six processes of the Initiate phase, starting from Create Project Vision to Conduct Release Planning.
- You will understand how to identify the Scrum Master and Stakeholders, and the criteria for forming a cross-functional Scrum Team.
- You will learn to develop Epics from the Project Vision and create the initial Prioritized Product Backlog.
- You will grasp the inputs, tools, and outputs (ITOs) for each process within this phase, including the Project Vision Statement and Release Planning Schedule.
🛠️ Skills You Will Build
- You will build the skill to facilitate a Project Vision Meeting and draft a comprehensive Project Vision Statement.
- You will develop competency in stakeholder analysis and mapping to manage expectations effectively.
- You will acquire the ability to guide the Product Owner in creating and prioritizing User Stories for the initial backlog.
- You will gain proficiency in conducting Release Planning sessions to create a high-level project timeline.
💡 Top Tips to Prepare
- Memorize the specific inputs, tools, and outputs for all six processes in the Initiate phase as they are frequently tested.
- Clearly differentiate the roles and responsibilities of the Product Owner, Scrum Master, and Sponsor during project initiation.
- Understand the data flow from the Project Business Case through the Project Vision Statement to the Prioritized Product Backlog.
- Practice exam questions focused on business justification, value-based prioritization, and stakeholder identification.
📖 About this Domain
The Plan and Estimate phase details processes for creating User Stories and estimates. This phase focuses on elaborating requirements and planning the work to be done in a Sprint.
🎓 What You Will Learn
- You will learn the Create User Stories process, including defining Epics and applying the INVEST criteria.
- You will understand the Estimate User Stories process using tools like Planning Poker® and Story Points.
- You will learn the Commit User Stories process, where the Scrum Team finalizes the scope for the Sprint Backlog.
- You will grasp the Create Tasks and Estimate Tasks processes for decomposing stories into actionable items.
🛠️ Skills You Will Build
- You will build proficiency in facilitating Sprint Planning meetings and Backlog Refinement sessions.
- You will develop the skill of applying relative sizing and agile estimation techniques for forecasting.
- You will gain the ability to guide the Scrum Team in creating a realistic Sprint Goal and Sprint Backlog.
- You will master task decomposition, breaking down User Stories into granular tasks for the Development Team.
💡 Top Tips to Prepare
- Memorize the inputs, tools, and outputs for all processes in this phase as per the SBOK® Guide.
- Understand the distinction between the Prioritized Product Backlog and the Sprint Backlog.
- Focus on the specific responsibilities of the Product Owner and Development Team during estimation and commitment.
- Practice applying estimation criteria and understand the value of relative sizing over absolute time estimates.
📖 About this Domain
This domain establishes the foundational knowledge of Agile methodologies and the Scrum framework. It details the Agile Manifesto, its principles, and contrasts Agile with traditional project management models as defined in the SBOK® Guide.
🎓 What You Will Learn
- Grasp the four values and twelve principles of the Agile Manifesto.
- Understand the Scrum framework's three roles, five events, and three artifacts.
- Differentiate Scrum's empirical process from predictive, plan-driven Waterfall approaches.
- Identify key Scrum advantages like transparency, iterative delivery, and continuous improvement.
🛠️ Skills You Will Build
- Articulate the core tenets of the Agile mindset and its application in a project environment.
- Distinguish the Scrum framework from other methodologies like Kanban and XP.
- Apply core Scrum vocabulary including terms like Sprint, Time-boxing, and Definition of Done.
- Analyze and justify the business value of implementing the Scrum framework to stakeholders.
💡 Top Tips to Prepare
- Internalize the Agile Manifesto's values and principles for direct recall during the exam.
- Focus on Chapter 1 of the SBOK® Guide as the definitive resource for this domain.
- Master the three pillars of empirical process control: transparency, inspection, and adaptation.
- Utilize ScrumStudy's official practice questions to validate your comprehension of core concepts.
📖 About this Domain
The Review and Retrospect Phase focuses on the final processes within a Sprint to ensure stakeholder acceptance of the deliverable and to identify process improvements. This phase includes the Demonstrate and Validate Sprint and Retrospect Sprint processes. Its purpose is to inspect the increment and adapt the process for future Sprints.
🎓 What You Will Learn
- You will learn the Demonstrate and Validate Sprint process, where the Scrum Team presents the Done increment to the Product Owner and stakeholders.
- You will understand the Retrospect Sprint process, a formal meeting facilitated by the Scrum Master for the Scrum Team to reflect and improve.
- You will identify key inputs like the Scrum Team and Sprint Backlog, and outputs like Accepted Deliverables and Agreed Actionable Improvements.
- You will recognize tools used in this phase, including the Sprint Review Meeting, Speed Boat, and Metrics and Measuring Techniques.
🛠️ Skills You Will Build
- You will build facilitation skills for conducting effective Sprint Review and Sprint Retrospective meetings.
- You will develop the ability to manage stakeholder engagement and secure formal acceptance of deliverables.
- You will gain proficiency in identifying process inefficiencies and creating Agreed Actionable Improvements.
- You will learn to validate that Done deliverables meet the defined Acceptance Criteria and User Story requirements.
💡 Top Tips to Prepare
- Memorize the specific inputs, tools, and outputs for the Demonstrate and Validate Sprint and Retrospect Sprint processes as defined in the SBOK® Guide.
- Clearly differentiate the purpose and participants of the Sprint Review Meeting from the Sprint Retrospective Meeting.
- Focus on the Product Owner's role in accepting or rejecting deliverables and the Scrum Master's role as a facilitator.
- Study the recommended tools for retrospection, such as Speed Boat and the 4 Questions, as they are common exam topics.
📖 About this Domain
Scaling Scrum covers the framework's application to large projects, programs, and portfolios. It details the coordination of multiple Scrum Teams to deliver integrated products in an enterprise setting. This domain introduces specific roles and processes for managing large-scale agile initiatives.
🎓 What You Will Learn
- You will learn the structure for implementing Scrum on large projects with multiple teams and a Program Product Owner.
- You will understand how to manage programs and portfolios using Scrum, including the specific roles and artifacts involved.
- You will learn the distinct responsibilities of the Chief Product Owner and Chief Scrum Master in a scaled environment.
- You will grasp the recommended steps and considerations for successfully transitioning an entire organization to the Scrum framework.
🛠️ Skills You Will Build
- You will build the skill to coordinate dependencies and communication across multiple, geographically dispersed Scrum Teams.
- You will develop the ability to manage a Program Product Backlog and facilitate large-scale release planning meetings.
- You will gain competence in prioritizing projects at the portfolio level to align with strategic business objectives.
- You will acquire the skill to guide an enterprise-wide agile transformation by applying Scrum transition principles.
💡 Top Tips to Prepare
- Memorize the specific responsibilities of scaled roles like Chief Product Owner, Chief Scrum Master, and Program Scrum Master.
- Map the flow of Epics and User Stories from the Portfolio Backlog down to the individual Team Product Backlogs.
- Focus on the inputs, tools, and outputs for the 'Create Program or Portfolio Components' and 'Review and Update Scrum Guidance Body' processes.
- Clearly differentiate between the management of Scrum at the program level versus the portfolio level as defined in the SBOK Guide.
📖 About this Domain
The Release phase focuses on delivering the Accepted Deliverables to the customer and conducting the Retrospect Project Meeting. This phase ensures the final product is successfully transferred and project knowledge is captured for organizational improvement. It represents the formal closure of the project activities.
🎓 What You Will Learn
- You will learn the Ship Deliverables process, which involves the formal transfer of the final product increment to the customer.
- You will understand the Retrospect Project process, including conducting the meeting to identify improvements for future projects.
- You will identify the key inputs, tools, and outputs (I-T-T-O) for each process within the Release phase as per the SBOK Guide.
- You will grasp the specific responsibilities of the Product Owner and Scrum Master in finalizing and closing the project.
🛠️ Skills You Will Build
- You will build skills in coordinating the final product handover and ensuring all Done Criteria are met for the release.
- You will develop proficiency in facilitating the Retrospect Project Meeting to capture actionable lessons learned.
- You will gain the ability to manage the final project documentation, including updating the Lessons Learned Register.
- You will learn to effectively communicate project closure and value delivery to key stakeholders and the Scrum Guidance Body.
💡 Top Tips to Prepare
- Focus on the I-T-T-O for the Ship Deliverables and Retrospect Project processes, as these are common exam questions.
- Distinguish clearly between the Retrospect Sprint Meeting and the Retrospect Project Meeting in terms of timing and scope.
- Understand the Product Owner's critical role in formally accepting the Final Deliverables before they are shipped.
- Memorize the key outputs of this phase: Final Deliverables, Lessons Learned Register, and updated stakeholder communications.
