ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Sprint Schedule
2
Week 1Weekly FocusMondayTuesdayWednesdayThursdayFriday
3
Scrum teamRamp up new sprintSprint PlanningStand UpStand UpStand UpStand Up
4
WorkshopDeploymentDeploymentProduct Demo
(Tech/Product)
5
Estimation
6
Engineering beginsCommittment
7
Engineering LeadsStory kick-off meetings
Ad hoc support
Engineering
Grooming
8
QATest suite preparation
Testing
9
ProductStakeholder meetings
Story writing
Grooming
10
Week 2Weekly FocusMondayTuesdayWednesdayThursdayFriday
11
Scrum teamEngineering
Testing
Bug fixes
Stand UpStand UpStand UpStand UpStand Up
12
Product Demo
(Tech/Product/Stakeholders)
13
Retrospective
14
Code CompleteDiscovery
15
Engineering LeadsStory kick-off meetings
Ad hoc support
Engineering
Grooming
Engineering ends
16
QATesting
17
ProductSprint planning
Story writing
Grooming
Product review
18
19
20
Legend
21
Sprint PlanningThis should be a relatively simple meeting to do some capacity planning and ascertain what the team can commit to in the sprint. The team should already be intimately aware of the prioritized backlog and what is coming up.
22
Stand UpThis is the daily meeting where the scrum team get to share what they are working on, what is complete, what challenges they are facing, ask for help, offer help and provide insight into how work is progressing. Any highlighted dependencies should be tracked here and also assigned an owner. Any blockers should also be discussed and assigned an owner so they can be removed.
23
GroomingThis should happen continuously but I suggest penciling in at least 1 formal weekly meeting to ensure they happen. This meeting is an opportunity to review, reprioritize and strengthen the backlog for the upcoming sprints. Stories should be matured with acceptance criteria and socialized amongst the scrum team in preparation for the Sprint Planning meeting.
24
Product DemoThe scrum team should demo internally to the team at the end of each week and then to our stakesholders at the end of the sprint.
25
RetrospectiveThe scrum team discuss the last sprint, good and bad and find ways to overcome challenges iteratively. Be honest, be open minded, be nice!
26
Engineering beginsEngineering gets underway.
27
Engineering endsEngineering ends on this day, without exception.
28
Scrum TeamThis is comprised of Engineering, QA and Product.
29
Mid-Sprint Review
In addition to our daily standup, this is an excellent way to keep everyone up to date, to understand the progress towards the objectives and to make sure that the projects are being communicated clearly.
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100