The Ultimate Advanced Training For Agile Scrum Masters

Refresh your agile knowledge and prepare for the advanced section by exploring the Scrum framework, its accountabilities, events, artifacts, and commitments, plus agile vs waterfall and product vs project management.

Explore the Agile Manifesto and its four core values: individuals and interactions, working software, customer collaboration, and responding to change, along with the 12 principles guiding flexible software development.

Compare waterfall's plan-driven, sequential phases with agile's adaptive, incremental, and iterative approach, emphasizing sprints, product backlog, continuous delivery, and customer feedback in scrum contexts.

Discover how agile planning avoids detailed upfront plans, using a transparent product backlog and sprint backlog to guide incremental development, with adaptation from feedback to reduce waste.

Shift from project to product management in agile Scrum, delivering value through user adoption, retention, and ROI, guided by customer feedback and a self-organizing backlog.

Explore Scrum as a lightweight framework grounded in empiricism and lean thinking, reveal its pillars of transparency, inspection, and adaptation, and outline roles, artifacts, and timeboxed events.

Learn how sprint planning defines the sprint goal and selects PBIs for the sprint backlog, while daily scrum, sprint review, and retrospective enable inspection, feedback, and adaptation toward product goal.

Explore how a cross-functional, self-managing scrum team delivers usable increments each sprint, defines the definition of done, and uses feature or component teams to achieve the product goal.

The ultimate advanced training for agile scrum masters shows how the product owner maximizes value, manages the backlog, communicates the product goal, and coordinates with stakeholders for transparent increments.

The product owner creates and communicates the product goal to guide the backlog and sprint planning, maintains a single goal, and leads sprint reviews.

The scrum master is accountable for scrum effectiveness, coaches the team in self-management, removes impediments, and ensures time-boxed events enable high value increments.

The Scrum Master part 2 clarifies the servant leader role, positions the Master as facilitator of stakeholder collaboration, and coaches the organization to remove impediments and enact Scrum.

Learn how developers collaborate with the product owner to select sprint backlog items, commit to the sprint goal, size work with story points, and adapt to deliver a usable increment.

The developers define the definition of done, refine backlog items into increments, and plan work to maximize value with a single product backlog.

Explore the scrum master, product owner, and developers as a cross-functional, self-managing team delivering a valuable increment each sprint through backlog management, definition of done, and stakeholder collaboration.

Master five official scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, using time boxing within the sprint container to enforce transparency, inspection, and adaptation as mandatory.

Discover how the sprint serves as the heartbeat of scrum, a time-boxed container for sprint planning, daily scrums, sprint previews, and work that moves toward the product goal.

Learn how sprint planning aligns the team with the product goal by answering why, what, and how, and by creating the sprint backlog.

Inspect progress toward the sprint goal through the daily scrum, adapt the sprint backlog, and have developers plan the next day in a time-boxed 15-minute, same time and place meeting.

Present the sprint increment to the scrum team and key stakeholders, gather feedback, and adjust the product backlog to align with the sprint goal and product goal.

The sprint retrospective lets the scrum team inspect the last sprint, focusing on interactions, processes, tools, and the definition of done to identify improvements for quality and effectiveness.

Set sprint length within one month, balancing rules and practical needs, avoid mid-sprint changes, and keep events time-boxed and consistent for inspection and adaptation.

Learn how sprints drive value in scrum through planning, daily coordination, reviews, and retrospectives, with focus on the backlog, product goal, increment, and definition of done.

Explore Scrum artifacts, including the product backlog, sprint backlog, and increment, and their commitments—product goal, sprint goal, and definition of done—emphasizing accountability and transparency.

The product backlog is the single source of work, an ordered list maximizing value, with the product owner prioritizing items for developers to pull into sprints and backlog refinement.

Define the product goal and align the backlog to move toward it, ensuring a single Scrum protocol at a time with measurable progress and product owner accountability.

The sprint backlog, created in sprint planning, lists the sprint goal, the PBIs selected, and an actionable plan, remaining flexible as incomplete items move back to the product backlog.

Explore how increments in scrum build toward the product goal, with each increment additive, verified, and usable, presented in the sprint review and released at the whole scrum team's discretion.

The definition of done is a formal description and commitment that an increment meets quality measures, serving as a usable, transparent checklist for all teams on the same product.

