Scrum Master

Prepare for a scrum master certification by covering core scrum concepts and essential strategies for success, even if you have limited prior exposure.

Join a global mentoring community for scrum and agile practitioners to learn capabilities, share best practices, and prepare for scrum and agile certifications.

Identify why learning scrum skills matters for your team and how your learning style shapes understanding of the techniques. Plan how you will apply course insights to improve organizational performance.

Explore Bloom's Taxonomy and its six levels, from knowledge to synthesis and evaluation, and apply basic knowledge and comprehension to improve scrum performance through targeted exercises.

Clarify how to use course and third-party materials, and engage with the mentoring community. Set personal expectations to own your skills and boost your Scrum team's productivity and outcomes.

Create a formal study schedule and dedicate distraction-free time to focus on the material, revisiting sections as needed, and establish milestones to review and revise understanding as you gain skills.

Print a copy of the courseware to follow along, using consistent conventions like chapter learning objectives, key terms, concepts to know, and iconography.

Use examples and quizzes to confirm learning objectives, reinforce key knowledge and skills, and build through each section to gauge readiness for the certification exam by answering practice questions.

Explore scrum certification exams as objective tests. Each exam has 75 to 140 questions, worth one point each, with no guessing penalty and online proctoring, lasting 90 to 180 minutes.

Create a study plan, master core concepts, objectives, and terms; apply insights to sprint reviews and retrospectives, and use quizzes and practice exams aligned with the Scrum body of knowledge.

Explore why agile development beats traditional project management, and learn six core scrum principles and how scrum leverages five key project aspects to improve outcomes.

Identify essential terms for scrum mastery, including adaptation, the Agile Manifesto, information radiators, time boxing, transparency, waterfall, and roles like programs and projects. Understand how scrum guidance shapes practice.

Explore the origins, benefits, and enterprise-scale applications of Scrum, and learn the key aspects and processes that ensure Scrum works.

Project management functions as a framework to organize time, money, and people across temporary teams, coordinating stakeholders to deliver valuable products, services, artifacts, and deliverables for customers.

Explore how project management as a discipline plans, organizes, motivates, and controls resources to reach goals, using initiation, planning, execution, monitoring, and closing across PMI, Prince2, and Scrum.

Explore software development lifecycle methodologies and management tools to initiate, plan, execute, control, deploy, and deliver projects while accommodating changing requirements through agile practices.

Explore the traditional waterfall method, which seeks structure by locking down requirements and design before moving forward, and why rapid changes in six-month projects challenge its effectiveness.

Explore the shift from traditional waterfall to agile, highlighted by the 2001 Agile Manifesto, prioritizing individuals, collaboration, working software, and responding to change to deliver business value over heavy documentation.

Focus on customer-centered value and viewing change as a competitive advantage. Deliver working software frequently through Scrum by enabling motivated teams and aligning business and development to create high-value solutions.

Foster face-to-face conversations and a cross-functional, self-organizing team to deliver working software aligned with customer value. Emphasize sustainable work, technical excellence, and refactoring to adapt to change and reduce waste.

Explore agile methodologies, including lean, extreme programming, crystal, feature driven development, test driven development, adaptive software development, agile unified process, and domain driven design, and see how scrum borrows techniques.

Trace the history of Scrum from the 1980s, where baton passes gave way to a rugby-style, team-based collaboration, evolving into a lightweight, self-organizing, empiricism-informed framework in 1995.

Explore scrum benefits that empower self-organizing teams to adapt to changing requirements with transparent delivery for customers and stakeholders, plus continuous feedback and focus on working software.

Scale scrum by coordinating multiple teams through a scrum of scrums, keeping teams at five to ten members. Establish a scrum guidance body to share lessons and improve velocity.

Explore the core concepts and principles of Scrum, and examine how these aspects support project management. Learn about the processes in the Scrum lifecycle to effectively deliver solutions for customers.

Embrace empirical process control through tangible results. Foster self-organization with no project manager and prioritize the product backlog by highest customer value in timeboxed two-to-four week iterations.

Apply empirical process control by embracing transparency, inspection, and adaptation in scrum projects. Use information radiators and stakeholder feedback to evolve solutions as customer needs change.

Foster self-organization and ownership in scrum teams by removing roadblocks and servant leadership. Empower team through scrum master and product owner to improve buy in, morale, and space for innovation.

Create collaborative environments with visibility into who has what and how work partitions are managed. Reuse technologies to support needs, and co-locate teams when possible to deliver better customer solutions.

