Complete Agile Scrum Management: Scrum Master

Explore the scrum team and its three roles—product owner, scrum master, and development team—and how they collaborate to manage the product backlog and deliver customer value through cross-functional, self-organizing work.

Learn the core scrum events, including sprint planning to select features, daily scrums for progress, sprint review for customer feedback, and sprint retrospective for improvements, plus release planning.

Learn how user stories capture customer needs as simple, role-based sentences, define acceptance criteria and definition of done, and guide backlog prioritization in agile scrum.

Learn how product owners gather requirements by interviewing customers, clarifying problems, identifying user personas, and shaping user stories and backlog for prioritized releases.

Discover how release planning selects market-ready increments from the product backlog by prioritizing must, should, and could user stories to meet customer needs.

Lead sprint planning by turning the updated product backlog into a sprint plan, selecting stories by velocity, and breaking them into developer tasks to deliver a usable increment.

Explain how the sprint backlog, a subset of the product backlog managed by the development team, defines what to do and how to achieve the increment, with evolving design.

Learn how story points define the effort, time, complexity, and risk of user stories, and how teams use planning poker, Fibonacci scales, and relative estimation to plan sprints.

velocity is the number of completed story points per sprint, used to estimate progress. average velocity from past sprints helps predict how many sprints, duration, and cost the project requires.

Recap sprint planning where development team selects user stories from product backlog to deliver a sprint increment. They use planning poker to estimate story points and plan with velocity.

Lead the daily scrum to review what was done, plan what will be done, surface issues, and update the sprint backlog, task board, and burn down chart to track progress.

Explain the product increment as the releasable outcome of the sprint, comprising completed items from the current and previous sprint, ready to present to the customer.

During the sprint review, the development team demonstrates the product increment to the product owner and customer, discusses backlog status, and captures customer feedback for the next sprint.

Drive continuous improvement through an internal sprint retrospective that inspects team performance, reviews communication, tools, and processes, and plans the next sprint with the product owner.

Recap the Scrum framework by detailing product owner interactions with the customer, product backlog, velocity, release planning, sprint backlog, and describe the sprint cycle with daily meetings and sprint review.

Identify and assess risks early, recognizing that risks include threats and opportunities. Plan responses such as mitigate, transfer, avoid, accept, exploit, and monitor with an impact-likelihood matrix.

Explore popular agile project management software like monday.com and Primavera to implement agile frameworks and manage your project with an agile approach.