Explore the three Scrum artifacts—the product backlog, sprint backlog, and increment—and their mandatory commitments: product goal, sprint goal, and definition of done, all designed to enhance transparency and focus.

Advance your agile scrum mastery by delving deeper into scrum concepts, with actionable items and curated readings (blog posts, white papers, articles) to prepare for the Pkm2 exam.

Embrace empiricism as the foundation of scrum, using transparency, inspection, and adaptation to drive sprint and product goals, guided by Kaizen and data-driven decision making.

Explore Scrum values—commitment, courage, focus, openness, and respect—and how these values drive behavior, build trust, and emphasize commitment to the sprint goal over the sprint backlog.

Spot common Scrum Master misunderstandings, such as acting as a schoolmaster, secretary, boss, or superhero, and learn to align with self-management and transparent artifacts rather than reports.

Explore the eight stances of the Scrum master and how servant leadership evolves into true leadership that serves, enabling self-management and value delivery.

Remove impediments and waste as a servant leader; the scrum master enables self-management and guides organizational change to support product owner and developers.

Review empiricism through transparency, inspection, and adaptation to guide sprint goals and decisions. Emphasize servant leadership, proactive impediment removal, and values-driven teamwork to empower high-performing scrum teams.

Learn how the Scrum Master serves the organization by fostering environments where Scrum teams thrive, collaborating with stakeholders, removing impediments, and guiding value-driven, empiricism-aligned, self-managed agile practice.

guide the product owner to refine the backlog, clarify the product vision, and foster stakeholder collaboration and empiricism to maximize value through releases.

Coach the Scrum team toward self-management and cross functionality, enable done increments each sprint, and guide clear sprint and product goals through productive events to reinforce empiricism.

Great scrum masters create environments where scrum teams can thrive by coaching organizations, promoting transparency, and embracing empiricism, while supporting the product owner and removing impediments to value delivery.

Ensure a releasable, done increment every sprint by including testing, with no pending work. Let the team decide releases, with the definition of done guiding transparency and valuable increments.

Set clear sprint and product goals in business language, with the product owner guiding objectives and the Scrum team committing to the sprint backlog as scope evolves.

Compare feature teams and component teams, showing how feature teams deliver value with cross-functional skills and fewer handoffs. Review forming, knowledge transfer, and self-management concepts for Scrum masters.

Recap #3 highlights delivering a releasable increment each sprint by upholding the definition of done, ensuring transparency, and aligning sprint goals with stakeholders.

Apply the five levels of conflict model by Lisa Atkins to keep scrum team disputes constructive at level one through facilitation, coaching, and self-management.

Learn emergent architecture in Scrum by balancing functional and nonfunctional requirements, delivering business facing functionality each sprint with just enough architecture guided by empiricism.

Velocity measures how much work a scrum team completes in a sprint and is unique to each team, not a direct measure of value.

Facilitate open discussions to de-escalate conflicts and protect team health, without HR or managers deciding removals; embrace emergent architecture and value-driven metrics over velocity.

Learn that scrum is a framework; teams can use tools, practices, charts to support collaboration. Prioritize individuals and interactions over processes and tools; let distributed teams choose communication tools.

Scaling scrum manages cross-team dependencies without changing the core design, using one product backlog, one product owner, one product goal, and a shared definition of done; accountability is delegated.

Timebox each Scrum activity with a fixed maximum time to limit work in progress and keep events focused. Support velocity planning and inform sprint length with consistent time boxes.

Explore the concept of T-shaped versus eye-shaped skills within the Scrum team, and learn how cross-functional collaboration and self-organization overcome scarce skills to deliver an integrated increment.

Learn how burn down and burn up charts function as information radiators to track sprint progress, reveal scope changes, and ensure value delivery in agile scrum.

emphasize that individuals and interactions trump processes and tools, and scaling scrum relies on collaboration, self-organization, and shared definitions to manage dependencies and prevent context switching.

Review the exam roadmap and resources, including practice questions, and learn what to do and what not to do during the Agile Scrum Master exam, plus top eight tips.

Eight tips to excel on the scrum master exam: eliminate absurd answers, read questions carefully, avoid distractions, manage 90 minutes, and rely on rules from the Scrum Guide.