In Scrum, the team maintains and continually refines a prioritized product backlog to adapt to changing customer needs, risks, and business value, always delivering the highest value features first.

Time-box scrum activities to boost efficiency and deliver more value, using a 15-minute daily standup and tightly scheduled sprint planning, reviews, and retrospectives to focus development and reduce overhead.

Apply iterative development by breaking work into rounds and sprints, adapt to changing requirements, re-prioritize efforts, and continuously manage risks to deliver maximum customer value quickly.

Learn how scrum organizes around three core roles: product owner, scrum master, and scrum team, and focuses on delivering high-value solutions aligned with customer vision while managing change and risks.

Explore the core scrum processes, 18 in total, organized into five large groups: initiation, planning and estimation, implementation, review, in retrospect and release.

Explore the five phases of a scrum project, from initiation and planning to estimation, implementation, sprint reviews and retrospectives, and finally releasing solutions to production.

Initiate the project by defining the vision, identifying stakeholders and the scrum master, forming the team with personas, creating a prioritized product backlog and release plans to deliver value early.

Plan and estimate effort through user story workshops, write concise stories, and commit to prioritized sprint goals by approving estimates. Map tasks and create backlogs for delivery.

Implement sprint deliverables based on user stories and run standups to keep the team informed. Groom the backlog to reflect change requests, new risks, and shifting priorities in upcoming sprints.

Coordinate with scrum of scrums to align teams. Conduct sprint reviews with the product owner to confirm completed user stories and gain buy-in; facilitate retrospectives to improve the next sprint.

Coordinate and plan a release to ship sprint outputs into production and align with organizational release and deployment planning; retrospect the project to capture lessons for the Scrum guidance body.

Explore the core concepts of scrum, including its purpose, benefits, and scaling approaches. Identify the key principles and the 18 processes that shape its framework.

Explore how scrum and agile methods address overemphasis on documentation and contracts. Empower teams to self-organize, collaborate, adapt to change, and deliver working software through empirical process control.

Test your understanding of agile practices and scrum with a focused quiz that challenges you to apply core concepts learned in chapter 02.

Explore scrum roles, including product owner, scrum master, and team, connecting business cases to vision and backlog with definition of done, acceptance criteria, risk identification, assessment, mitigation, and change management.

Master the core scrum vocabulary by exploring terms like business case, epic, backlog, sprint length, minimum marketable features, prioritized product backlog, user story, and product owner roles.

Explore the core roles within Scrum, how Scrum organizes itself, and how to establish responsibilities and authorities for each Scrum role.

Identify the scrum master as a servant leader who works for the team, facilitates meetings and collaboration, coaches and removes roadblocks to deliver customer-valued solutions.

As a scrum master, teach and coach scrum practices—time boxing, self-organization, and collaboration—reminding the team of their purpose, enabling improvement, removing impediments, protecting sprints, and delivering customer value.

The scrum master guides through indirect authority, advocating for the team and facilitating optimal performance by applying scrum principles, while fostering self-organization and accountability without decision-making power.

Identify the product owner, who ensures business value and serves as the voice of the customer. The scrum master supports by facilitating requirements sessions and prioritization to organize the backlog.

Product owner ensures the solution aligns with business goals by maintaining visibility into customer needs and markets, and collaborates with stakeholders on backlog grooming and sprint reviews.

Take full ownership of the product backlog and prioritization to drive value, deliver early ROI, and guide release timing while protecting sprint scope with a single accountable product owner.

Form a cross-functional scrum team with the right skills to deliver whole working solutions, test, integrate, and document customer user stories, through collaboration, accountability, and value delivery.

Scrum team delivers project deliverables to support user stories, tracks progress with a sprint burndown chart, and participates in planning, sprint review, daily stand-up, and retrospective meetings.

The scrum team self-organizes to deliver user stories and outcomes, defining who does what, planning tasks, estimating effort, and collaborating to deliver whole customer solutions.

Facilitate stakeholder communications across customers, users, sponsors, vendors, and governance bodies through sprint reviews, product updates, and retrospectives, while establishing a tailored communication plan for lifecycle needs.

Explore fundamental differences between scrum and traditional project management, including no project manager and cross-functional teams owning deliverables. A business analyst broadens to prototypes, testing, documentation, and sprint reviews.

