Scrum Master Bootcamp: Basics to Advanced Agile Leadership

Understand how scrum, as a popular agile framework, drives customer value through frequent deliveries and feedback, with clear roles (scrum master, product owner, development team) and a structured lifecycle.

Explore the origins of the Agile manifesto, from the late 1990s to its 2001 release, and its four values: individuals and interactions, working software, customer collaboration, and responding to change.

Explore how the PMBOK guides project management across initiation, planning, execution, monitoring and control, and closing, and compare predictive, iterative, incremental, and adaptive lifecycles in agile contexts.

Highlight the first five Agile Manifesto principles: satisfy customers through early, continuous delivery; welcome late changes; deliver frequently; and promote daily collaboration of business and developers with motivated, trusted teams.

Discover how face-to-face communication and co-located teams accelerate agile delivery, emphasize working software, sustainable development, technical excellence, simplicity, self-organizing teams, and continuous improvement.

Explore the six scrum principles: empirical process control, transparency, inspection, adaptation, self-organization, and collaboration, and how time boxing, value-based prioritization, co-location, and iterative development guide sprint planning and risk management.

Discover empirical process control in Scrum through transparency, inspection, and adaptation, guided by roles, meetings, artifacts, and information radiators that enable continuous improvement.

Self-organization in scrum relies on servant leadership and decentralized authority among product owner, Scrum Master, team. The Scrum Master coaches, removes impediments, and drives improvement through sprints and daily meetings.

Unite the product owner, Scrum Master, and development team to deliver value through collaborative Scrum practices. Prioritize co-location, build trust, and adapt tools to support distributed teams and stakeholder communication.

Prioritize value-based backlog and user stories in Scrum to drive business value, guided by the product owner and team through sprints and risk-aware planning.

Understand timeboxing in Scrum: sprints are time-boxed iterations of 1–6 weeks, with sprint planning, daily standard meetings, sprint reviews, and retrospectives guided by Scrum Master and Product Owner prioritizing backlog.

Embrace iterative development within scrum to handle changing requirements via epics and user stories, prioritized by business value and ROI, with the product owner guiding backlog for time-boxed sprints.

Scrum focuses on people and change, unlike project management’s process-driven, plan-detailed approach, highlighting sprint-based iteration, minimal documentation, and embracing change to maximize business value.

Explore Scrum versus project management with a focus on customer involvement, sprint planning, user stories, and decentralized roles to drive final outcomes and customer satisfaction.

Scrum delivers adaptability, transparency, and continuous feedback through information radiators like boards and burn-down charts, aligning the team with the project vision and delivering value.

Explore how time boxing and daily standups improve efficiency and motivation in scrum. Leverage sprint reviews, collaboration, and transparency to accelerate problem resolution and deliver customer-centered value.

Explore the five Scrum phases: initiation, plan and estimate, implement, review and retrospect, and release, and how they drive vision, backlog, sprint planning, and validated deliverables.

Initiate phase kicks off the scrum process by creating the product vision, identifying the Scrum Master and stakeholders, forming the Scrum Team, and prioritizing epics and backlog for release planning.

Create and refine user stories with acceptance criteria for the prioritized product backlog, then identify and estimate tasks, commit stories, and build the sprint backlog to achieve the sprint vision.

Implement phase emphasizes creating deliverables from the sprint backlog, using information radiators like the scrum board, maintaining an impediment log, and daily standups to groom and prioritize the product backlog.

Demonstrate and validate sprint deliverables to the product owner and stakeholders in the sprint review, then the scrum master and team retrospect for lessons learned and actionable improvements.

Release phase finalizes the sprint by shipping deliverables, securing acceptance from the product owner and stakeholders, and conducting a retrospective to capture lessons for future projects.

Explore agile methods from the manifesto to practical frameworks such as Scrum, XP, lean, Crystal, SDM, FDD, and Kanban, and compare iteration-based and flow-based approaches.

Trace scrum’s history from the 1980s rugby-inspired teamwork by Takeuchi and Tanaka to 1995 expansion by Tauber and Sutherland, leading to its status as a premier software development approach.

Explore how Scrum rules, roles, and business justification shape the project lifecycle. Drive value-based delivery with quality, definition of done, change response, risk management, and Moscou prioritization.

Explore the three core Scrum roles—product owner, Scrum master, and Scrum team—and how non-core roles like stakeholders, vendor, and Scrum guidance body shape agile project practices.

Identify the scrum master as a servant leader who facilitates, motivates, and coaches the team, bridging the product owner and team while removing impediments and avoiding traditional project-manager authority.

empower the Scrum Master to act as facilitator in a decentralized system, guiding Scrum practices, coordinating with the product owner and stakeholders, and removing impediments to sprint success.

Coordinate with the product owner to prioritize the backlog, develop epics and user stories, define done criteria, and explain Scrum to stakeholders for effective sprint planning and continuous delivery.

The Scrum Master wields indirect authority as a facilitator, motivator, and coach, advocates for stakeholders, and ensures Scrum practices are followed with pre-implementation analysis to drive project success.

Identify the product owner who defines responsibilities, creates and prioritizes the product backlog with epics and user stories, and translates stakeholders' needs into business value through sprint planning.

Translate customer needs into epics and simple user stories with acceptance criteria, collaborate with the Scrum Master, establish a project vision, maintain a prioritized backlog guiding sprint planning and review.

Learn how the product owner drives the product backlog with business-focused user stories and epics, communicates with stakeholders, prioritizes by ROI, and has final decision authority.

The development team owns backlog items, self-manages their work, and delivers product backlog items in a cross-functional, full-time sprint, aligned with sprint goals for incremental delivery.

Enhance scrum quality by aligning with business value through measurable acceptance criteria. Define done and apply plan, do, check, and retrospective cycles with continuous testing.

