Agile Scrum for Beginners

Explore how Agile delivers value through time-boxed, iterative increments, with cross-functional teams and Scrum guiding fast, customer-aligned delivery and continuous improvement.

Discover how scrum provides a lightweight, time-boxed framework for agile product development, outlining events, artefacts, rules, and values to enable iterative, incremental delivery.

Explore how scrum theory combines empiricism, lean thinking, and an iterative, incremental approach with transparency, inspection, and adaptation to drive quick delivery and manage risk.

Empower a small, cross-functional, self-managing Scrum team—one Scrum Master, one Product Owner, and developers—sharing a single product backlog to deliver a valuable increment each sprint at a sustainable pace.

Maximize product value through accountable backlog management by the product owner, clearly communicating the product goal, ordering backlog items, and keeping the backlog transparent, visible, and aligned with stakeholders' needs.

Facilitate scrum as a servant leader, accountable for the team's effectiveness, removing impediments, coaching self-management and cross-functionality, and guiding product backlog and definition of done with the product owner.

Developers, as Scrum team members, commit to creating aspects of a usable environment, draft sprint backlog plan, adapt toward the sprint goal, uphold the definition of done, and maintain accountability.

Explore how scrum events, including sprint planning, sprint review, sprint retrospective, and daily scrum, enable inspect and adapt through transparency and empiricism, with time-boxed, same-time practices to reduce complexity.

Sprints are the heartbeat of Scrum, fixed-length cycles that turn ideas into value, typically two weeks, with planning, daily Scrum, review, and retrospective.

Collaborate to define the sprint goal and select backlog items. Finalize the sprint backlog with a plan to deliver an increment meeting the definition of done.

Only the product owner can cancel a sprint before it ends if sprint goal becomes obsolete due to market or technology changes; completed items are reviewed and incomplete items re-estimated.

Attend the daily scrum to inspect progress toward the sprint goal, adapt the sprint backlog as needed, and produce an actionable plan for the next day.

Conduct a collaborative, time-boxed sprint review to inspect the sprint outcome, adjust the product backlog, and plan next steps with the Scrum team and stakeholders.

Inspect the last sprint to identify meaningful improvements in people, interactions, processes, and tools. The Scrum Master guides a time-boxed retrospective that translates improvements into the next sprint backlog.

Explore Scrum artifacts, including product backlog, sprint backlog, and increment, and how commitments to product goal, sprint goal, and definition of done promote transparency and empiricism.

Explore the product backlog, an emergent, ordered list that guides scrum work, with refinement, sizing, and readiness for sprint planning toward the product goal.

Break down the product backlog into themes, epics, user stories, and tasks to guide sprint work from the end user perspective.

Use release burn up charts to track plan versus completed work for a release, while burn up charts show completed work against scope and burn down charts show remaining work.

The sprint backlog combines the selected product backlog items and an actionable plan to deliver the increment, updated continuously by developers to meet the sprint goal and enable continuous improvement.

Deliver usable, verified increments by meeting the definition of done, ensuring transparency at sprint reviews and providing value; if DoD standards exist, teams follow them; otherwise create an appropriate DoD.