Explore business justification within scrum, emphasizing value driven delivery, delivering benefits and services to customers, and the roles that maintain justification, track benefits, and confirm realized value.

Scrum prioritizes high-value capabilities and delivers early, incremental value by releasing services into production quickly. It reduces risk by embracing changes, re-prioritizing requirements sprint by sprint to maximize business value.

Justify business value and help product owner maintain prioritized backlog with stakeholders, review sprint deliverables with customers, while scrum master facilitates, mitigates risks, and guides turning requirements into user stories.

Assess the business justification by analyzing the project reason, internal strengths and weaknesses, external opportunities and threats, and the resulting business need, benefits, costs, and risks to set timescales.

Explain how to maintain a justified business case throughout the project lifecycle by linking deliverables to ongoing value and customer benefits realization after each release.

Apply traditional financial metrics, value stream mapping, and Moskow analyses for prioritization to justify the business value. The product owner prioritizes the backlog to identify minimum marketable features for release.

Prioritize with MoSCoW analysis to classify must have, should have, could have, and won’t have items, balancing level of effort with business value to deliver minimal marketable features.

Use the 100 point method to prioritize user stories by letting users and customers allocate up to 100 points across stories. Aggregate the votes to drive the prioritized product backlog.

Use the Kano model for strategic planning to classify features by customer expectations into excitement, performance, basic needs, and indifferent features, guiding prioritization.

Scrum masters replace traditional tools with value analysis and cumulative flow diagrams to track delivered features and evolving requirements, ensuring solutions reflect changing goals and real progress.

Emphasize empiricism and demonstration of value through sprint reviews, using prototypes to explore requirements, focusing on deliverable services over tasks, deploying minimum marketable features early, and aligning with release plans.

Explore how the scrum master facilitates quality in customer solutions, defines quality within scrum, and uses definition of done and acceptance criteria as metrics to meet customer expectations.

Coordinate stakeholders and acceptance criteria to deliver business value while meeting the product owner's definition of done, and continually test and improve quality through refactoring and change.

Create and manage user stories in a product backlog, and set minimum acceptance criteria that meet both the broad definition of done and story-specific criteria, authored by the product owner.

Define the definition of done as consistent criteria for every user story; align metrics and acceptance criteria to ensure quality, including reviews, testing, documentation, fixes, and demonstrated to stakeholders.

Embrace scrum practices that build quality into every solution through refactoring, continuous integration, automated testing, and sprint-driven continuous improvement amid changing requirements.

Master the agile mindset by embracing change, balancing flexibility and stability, and safeguarding each sprint as a Scrum Master while aligning change requests with the product backlog.

This lecture contrasts waterfall's resistance to change with agile responsiveness, inviting changes to improve quality and outcomes by continually grooming and prioritizing the product backlog based on value.

Establish a change management process and change authority; unapproved requests await approval, with small changes approved by the product owner for backlog, while larger changes involve sponsors or program management.

Balance stability and flexibility by protecting the sprint backlog while iteratively delivering high-value user stories through value-based prioritization, grooming, cross-functional teams, time-boxed meetings, and continuous integration.

Protect the sprint backlog from significant changes, reflect them in the prioritized product backlog, and restart the sprint if results are worthless.

Explore risk management in scrum, learn how to identify, mitigate, and track risks, and facilitate their management within your team.

Identify and assess risks and issues in scrum projects, evaluating likelihood and impact, to plan responses that exploit opportunities or mitigate threats, and differentiate future risks from already occurred issues.

Assess the organization's risk appetite and tolerance to align project risk management with governance and the board. Identify whether the organization is risk-averse, risk-neutral, or risk-seeking for project sizing.

Identify potential risks early using checklists, brainstorming, and a risk breakdown structure, then validate them with risk-based spike experiments to size and mitigate uncertainties.

Identify and assess risks by impact, probability, and proximity; prioritize near-term threats via risk meetings, using probability trees and a probability–impact grid to guide responses and expected monetary value.

Identify and prioritize risks as you would user stories, then integrate them with the product backlog to guide sprint planning and risk mitigation.

Assess risks and plan responses, including mitigation, plan B, and acceptance, while the scrum master facilitates visibility and stakeholder communications for the team's risk responses.

Explore how a risk burndown chart tracks risk exposure across sprints, with ongoing identification and mitigation to reduce risks from 25 to 30 to zero by sprint 7.

Explore how scrum optimizes risk by aligning risk management with project solutions, using transparent practices, sprint reviews, backlog grooming, and iterative delivery to reduce estimation and investment risk.

