6. Program start
•SOW, budget allocated
•Capacity as monthly User Story
Points
•Supplier feature crew ramp-up
•Backlog initiation
Quarterly planning
•Supplier capacity is adjusted at
Quarter boundaries
•Microsoft to maintain 2 sprints
worth of user stories meeting DoR
•Schedule UAT or no UAT
Delivery by sprint
•2 weeks sprints
•Independent Feature Crew and
Scrum
•Sync at Scrum of Scrums
•CD/CI, shared code branch and pre-
prod environment
Warranty period
•Bugs fixed per SLA “or else” penalty
system
•No extra charge to Microsoft for
supplier poor job

7. Backlog grooming
[Microsoft]
• Maintains 2 sprints worth of user stories per
Definition of Ready
• User story points draft
Review and bid
[Supplier]
• User story point bid
Execution and delivery
[Supplier]
• 40% paid when self-assess meet Definition
of Done
• 2 weeks sprints
Review for acceptance
[Microsoft]
• 40% paid when accepted per Definition of
Done requirements
• 5 work days time-bound after sprint
Warranty Period
[Supplier]
• Time-bound
• 20% paid at UAT Exit
• Penalty system for significant Prod issues

8. “Framework Design Guidelines”