Time-boxed Sprints (3 weeks)

System / Product / Program

Annual Project
Plan Release 1 Release n
IS Review
Startup 650 Approval
Sprint Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint m

This example illustrates a 3-Sprint Release proceeded by one Sprint (0) of preparation.
The exact number of Sprints in a release will vary depending on the project. All Sprints are 3 weeks long. Sprint 1 is expanded here to show more detail.

Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4

Create Product Backlog

Sprint Review & Retrospective

Estimate Product Backlog
Select Release Backlog Analysis & Design Analysis & Design
Current Sprint Next Sprint
Sprint Planning

In preparation for the

Activities

Create Preliminary Conceptual

See detail of the time- release, the activities Deployment Activities for the Release can
Design
boxed Sprint on the next required for be done as additional Sprints are
Preliminary Conceptual Design
page Implementation are deemed valuable by the deployment
Review Development & Testing performed in the Sprint team.
Current Sprint prior to the release date
Determine Staffing Model Develop
Funding Model & Approval Remediation Pre
Planning daily scrums Planning
Deliverables

Daily: Updated Sprint Burndown

Definition Phase deliverables as
required. Deliverables not required
for the project should be specified.
Business Process & RACM (if needed)
Weekly: Completed increments of functionality
See detail of the time- Client Satisfaction Survey
boxed Sprint on the next Lessons Learned
Sprint: Implementation Plan
page Support Materials
Completed Functionality to achieve Sprint Goal
(e.g. Application Support Binder)
Sprint Review (Functional & Technical Design Review)
Transition Checklist Signoff
Sprint Retrospective

Implementation Review
Inspections

See detail of the time-

Approvals

IS Review Code Reviews IS Change Review

Reviews

boxed Sprint on the next Support Transition Review

Design Reviews Production Change
page Review Signoff
Request
 A Sample Sprint
(3 week time-box, weekend days not shown)

Sprint Planning
Daily Pre-Sprint
Day 13 Scrum
Who When What Deliverables
Planning for Product Owner Beginning of each Review Sprint Goal Conceptual Design Signoff
Daily Next Sprint ScrumMaster Sprint. Select Backlog Items Sprint Backlog
Day 14 Scrum
Scrum Team No gap between prior Start Functional Design Initial Burndown Chart
Prior Daily Sprint Review Sprint Sol Arch † Sprint and Sprint Start Technical Design
Sprint Day 15 Scrum Functional & Technical Retrospective EDM † Planning Start Test Plan
Tech Arch † Time-boxed to 4 Task Breakdown
Daily Sprint These activities occur each Sprint as hours Task Estimation
Day 1 Scrum determined by the Scrum team:
Planning Team Commitment
Daily Finish Analysis & Design: Current Sprint
Day 2 Scrum Continue Analysis & Design: Next Sprint Daily Standup
Create Functional Design Who When What Deliverables
Sprint (3-weeks)

Daily Create Technical Design

Days 3 - 7 Scrum Product Owner Every day at the Each person communicates: No formal deliverables
ScrumMaster same time 1.What did you do yesterday
Finish Development & Testing: Current
Daily Mid-Sprint Scrum Team Time-boxed to 15 2.What are you doing today Outcomes include follow on
Day 8 Sprint
Scrum Check minutes 3.What is in your way meetings, task list updates,
Develop (code, etc.)
Other stakeholders Start on time action items.
Daily Perform Build Daily
Days 9-12 can observe to Sprint Burndown is Avoid during the Daily Scrum:
Scrum Conduct Unit & Integration Testing • Details
learn, but can NOT updated prior to
Conduct System & Regression Testing ‡ • Metrics reporting
talk or ask Daily Scrum
Daily Conduct Performance Testing ‡ • Problem Solving
Day 13 Pre-Sprint questions until after
Scrum the Daily Scrum • Burndown updates
Planning for Functional / Technical Inspections & Design
Daily Next Sprint Review
Day 14 Scrum
Sprint Review – Technical, Functional Review & Design Inspection
Daily Sprint Review Sprint
Day 15 Scrum Who When What Deliverables
Functional & Technical Retrospective
Product Owner End of the every Review Sprint Goal and Selected Demonstrated Working
Next Daily Sprint ScrumMaster Sprint Backlog Items System
Day 1 Scrum
Sprint Planning Scrum Team Demonstrate Functionality Review SIgnoff
Stakeholders Functional Design Review Updated Product Backlog
Sol Arch, EDM, Technical Design Review Topics for Retrospective
Tech Arch Collect comments and changes
Interested Observers to the Product Backlog
During the Sprint, the Scrum
Sprint Review & Retrospective

(attendance is not
Analysis & Design Analysis & Design Team determines the limited)
Current Sprint Next Sprint sequence of the
Sprint Planning

implementing the tasks in Sprint Retrospective

the Sprint Plan. This is a
typical model of when Who When What Deliverables
different activities occur Product Owner After Every Sprint Review Items from Sprint Review Lessons Learned List
Development & Testing during a Sprint. The ScrumMaster Review Review Improvement Goals for Improvement Goals
Scrum Team the current Sprint
Current Sprint sequence of the Sprint tasks
Sol Arch † Brainstorm things to start, stop,
will vary based on that
Sprint goal, individual EDM † and maintain doing
Remediation Pre
availability, etc. Tech Arch † Select improvement goals for
Planning daily scrums Planning
time
Next Sprint

† = as needed