Explore core Scrum aspects, roles, and organizational structure; manage quality, definition of done, acceptance criteria, change, and risk, while aligning business justification, project vision, and backlog with stakeholders.

As the scrum master, facilitate scrum team's success by managing risk, guiding changes to solutions with information or customer priorities, clarifying roles and authorities, and ensuring value, quality, and justification.

Test your understanding of scrum aspects and the scrum master's facilitation role by taking the chapter 03 quiz and measuring your results.

Learn to facilitate sprint planning, daily stand-ups, sprint reviews, and retrospectives, enabling teams and stakeholders to produce results from the meetings.

Identify key terms and meetings—project vision, sprint planning, daily stand up, review and retrospective—and essential techniques such as planning poker and user stories with scrum boards.

Uncover the scrum master's role and how to facilitate a successful project vision. Clarify the meaning of the project vision.

Define a clear project vision by aligning the business case, organizational objectives, and stakeholder needs to articulate the problem, opportunity, and expected deliverables that realize the shared mission.

Facilitate a project vision meeting with customers, users, and the scrum team to define the problem, use cases, success metrics, and establish a north star for epics and user stories.

Facilitate JAD sessions and requirements workshops to align scope, and enable time-boxed prioritization while fostering collaboration between business and scrum teams in a safe feedback space.

Define the end state with customers, then perform swot analysis to identify internal strengths and weaknesses and external opportunities and threats, guiding risk mitigation and value delivery.

Perform a gap analysis to define existing performance, identify future targets, and determine the changes needed to move from baseline to desired outcomes, including required processes and capabilities.

The project vision meeting yields key deliverables, including a concise vision statement, a formalized charter, and a defined product owner, with an approved budget to drive customer value.

Identify and develop ethics and persona through user group meetings to uncover detailed user stories, then support the product owner in prioritizing them into a product backlog.

Collaborate with the product owner as a scrum master to create a prioritized backlog of user stories by facilitating workshops and using MoSCoW, paired comparisons, and the hundred point method.

Facilitate user workshops to define epics as high-level, estimable user stories describing functionality. Break them into detailed stories with acceptance criteria and prioritize requirements and risks.

Explore how epics capture user stories and how personas map value for stakeholders, using an expense system scenario to illustrate cash flow and timely reimbursement.

Facilitate breaking epics into consumable user stories for a sprint, clarifying who uses the system, what it does, why it's valuable, and how risks and changes are prioritized by value.

Learn to write user stories using a clear format that specifies the role, action, and benefit, such as submitting expenses from any internet connection to ensure timely reimbursement.

Product owners define acceptance criteria for user stories, while scrum masters defend sprint integrity by keeping criteria fixed during the sprint and handling new needs as future stories.

Explore the scrum master's role in sprint planning, using techniques to facilitate coordination between the product owner and team, and guide the assembly and management of the sprint backlog.

During sprint planning, the product owner identifies backlog items and the Scrum team selects the sprint backlog, while the Scrum master facilitates outlining initial tasks within a time box.

Structure sprint planning by aligning the product owner and the scrum team around selected user stories and commitments, then define tasks, estimate effort, and plan delivery.

Facilitate planning poker to help the team estimate a user story's level of effort using S, M, and L cards, and drive consensus through questions and discussion.

Use fist of five to gauge team consensus during planning poker and reviews, having members raise up to five fingers to signal agreement or concerns.

Use story points to describe relative cost and effort, establish a shared benchmark, and measure velocity to size a sprint and convert points to done levels.

Explore traditional estimation techniques such as Delphi and story points to size effort, identify affinities, and provide ranges for the sprint, while tracking how stories convert to done work.

Use index cards or sticky notes to document user stories and tasks with essential details and acceptance criteria, enabling collaboration, accurate sizing, and transparent scrum board visibility.

Break down user stories and epics through functional decomposition into tasks for sprint planning, development, testing, and refactoring. Align efforts to deliver the user story within the sprint window.

Identify and categorize dependencies that affect sprint planning, including mandatory, discretionary, external, and internal dependencies, to determine feasible user stories and sprint velocity.

Facilitate task guesstimation during print planning by using relative measures and story points to estimate effort without detailed costs, and use ideal time to gauge what the team can deliver.

Create the sprint backlog from committed user stories, approved changes, risks, and effort estimates; use the scrum board to organize tasks for this sprint.

