A Professional Introduction to Scrum

Explore how the Scrum framework enables self-organizing, cross-functional teams to deliver high-value outcomes through empirical learning, iterative sprints, and transparent roles, artifacts, and events.

Learn how empiricism guides scrum through transparency, inspection, and adaptation, using the product backlog, sprint backlog, and increment to gain feedback and adapt product goals.

Identify how you use empiricism in your environment and the benefits you gain. Note areas for more transparency and how frequent feedback loops could improve your work with the worksheet.

Explore how a small, cross-functional, self-organizing Scrum team delivers a valuable increment each sprint, guided by product owner, developers, and Scrum Master through collaboration, boundaries, and shared goals.

Learn how the product owner maximizes product value by managing the backlog, setting a clear vision, aligning with business strategy, and collaborating with the scrum team and stakeholders.

Developers in a scrum team collaborate with the product owner to deliver a usable increment with quality, managing the sprint backlog and pursuing the sprint goal through cross-functional, self-organizing work.

Empower the Scrum team through servant leadership, fostering empiricism, removing impediments, and coaching for self-organization, cross-functionality, and value-driven delivery.

Explore how the product backlog serves as the single source of truth for planned value, detailing PBIs, ordering, and refinement to create transparency and maximize value through emergence.

The sprint backlog translates the product backlog into a transparent, team-owned plan for the current sprint, guided by the sprint goal and the emergent plan to deliver a done increment.

Produce the increment as the usable value produced by the sprint backlog, increase transparency, enable faster feedback, and guide investment decisions through thorough testing and a solid definition of done.

Explore how artifact commitments enhance transparency and guide progress toward the product goal and product backlog, the sprint goal and sprint backlog, and the definition of done for the increment.

Explore how time-boxes power scrum events by promoting transparency, inspect-and-adapt learning, and rapid decision making, while reducing waste and preventing analysis paralysis in sprint cycles.

The sprint is a time-boxed container that starts with planning and ends with a retrospective to create a usable increment of value, fostering focus, predictability, and freedom within cadence.

Developers inspect progress toward the sprint goal and adapt the sprint backlog in a 15-minute daily scrum, surfacing impediments and coordinating next steps.

the sprint review brings the scrum team and stakeholders together to inspect the increment, gather feedback, and adapt the product backlog for future sprints within the four-hour timebox.

Learn how the sprint retrospective lets the Scrum team inspect processes, tools, and interactions, and produce an actionable improvement plan for the next sprint within the timebox.

Explore how the five scrum values—focus, openness, courage, commitment, and respect—bring the scrum framework to life by enabling collaborative teamwork and empiricism, transparency, and adaptation.

Reflect on how the five scrum values—focus, openness, courage, commitment, and respect—appear in your current environment, and explore how they can deliver value more frequently, reduce frustration, and boost creativity.

Scrum fits teams facing complexity and change, delivering value sooner through iterative, incremental work, with transparency, stakeholder collaboration, and rapid feedback to validate assumptions.

Discover the scrum framework as a value-driven, empirical approach to complex work, with roles, artifacts, events, and five values: focus, openness, courage, commitment, and respect, guided by the scrum guide.

apply scrum in practice by examining key process decisions and defining your product, value, and done criteria. assess sprint length factors and identify what you need to start scrum.

Define value to enable transparency, guide inspection, and adapt toward valuable outcomes. Let the product owner maximize value by aligning vision, value, and validation with empirical data.

Develop a clear definition of done as a checklist that ensures transparency of the increment, while addressing testing, integration, usability, performance, maintainability, security, and documentation.

Define your product by clear boundaries and value delivery, guided by a single product owner and backlog, and validate value through conversations, incremental delivery, and shared definition of done.

Reflect on how you create value and the definition of done, define your product, and paint its boundaries using the worksheet to start delivering value iteratively and incrementally.

Learn how to refine the product backlog to break down value into small, well-defined PBIs, balance detail with waste using the Goldilocks principle, and improve transparency, value, and forecasting.

Start scrum with cross-functional team of developers, product owner with a vision, and a scrum master; plan sprints, set sprint goals, and establish a definition of done to ensure quality.

Explore key decisions to start scrum with your team using the getting started with scrum canvas, and prepare for your first sprint with a 30–60 minute worksheet.

Apply an empirical approach to planning and forecasting with scrum, delivering value iteratively and incrementally with quality while deciding sprint length and starting your first sprint.

Plan actively with scrum by contrasting plan-driven forecasts with value-driven, empirical planning. Collaborate to align teams, enable emergence and adaptation, and guide inspection with lightweight, up-to-date plans.

Use relative estimation to size backlog items for sprint fit, support forecasting, and guide backlog ordering, while embracing that estimates are imperfect and ongoing learning.

Forecast delivery by combining estimates with past performance using velocity and burnup charts, applying date-based and scope-based forecasting, and acknowledging the cone of uncertainty.

Explore agile budgeting and scheduling with scrum, contrasting date-based and scope-based forecasting. Learn how the product owner and backlog enable value delivery, transparency, and rapid adaptation within fixed sprint cycles.

We build blocks to plan for unpredictability in complex work, embracing change as value with a lightweight approach; forecasts and estimates are educated guesses guided by experience.

Master scrum as a journey guided by context-driven practices, uncertainty, and empiricism. Stay disciplined in tailoring practices to your team, improving transparency, and forecasting beyond sprints.

Learn a four-dimension model to improve scrum practice: team identity, team process, product value, and organization, grounded in an agile mindset, empiricism, and teamwork for greater agility.

Explore servant leadership within scrum, focusing on empowering teams, measuring success by others' growth, and fostering an agile, self-organizing culture that delivers high-quality value.

Focuses on agility and scrum to deliver value iteratively through small self-organizing teams, guided by empiricism and frequent feedback to adapt to change. Embrace the disciplined journey of continuous improvement.