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.

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.

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.

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.

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.

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.

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.

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'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.

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.

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

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.

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.

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.