Explore how a scrum board creates transparency and tracks user stories from to-do to done. See how tasks are estimated, assigned with initials, and moved through in-process, verification, and completion.

Track sprint progress with a burn down chart that shows remaining hours against days, monitoring user stories and tasks to identify obstacles and stay on schedule.

Explore velocity as a planning tool to track story points per sprint, improve team performance, and guide release planning based on past sprints.

Track sprint metrics that tie work to customer value, focusing on business value delivered and velocity. Assess completed user stories and story points per sprint to gauge team efficiency.

Sprint planning outputs fill scrum board with the backlog of activities and user stories the team commits to deliver, with product owner approval and the scrum master protecting self-directed decisions.

The scrum master facilitates the daily standup with an equal, authority-free team, guiding the daily scrum without dictating work or reporting to a manager.

Learn to run a 15-minute standing daily standup that keeps the team aligned, reports progress, and plans the day, with the scrum master facilitating peer updates and timeboxed discussions.

Guide the standup by asking questions: what did I complete yesterday, what will I complete today, and what impediments am I facing, with the scrum master supporting through action items.

Learn how co-located scrum teams boost collaboration with workrooms, pair programming, and information radiators like a sprint breakdown chart, using index cards and sticky notes to drive productive solutions.

Daily standups surface impediments, update stakeholders, and track risks and dependencies, while the scrum master fosters safe space and autonomy to boost morale and quality through self-organization.

Help the scrum master facilitate grooming of the prioritized product backlog with the product owner during sprint, identify risks, and support changes that affect prioritization and readiness for subsequent sprints.

A scrum master facilitates product backlog review meetings with stakeholders and the SWAT team to prepare the next sprint, assess changes and risks, and ensure the backlog reflects current priorities.

Facilitate ongoing, informal communications among the team and stakeholders to keep the product backlog aligned with evolving business needs, with the scrum master guiding backlog grooming and prioritization.

Explore the sprint review with customers and the sprint retrospective for end-of-sprint product feedback and process improvements.

Demonstrate completed user stories with acceptance criteria and the definition of done, showcase potentially shippable deliverables to stakeholders, and groom the backlog for future releases.

Sprint review yields accepted deliverables; rejected items return to backlog if they miss definition of done or acceptance criteria, and we update risks, release plan, dependencies, and value data.

Learn how sprint retrospectives focus on the team’s collaboration, efficiency, and velocity, with the scrum master facilitating team-building and continual improvement to produce done user stories.

Facilitate a safe, offsite sprint retrospective to identify best practices, new process improvements, and actionable items with owners and deadlines for better team collaboration and workflows.

Identify team engagement levels in sprint retrospectives using anonymous svp self-identification (explorer, shopper, vacationer, prisoner) to tailor discussions and foster constructive participation.

Learn the speedboat retrospective technique to identify engines and anchors affecting team performance, prioritize obstacles, and plan mitigations, enabling the scrum master to remove impediments quickly.

Select two or three KPI metrics to share during sprint retrospectives, focusing on velocity improvements, stakeholder feedback, and progress toward the minimum viable features for production.

Extract actionable improvements and due dates from retrospective sprint, document lessons learned for the scrum guidance body, and capture performance, capacity, availability, redundancy, security, and continuity requirements for prioritized backlog.

Learn how release planning occurs at multiple stages, defining requirements for marketing features and value thresholds, and coordinating deliverables to customers and operations.

Identify when to deliver high-value features in an agile scrum release plan, align stakeholders on delivery timelines, and manage continuous production deployments with phased updates.

Coordinate among product owner, scrum team, and stakeholders to plan value, set sprint length of two to four weeks, determine sprints for minimum functionality, pilot if needed, and adjust backlog.

Identify the need for a pilot, select customer subsets for feedback, and plan scope, timing, rollback, training, transition, and critical success factors to evaluate the pilot's success for broader production.

Align development with organizational release and deployment processes to determine minimum functionality for production, validate deliverables, ensure security compliance, and coordinate user acceptance testing and stakeholder handoffs before deployment.

Coordinate with the product owner and customer stakeholders to improve communications and collaboration across scrum teams using information radiators, the war room, and frequent sprint reviews.

Outline four sprint meetings: planning, daily scrum, sprint review, and sprint retrospective, designed to facilitate communication among product owner, scrum teams, and stakeholders, with elicitation and requirements activities.

