Scrum: Become a Certified Scrum Master

Explore the different roles of Scrum and learn how Scrum works by examining its core mechanics and team responsibilities.

Identifies the three scrum roles—product owner, scrum master, and development team—and explains how the product owner prioritizes the backlog, the scrum master coaches, and the team is self-organizing.

Learn how scrum uses four week sprints, product and sprint backlogs, and ceremonies: sprint planning, daily scrum, sprint review, and sprint retrospective to deliver a potentially shippable product increment.

We summarize the Scrum roles—the product owner, the development team, and the Scrum master—and their collaboration through a four-week sprint cadence of planning, daily scrum, execution, demo, review, and retrospective.

Explore Scrum basics, manage project uncertainty as risk, embrace agility and learning, control work in progress (WIP), and measure progress by completed value while balancing quality, speed, and cost.

Learn how Scrum addresses uncertainty and risk in projects by embracing change through iterative and incremental development, using short sprints to deliver valuable increments from the product backlog.

Embrace agility and adaptation by deciding at the last responsible moment, using just in time planning and adaptive exploration to manage changes and reduce costs of late changes in Scrum.

Embrace change through experiential learning, fail fast in a safe team environment, and test assumptions quickly while inspecting and adapting via daily scrum, sprint review, and retrospective.

Limit the work in progress to keep the team's flow and finish items quickly. Enable the scrum master to provide the team with necessary information, reducing waiting and task switching.

Measure value by validation and deliver software that customers can use, not work alone. Scrum uses sprint planning, reviews, and retrospectives to adapt to feedback and deliver value from backlog.

Explore how quality equals conformance and fitness for use, and how Scrum balances fast delivery with feedback through sprint reviews and minimally sufficient ceremonies and documentation.

Embrace uncertainty as risk, apply agility through Scrum, sprint reviews, and retrospectives; limit work in progress and focus on one feature at a time, measuring progress by quality and speed.

Explore time boxing in scrum, using small bites of planning and execution to keep sprints in flow, avoid task switching, and deepen the definition of done.

Use timeboxes to define fixed durations for scrum ceremonies and sprints, improving predictability, prioritization, progress visibility, and team motivation.

Master planning and execution with compact sprint cycles, planning only the next chunk of work, executing for 1–4 weeks, and iterating via review and retrospective for rapid feedback.

Set a consistent sprint duration, such as two weeks, and stick with it; define a sprint goal with mutual team commitment, and avoid mid-sprint changes to the sprint backlog.

Keep the sprint backlog stable and route new requirements to the product backlog while focusing on the sprint goal; early changes are cheaper and preserve cadence for reviews.

Define the definition of done with the Scrum team so the increment could be released, meeting design, code, testing, and acceptance criteria.

Learn how time boxes drive sprints, plan and execute in small blocks, keep fixed sprint durations, manage backlog changes, and map the definition of done to the sprint goal.

Explore the product owner role, responsibilities, and ideal skill set, including managing the product backlog and sprint activities, with a focus on team collaboration and unusual scenarios.

The product owner bridges business stakeholders and end users, prioritizing the backlog to deliver maximum business value.

The product owner brings industry knowledge and emotional intelligence to anticipate unknown unknowns, align with mission, negotiate priorities, and balance return on investment with value.

Manage portfolio planning, envisioning, release and sprint planning, and ongoing grooming to deliver product backlog increments; collaborate with stakeholders, analysts, and the Scrum Master through the sprint cycle.

Blend product management, business domain knowledge, and technical fluency to embody the ideal product owner who voices customer value and guides the backlog across internal or outsourced teams.

Explore the product owner as a team approach, the risks of proxy and multiple product owners, and why empowered product owners reduce delays and avoid communication bottlenecks.

Explore the product owner's roles, day-to-day activities, and ideal candidate attributes, highlighting emotional intelligence, cross-team communication, and active participation in sprint ceremonies and backlog grooming.

Meet the scrum master as a coach and guide for the team. Learn roles, responsibilities, skills, daily activities, and how the master interacts with the development team and product owner.

Explore the Scrum Master roles and responsibilities as a coach and facilitator guiding the development team and product owner to follow the Scrum framework through servant leadership and remove impediments.