Embrace change as a core agile principle, allowing the product backlog to evolve through the product owner's prioritization, while maintaining sprint stability and team focus.

Understand how risk drives the Scrum process, from identification and analysis to planning, attitude, appetite, and tolerance, converting threats into opportunities with the team.

Identify and manage risk in Scrum through a risk breakdown structure, assess probability and impact, prioritize risks in the backlog, and implement mitigation with the product owner and Scrum Master.

Understand how sprints drive the scrum process by iterating through planning, daily scrum, review, and retrospective, delivering increments that may be released and refined via the product backlog.

Define a fixed, time-boxed sprint; keep the sprint backlog and sprint goal unchanged; use a clear definition of done and acceptance criteria to deliver increments.

Explore sprint time boxes in agile scrum, typically 2–4 weeks, balancing focus and risk, and learn how the product owner can cancel a sprint when backlog changes render it obsolete.

Kick off sprint planning within a fixed eight-hour window with product owner, scrum master, and development team to align a not 100 percent complete backlog with value-ranked stories and estimates.

Master sprint planning as the Scrum team selects top user stories from the product backlog, estimates work against capacity, and creates a sprint backlog guided by the sprint goal.

Learn how the sprint backlog translates selected product backlog items into a sprint plan with a defined goal, tasks, and status on a board to simplify Scrum.

Master scrum artifacts and their role in transparency, including the product backlog, sprint backlog, and increment. Learn to monitor progress, define done, and use information radiators for inspection and adaptation.

Discover how the product backlog, owned by the product owner, guides sprint planning, prioritizes user stories by business value and ROI, and remains dynamic for delivery.

Facilitate grooming and maintenance of the product backlog with the product owner, prioritize user stories, and translate requirements into epics and tasks for the Scrum team.

Create and manage a product backlog with ordered backlog items for user stories, including story name, description, estimates, due dates, complexity, categories, assignments, tracking, and collaboration to guide sprint planning.

Attend the daily scrum, a 15-minute time-boxed ritual that enables the Scrum team to plan the next 24 hours, inspect progress toward the sprint goal, and surface impediments.

The daily scrum, time-boxed to 15 minutes, answers what has been accomplished, what will be done, and what obstacles remain to drive sprint progress.

Facilitate a 15-minute internal daily scrum that aligns the development team, product owner, and stakeholders, surfaces impediments, and enables quick decisions to keep sprint goals on track.

Review the sprint increment with the Scrum team and stakeholders to inspect progress, foster collaboration, and adapt the product backlog for maximum value in the next sprint.

The scrum master ensures a time-boxed sprint review, aligns stakeholders with the sprint goal, reviews completed user stories, and guides the team to improve in the next sprint.

Explain the sprint review, its attendees, and the definition of done for backlog items and increments. Demonstrate how feedback, impediments, and marketplace conditions guide future sprint planning and delivery dates.

The sprint retrospective invites the Scrum team to inspect the completed sprint, discuss what went right, and create an improvement plan to be enacted in the next sprint.

Drive continuous improvement by inspecting the last sprint's people, processes, and tools. Plan for better sprint execution, planning, and daily stand-ups, and identify improvements and impediments.

Explains how sprint retrospectives drive inspection and adaptation by analyzing what went right or wrong, planning improvements for the next sprint, and aligning stakeholders and team with the project vision.

Monitor progress toward the product backlog goals using burn down charts, sprint reviews, and empirical practices led by the product owner and Scrum Master.

During sprint planning, collaborate to create and freeze the sprint backlog by selecting top product backlog items based on estimates and team capacity, guided by the sprint goal.

Monitor sprint progress by tracking the sprint backlog, daily scrums, and burn down charts to assess goal achievement, adjust plans, and ensure transparency across the Scrum team.

Discover how an increment is the usable output of a sprint, shaped by the product backlog, definition of done, and collaboration among the product owner, Scrum team, and stakeholders.

Define the definition of done as a shared standard for completed work, aligning the product owner, Scrum team, and stakeholders with acceptance criteria and a potentially releasable increment.

Learn how scrum values guide agile teams—commitment, courage, focus, openness, and respect—through product owner, scrum master, and development team collaboration, planning, and decision making.

Emphasizes commitment as the foundation of Scrum, aligning transparency, inspection, and adaptation to drive collaboration, deliver value from the product backlog, and achieve sprint goals through a quality increment.

Emphasize courage to support transparency, accountability, and collaboration in the scrum process. Teams tackle complex adaptive problems through empirical principles, inspecting progress, adapting plans, and embracing change to deliver value.

Deliver increments by incorporating customer feedback, refining the backlog, and running sprints with high-priority user stories, while the Scrum team stays transparent, adapts through sprint reviews, and continually improves.

Focus drives the Scrum team to deliver a high quality product by aligning with the project vision, prioritizing backlog items, and managing change through time-boxed sprints and clear goals.

Explore openness as a core scrum value that promotes transparency, honest information sharing, and ongoing inspection and adaptation of how the team, product backlog, and stakeholders work.

Respect enables transparency, self-organization, and collaboration in a Scrum team, empowering individuals with autonomy and shared responsibility to achieve the project vision through open, diverse, change-driven teamwork.

Explore the overall scrum process, initiating with the project vision statement and product roadmap, then plan sprints and manage the backlog of user stories under the product owner's guidance.

Master the daily scrum, sprint planning, and sprint review to deliver iteratively with a product owner guiding the roadmap, while tracking progress with burn-down charts and information radiators.

Act as a servant leader, the Scrum master guides the team and product owner to clarify goals and backlog, promoting agile events and empirical planning to maximize value.

Remove impediments for the scrum team, facilitate sprint events, and coach the organization through scrum adoption and empirical product development to boost productivity and align with goals.