Understand the scrum team as the product-focused unit of one scrum master, one product owner, and developers. Learn cross-functional collaboration, self-management limits, and Scrum's immutability toward the product goal.

The Scrum Master establishes Scrum by coaching the team and organization, enabling self-management and cross-functionality, removing impediments, and guiding value-driven, timeboxed events toward the definition of done.

Discover how the Scrum Master evolves from servant leader to true leader, proactively facilitates the team and the Product Owner, removes impediments, and coaches the organization for successful Scrum adoption.

Identify the eight misunderstood and eight preferred stances of a scrum master, including servant leader and facilitator, and learn to restrain from solving while promoting self-management and navigating conflicts.

Discover how the product owner maximizes value through backlog management, clear product goals, and marketplace knowledge, while guiding sizing and stakeholder collaboration for ROI.

The product goal anchors the product backlog and guides the scrum team toward a future state, with the product owner accountable for clear communication and backlog prioritization.

Developers in a scrum team create a usable increment each sprint, size PBIs, and plan the sprint backlog with the product owner toward the sprint goal.

The developers now shape the definition of done and plan how to convert product backlog items into increments, while the product owner prioritizes value and refinement.

Learn how to address missing skills in a scrum team by promoting collaboration and moving from i-shaped to t-shaped, pi-shaped, and comb-shaped capabilities, enabling self-organization and a done increment.

Review the Scrum roles: Scrum master, product owner, and developers, and how a cross-functional, self-managing team delivers a valuable increment each sprint through backlog management and a definition of done.

Identify the five official scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, all timeboxed to support transparency, inspection, and adaptation within the sprint.

Timeboxing assigns fixed maximum durations to scrum activities, boosting focus, urgency, and rapid inspection and adaptation across sprint planning, daily scrum, sprint review, and sprint retrospective.

The sprint timebox is Scrum's heartbeat, a container where Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective turn ideas into value toward the product goal within a one-month limit.

Explore sprint planning, where the whole scrum team defines the sprint goal, selects PBIs, and plans how to turn them into an increment that meets the definition of done.

Developers conduct the daily scrum for 15 minutes at the same time and place, inspect progress toward the sprint goal, and update the sprint backlog, with optional product owner attendance.

During the sprint review, the scrum team and stakeholders inspect the increment against the sprint and product goals, adapt the backlog, and plan next steps in a working session.

Inspect the sprint retrospective to boost team effectiveness by examining individuals, interactions, processes, tools, and the definition of done, focusing on context over content.

Clarifies scrum event durations and rules, explains how sprint length is chosen and kept consistent, and shows how inspection and adaptation occur at planning, daily scrum, review, and retrospective.

Master the scrum events and artifacts to deliver usable increments, mapping work to the product goal through sprint planning, daily scrums, reviews, and retrospectives.

Discover how Scrum artifacts and their commitments—product goal, sprint goal, and definition of done—enhance transparency and focus, guiding the product backlog, sprint backlog, and increment.

Discover how the product backlog, the single source of work, is ordered by value for delivery. Explore backlog refinement, sizing, and owner-developer collaboration to keep items ready.

Define the product goal as a future state in the backlog that guides incremental delivery toward a single, measurable objective, owned and communicated by the product owner.

Define the sprint backlog as the sprint goal, selected PBIs, and a plan for delivering the increment, updated during the sprint and kept highly visible.

An increment is a concrete stepping stone toward the product goal, additive and usable. The whole Scrum Team decides when to release increments that meet the definition of done.

The definition of done is a formal description and commitment for an increment that meets product quality measures and ensures the increment is usable by end users.

Review the three Scrum artifacts—Product Backlog, Sprint Backlog, and Increment—and their commitments, including the Product Goal, Sprint Goal, and Definition of Done, to drive transparency and value.

Explore story points as a relative unit of effort for estimating product backlog items, including design, coding, testing, and definition of done considerations, and learn how velocity guides sprint planning.

Planning poker to assign story points to PBIs, using face-down votes to prevent anchoring bias, compare high and low estimates, discuss, and derive a consensus.

Track sprint and project progress with a burndown chart that compares planned progress (gray line) to actual progress (blue line), revealing behind-schedule or ahead-of-schedule status, often automated in Jira.

Compare Burnup and Burndown charts to track progress, highlighting how Burnup shows complete and total work and scope changes, while the living product backlog evolves.

Explore the cone of uncertainty, showing high initial project uncertainty that decreases as we gain knowledge through iterations. Learn how evolving knowledge improves estimations and confidence over time.

Learn how technical debt accrues when teams trade quality for speed, explore refactoring as a debt repayment strategy, and discuss planning, architecture, and scalability considerations.

Master agile concepts by reviewing story points and planning poker, and track progress with burndown and burnup charts while understanding the cone of uncertainty and technical debt.

Explore a scrum example to apply the Scrum theory in practice, covering project initiation, product backlog creation and items, tools to manage tasks, and starting and completing sprints with length.

IWS teams up with John to build a conversion-focused website, enabling long-term brand growth as they shift from newspaper ads to Facebook marketing through an agile scrum approach.

Explore how a product owner and team write user stories using a simple template, build a living backlog, and plan features like scheduling, marketing funnels, and secure payments.

Create a Jira project with a Scrum template, build a product backlog of user stories and tasks, start a sprint, assign work, and track progress with burndown and burnup reports.