The scrum master removes obstacles to performance and facilitates project vision, user group meetings, sprint planning, daily stand-up, and sprint reviews and retrospectives to ensure business value and collaboration.

Explore how the scrum master facilitates collaboration and communication among stakeholders through various meetings, and test your understanding with the chapter 04 quiz.

Explore the effective use of artifacts in scrum, define the scrum master's role in supporting the team through sprints, and scale scrum practices for larger programs and portfolio management.

Learn the key terms: product backlog, sprint backlog, burn down charts, Scrum board, refactoring, and Scrum scrums, and apply them to support a Scrum project.

Explore key Scrum artifacts and their roles in optimizing the product backlog and sprint backlog, and learn how burn down charts support the team during deliverable creation.

The product backlog provides a real-time view of business preferences, listing user needs, changes, and risks, guiding functional and nonfunctional requirements for value-driven, potentially shippable increments each sprint.

Select top backlog items for a sprint, ensure they fit the sprint window and have defined acceptance criteria, then estimate effort with planning poker and story points to plan velocity.

Focus each sprint on delivering potentially shippable solutions, review them with customers, and align with a release plan to provide early value while meeting minimum functional requirements.

Agree on a working deliverables agreement with customers, enabling sign-off and revenue recognition with third parties, then hand off for release planning with documented release notes.

Define generic done criteria approved by the product owner. Attach acceptance criteria to each user story to ensure a potentially shippable vertical slice in the sprint.

During sprint planning, the scrum team and product owner commit to backlog items, estimate work, and plan tasks to deliver user stories, using the sprint backlog and information radiators.

Use a simple scrum board to track sprint backlog items, tasks, and story points, empowering self-organizing teams to assign work, monitor status, and complete user stories.

Drive visibility into the sprint burn down chart to track progress against the plan and keep the team focused on completing work on time through daily updates.

Track sprint progress with a burn down chart showing total work hours and daily completed versus remaining tasks to deliver user stories.

Track release progress with a release burndown that shows how shippable solutions move from product backlog toward production releases in sprints, using empirical data to help product owners plan releases.

Track a release burndown chart across nine sprints and 120 story points to ensure a minimum functional release is ready by sprint nine and delivered to customers.

Explore how the sprint unfolds as the team creates deliverables, and how we identify and remove impediments to the team's performance.

Create deliverables each sprint by building solutions that support user stories, track progress with sprint boards and information radiators, and identify and remove impediments through daily standups.

Promotes Scrum and agile practices to deliver cross-functional, potentially shippable solutions through collaboration and end-to-end sprint activity, while preventing technical debt with test-driven development and refactoring.

Refactoring in this course teaches creating a clean, maintainable baseline by reducing repetition, breaking large methods into reusable routines, clarifying names, and preparing code for future changes through test-driven development.

Explore how scrum scales to support larger programs and portfolios of services. Architect communications between scrums of scrums to roll multiple scrum teams into integrated, larger-scale programs.

Explore how to align multiple scrum teams within a portfolio and program through integration points. Learn how the scrum of scrums and clear communication handle dependencies.

Enable cross-team coordination through a scrum of scrums, a relatively short meeting with one representative from each scrum team who shares detailed dependency information to identify risks and manage dependencies.

Master the four questions for the scrum of scrums: what we did, what we’ll do, dependencies from other teams, and our play planning; use video conferencing when not co-located.

Master the scrums of scrums to boost collaboration and communications, identify dependencies, resolve impediments, and coordinate teams to support larger program and portfolio objectives.

Enable distributed teams to collaborate and communicate effectively despite not co-located, using video conferencing and collaboration tools, and information radiators like scrum boards and burned down charts to ensure participation.

Address co-location challenges in distributed scrum teams by enabling real-time collaboration, pair programming across locations, and visible information radiators, while mitigating impediments through accessible video conferencing and shared artifacts.

Learn how to act as a scrum master by leveraging artifacts, supporting teams during sprint deliverables, facilitating coordination and communication in larger programs and portfolios, and guiding scrums of scrums.

Coordinate with stakeholders, ensuring transparency and visibility into tasks, user stories, and sprint progress. Identify and remove impediments, mitigate impacts, and align teams to manage external dependencies and program objectives.

Explore the specific activities scrum masters engage in to support their teams, and test your knowledge with the chapter 05 quiz to see how you perform.

Serve your teams as a scrum master by ensuring resources and capabilities to deliver user stories and value, while using scrum meetings and artifacts to foster collaboration and visibility.