GuideRolesEventsWorkflow

Scrum Framework

Scrum Framework Flow

Interactive Workflow

Click any element to explore
SCRUM TEAMTHE SPRINT (≤ 1 MONTH)ARTIFACTSimprovements feed next Sprintadapts
ProductBacklog
SprintBacklog
Increment
ProductOwner
ScrumMaster
Developers
SprintPlanning≤ 8 hours
DailyScrum15 min
SprintReview≤ 4 hours
SprintRetro≤ 3 hours
BacklogRefinementCommitment · Focus · OpennessRespect · Courage
artifact

Product Backlog

The single, ordered list of everything needed to improve the product. Owned by the Product Owner. Items at the top are refined, estimated, and ready for Sprint Planning.

Single source of work for the Scrum Team
Ordered by value, risk, and dependencies
Continuously refined (~10% of Sprint capacity)
Product Goal = long-term commitment
artifact

Sprint Backlog

The Sprint Goal (why) + selected PBIs (what) + the plan for delivering them (how). Owned by Developers. Updated daily.

Created during Sprint Planning
Owned and managed by Developers
Updated daily as more is learned
Sprint Goal = single objective commitment
artifact

Increment

A concrete stepping stone toward the Product Goal. Each is additive, verified, and usable. Multiple Increments may be created per Sprint.

Must meet Definition of Done
Additive to all prior Increments
Multiple per Sprint possible
Definition of Done = quality commitment
role

Product Owner

Accountable for maximizing product value. Owns the Product Backlog — its content, ordering, and transparency. One person, not a committee.

Defines and communicates Product Goal
Orders the Product Backlog
Ensures backlog is transparent and understood
Accepts work at Sprint Review
role

Scrum Master

Accountable for establishing Scrum and the team’s effectiveness. A true leader who serves the team, PO, and organization.

Facilitates Scrum events
Removes impediments
Coaches self-management
Serves team, PO, and organization
role

Developers

Committed to creating usable Increments each Sprint. Self-managing and cross-functional. Decide who, what, when, and how.

Create the Sprint Backlog
Adhere to Definition of Done
Adapt plan daily toward Sprint Goal
Hold each other accountable
event≤ 8 hours

Sprint Planning

Initiates the Sprint. Entire Scrum Team defines Sprint Goal (Why), selects items (What), creates plan (How).

Topic 1: Why is this Sprint valuable?
Topic 2: What can be Done?
Topic 3: How will work get done?
Timebox: ≤ 8 hrs (1-month Sprint)
event15 min

Daily Scrum

15-minute event for Developers. Inspect progress toward Sprint Goal, adapt Sprint Backlog, create plan for next 24 hours.

Owned by Developers
Any format that focuses on Sprint Goal
Surface impediments immediately
Not a status meeting
event≤ 4 hours

Sprint Review

Scrum Team presents results to stakeholders. Progress toward Product Goal discussed. Attendees collaborate on what’s next.

Working session, not a presentation
Stakeholders provide real feedback
Product Backlog may be adjusted
Timebox: ≤ 4 hrs (1-month Sprint)
event≤ 3 hours

Sprint Retro

Team inspects how the Sprint went — individuals, interactions, processes, tools, DoD. Identifies most impactful improvements.

Plan ways to increase quality
Most impactful improvements first
May add items to next Sprint Backlog
Timebox: ≤ 3 hrs (1-month Sprint)
activity

Backlog Refinement

Ongoing activity (~10% of capacity). Team adds detail, estimates, and order to PBIs. Not a formal Scrum event, but critical for smooth Sprint Planning.

Break items into smaller pieces
Add acceptance criteria & estimates
Identify dependencies
~10% of Sprint capacity