Master sprint planning for a two-week sprint, addressing the why, what, and how, setting the sprint goal and backlog while planning design, hosting, and payment integration.

Discover how daily scrums keep the team aligned with the sprint goal using the three questions, and how the definition of done differs from acceptance criteria.

During the sprint review, the team demos 100% done items while the product owner gathers feedback from John to prioritize next sprint tasks, including Facebook pixel integration and going live.

The Scrum Master guides the team to identify high-priority improvements and test a new practice: developers test before passing bugs to QA to reduce back-and-forth.

Plan the second sprint by prioritizing the backlog to build a lead-generation page that collects user details. Design a MySQL database with CRUD operations and integrate MailChimp and Facebook pixel.

Follow a multi-sprint journey from testing adjustment landing page and Facebook pixel to deploying a lead-generation page with Google Analytics and a payment sandbox, while refining the definition of done.

Read questions carefully to avoid traps and wording changes, such as participate versus attend or can versus should versus must; stay focused and do not panic.

Master the immutable rules of scrum, including a 15-minute daily scrum, sprint timeboxes, five events, and three roles guiding multiple teams toward a product backlog, product goal, and integrated increment.

Scale Scrum by focusing on a single product backlog, shared definition of done, and delegated product owner duties; manage dependencies and context-switching across multiple teams for alignment.

Explore how product owners turn ideas into backlog items, the role of refinement, and why the definition of ready is not part of Scrum, yet readiness guides sprint work.

Follow a structured exam prep using the strong guide, open assessments from chrome dot org, the Nexus guide, and optional Jeff Sutherland videos to achieve 98–100% on practice tests.

Focuses on harder, scenario-based questions with detailed explanations and the thought process behind answers, grounded in the Scrum Guide and evidence based management, to help you excel on the exam.

Navigate a behind-schedule scenario as a scrum master, guiding collaboration between the portfolio manager and product owner to refine the backlog and agree on a future delivery date.

As the scrum master, coach the team on the daily scrum purpose and encourage self-correction to keep daily scrums as developer synchronization, not status updates.

Remind all developers of the daily scrum's purpose. Discuss the consequences of non-participation to address the situation.

A Scrum team addresses slow website performance by advising the product owner to raise the concern with the whole team for collaborative, transparent decision-making.

Apply facilitation and coaching to de-escalate conflicts, using the five levels of conflict, facilitating open discussions in sprint retrospectives to uncover root causes and improve team dynamics.

Learn how a Scrum Master guides a product owner to focus on the sprint goal rather than the initial forecast, and adjust the sprint backlog to achieve that goal.

Explore integrating scalability and other nonfunctional requirements into the product backlog and definition of done, while ensuring each sprint delivers some business facing functionality.

Learn to transition from waterfall to adaptive agile by adopting feature teams and understanding that new scrum teams progress through forming, storming, norming, performing, with initial productivity often low.

Explore how to allocate product owners across multiple products, from one per product to a chief owner, with delegation, backlog management, PBIs, and context-switching considerations.

Explain the definition of done, how PBIs become releasable increments, and why acceptance criteria differ from the definition of done, with examples from sprint reviews.

Daily scrum lasts up to 15 minutes, held at the same time and place to reduce complexity; developers participate, product owners may attend without interrupting, focusing on sprint goal progress.

Balance stakeholder opinions as a product owner by running experiments to validate feature value, prioritizing the backlog with minimum viable products, and seeking end-user feedback.

Coach the inexperienced product owner to align with the sprint goal as your Scrum Master, avoid changing the sprint backlog for feedback, and facilitate internal resolution to protect value delivery.

Stakeholders stay upset because lacking transparency and missing feedback during sprint reviews lead to assumptions about features, while the product owner fails to seek stakeholder input.

Learn how the definition of done creates a releasable, transparent increment with testing included, involves the whole Scrum team, guides sprint planning, and informs the product owner of sprint progress.

Develop practical scrum master skills for daily work through servant leadership, empowerment, humility, empathy, foresight, and stewardship, with role play, actionable tips, and active listening practice.

Explore the principles of servant leadership for the Scrum master, and learn empowerment, humility, empathy, foresight, stewardship, and commitment to growth through practical examples and role-play.

Empower your team through servant leadership, fostering confidence, ownership, and decision-making in sprint planning, while guiding with open questions and collaborative research on payment gateway security.

Lead with servant leadership and humility as a scrum master. Acknowledge you don’t have all the answers, learn with the team, and address the learning curve, roadblocks, and communication.

Practice empathy in action to strengthen servant leadership as a scrum master, connecting with team members' emotions, acknowledging stress, and offering flexible support to build trust.

Master foresight as a servant leader by anticipating obstacles, managing dependencies, and transparently coordinating with stakeholders to keep sprints on track and deliver value.

Embrace stewardship in action by advocating for your team's growth, removing obstacles, and exploring rewards like training or leadership roles when budgets limit promotions, aligning with scrum's team-focused review.

Foster continuous improvement within the scrum team by leveraging sprint retrospectives and team-based learning. Balance learning with sprint commitments while expanding cloud technology skills to deliver greater value.

Master active listening to strengthen scrum team communication, empathy, and trust through being fully present, maintaining appropriate eye contact, avoiding judgment, and guiding through servant leadership.

Master active listening by not interrupting, paraphrasing key statements, summarizing insights, and asking open-ended questions to encourage participation and ensure clear, respectful communication.