Agile Scrum Master Certification: Scrum Project Management

Explore the agile mindset and the four core values of the Agile Manifesto—individuals and interactions, working software, customer collaboration, and responding to change—for practical team impact.

Explore the foundational 12 agile principles and the agile mindset, focusing on customer collaboration, embracing change, frequent delivery, co-located teams, working software, and continuous improvement.

Apply scrum as an empirical process control to balance iterative and incremental delivery with frequent reviews and backlog adaptation. Lean thinking reduces waste and guides delivering in small increments.

Explore empiricism as the basis of scrum, showing fact-based, experience-based decisions informed by constant team, constant sprint length, and constant work type, guided by Tuckman's forming to performing stages.

Learn how scrum uses transparency, inspection, and adaptation to manage sprint work, plus how lean thinking identifies muda, mura, and muri to reduce waste, unevenness, and overburden.

Distinguish methodology from framework by contrasting rigid, documented processes like waterfall with flexible, principle-based guidelines; apply PMBoK rules and agile practices such as daily stand-ups and sprint planning.

Explore the scrum framework as an agile, iterative approach with product owner, development team, and scrum master, and learn sprint planning, daily scrums, reviews, and retrospectives.

Explore the scrum values of commitment, courage, focus, openness, and respect, and the pillars of transparency, inspection, and adaptation, to enable trust, collaboration, and a high-performing team.

Explore the Scrum framework’s rules, events, and artifacts, including Product Owner, Scrum Master, and Development Team roles, and how Sprint Planning and Daily Scrum enable transparency and value.

Explore the distinct responsibilities of developers, Scrum master, and product owner in a scrum team, including sprint activities, backlog prioritization, and delivering a potentially shippable increment.

Learn sprint fundamentals in scrum, a 1–4 week timebox where a cross-functional team delivers a potentially shippable product increment, guided by a sprint goal and cadence.

Refine the product backlog continuously by the product owner and development team, allocating at least 10% of the sprint to refinement for ready, prioritized items.

Understand the daily scrum, a 15-minute stand-up where the development team coordinates, reviews progress, and plans the day to achieve the sprint goal.

Learn how to run a sprint planning session by timeboxing, defining a sprint goal, selecting top backlog items, estimating capacity, and creating a sprint backlog to deliver a done increment.

Inspect the increment with stakeholders to gather feedback and validate it against the definition of done. Demonstrate the working features and refine the backlog through open discussion, collaboration, and transparency.

The sprint retrospective enables the scrum team to reflect on performance, identify improvements for people, processes, and tools, and create an action plan for the next sprint.

Explore how product backlog functions as the living, prioritized list of all features and changes, refined through backlog refinement and techniques like Moscow method, WSJF, and value versus complexity matrix.

Learn how sprint backlog, a subset of the product backlog, becomes a dynamic, task-level plan owned by the development team, aligned with the sprint goal and updated during the sprint.

Deliver a potentially shippable product increment each sprint by meeting the definition of done, enabling early stakeholder feedback and continuous value delivery in agile scrum.

Define the definition of done and acceptance criteria for each team, align with stakeholders, and manage technical debt to deliver a potentially realizable increment.

Define the definition of ready as an optional pre-sprint checklist ensuring user stories have clear acceptance criteria, identified dependencies, and adequate team capacity for sprint planning and execution.

Facilitate discussions between stakeholders with conflicting priorities to move forward together, balancing business value and technical sustainability through Scrum values, open communication, and shared understanding.

Master crafting user stories and acceptance criteria in agile development, using the three Cs and invest to deliver independent, negotiable, valuable, estimable, small, and testable backlog stories.

Explore estimation techniques like story points, planning poker, and relative sizing to predict sprint goals and de-risk scope, while collaborating to estimate, discuss requirements, and reach consensus.

Estimate the upcoming sprint capacity by analyzing velocity through story points or capacity in hours, accounting for holidays and ceremonies to set realistic sprint commitments and prioritize the sprint backlog.

Explore agile release planning and roadmap creation to deliver value through vision, roadmap, releases, sprints, and feedback loops, with six release types and practical planning considerations.

Learn to counter dominance in estimation with a silent simultaneous fix, anchoring, and structured meetings by prework, guardrails, and a shared information base.