The scrum master blends technical and business understanding to support the development team, question ROI, and collaborate with the product owner while protecting the team through transparency, inspection, and adaptation.

Explore how a Scrum Master guides early framework adherence, removes impediments, supports daily scrums, and collaborates with the product owner across backlog grooming and ceremonies.

Identify ideal scrum master candidates, such as project managers from predictive environments or technical leads transitioning to management, embracing servant leadership, coaching, and removing impediments to foster self-organizing teams.

Develop proficiency in scrum master roles and responsibilities, coordinating sprint planning, daily scrums, reviews, and retrospectives, removing impediments, and communicating with product owners, the development team, and stakeholders.

Explore the development team within the Scrum framework, detailing its roles, responsibilities, required skill sets, and key characteristics of its members.

The development team functions as a generalising specialist across roles, grooming the backlog, planning sprints, the daily scrum, and delivering a potentially shippable product increment through reviews and retrospectives.

Develop a self-organizing, cross-functional development team of t-shaped people, right-sized for a sustainable pace, focused on delivering quality and business value while avoiding burnout.

Avoid multitasking and excessive work in progress to prevent task switching and hinder productivity. Maintain a sustainable pace with four-week iterations to prevent burnout and maximize value.

Understand the development team's roles, responsibilities, and diverse skill sets, the forming, storming, norming, performing journey, and the need for emotional intelligence from the product owner and Scrum Master.

Explore how the product owner, Scrum master, and development team collaborate within the Scrum team, and how multiple teams coordinate on large projects.

Explore how feature and component teams divide a project into features and subsystems, with a product owner coordinating backlogs and DODs to deliver a cohesive product.

Slice large projects into multiple component teams, run daily scrums and a scrum of scrums, align releases on a release train with the same sprint length and release map.

Explore the roles of product owner, Scrum master, and development team; chunk work into features, coordinate multiple Scrum teams, plan releases, and accelerate return on investment.

Learn how Scrum guides requirements gathering, progressive elaboration, and refinement, document user stories with Invest principles, address non functional requirements, and prepare the product backlog for sprint execution.

Gather and prioritize requirements iteratively in Scrum, embracing change with a flexible scope and fixed cost and schedule, using the product backlog and sprint review to refine work.

Progressive elaboration turns big ideas into precise requirements over time through backlog refinement and sprint reviews, with agile welcoming changes as knowledge grows.

User stories capture requirements from the user’s perspective using the three C’s (card, conversation, confirmation). They support sprint planning, definition of done, and testing, and distinguish epics, features, and themes.

Apply the invest criteria to craft user stories that are independent, negotiable, valuable, estimable, sized appropriately, and testable for the DOD and enable clear sprint planning in Scrum.

Identify and document nonfunctional requirements—security, capacity, compatibility, maintainability, scalability, usability—and integrate them into the prioritized backlog and definition of done, with testing considerations.

Elaborate requirements progressively through epic features and the definition of done, plan and review sprints, and balance product owner guidance with prototyping, spikes, and exploration to deliver value.

Explore agile story creation methods in Scrum, including story writing workshops and story maps, with personas as an option, to capture requirements, goals, and the definition of done.

Master the basics of requirements, user stories, and invest for the product backlog, while exploring story maps and personas to enhance story creation methods.

Explore how to create and groom the product backlog with input from the product owner, Scrum master, and development team, define ready vs done, achieve flow, and manage multiple backlogs.

Learn how the product backlog drives Scrum, prioritizing user stories, defects, and nonfunctional requirements, with story points guiding sizing and progressive refinement.

Product owners groom the backlog by refining, prioritizing, and estimating items, breaking epics into stories, and keeping priorities aligned with customer needs.

The definition of ready ensures stories are prioritized in the product backlog and ready to enter the sprint backlog with DoD and acceptance criteria.

Understand how the sprint cadence flows from the product backlog through product owner and development team collaboration, with the Scrum Master protecting focus and maintaining a ready backlog pipeline.

Advocate for one product backlog per project, avoiding multiple backlogs that cause overlap and mess. Teams may segment within a single backlog, but beware replication of effort and risk.

Prioritize and groom product backlog with the product owner, development team, stakeholders. Define sprint goal, reach definition of ready, and flow user stories and non functional requirements into execution.