Sunday, 28 April 2013

Sprint Checklist

Article written by Sreenivas Mothukuru

After working for many years on projects developed using Agile (Scrum) I came up with below sprint checklist (3 week sprint). Please go over below items and help me fine tune the checklist. Thank you!



Before Sprint Starts
1
Book conference room for backlog grooming meeting
2
Review prioritized user stories in product backlog before attending backlog grooming meeting
3
Attend backlog grooming meeting
4
Book conference room for sprint planning meeting

Day 1
5
Review user stories in sprint backlog before planning meeting
6
Come up with Dev tasks for (already groomed) user stories
7
Come up with QA tasks for (already groomed) user stories
8
To come up with QA and Dev estimates
9
Identify (module/code) dependencies
10
Attend sprint planning meeting
11
Come up with testing scope document

Day 2
12
Review the priority of user stories
13
Everybody must have clear understanding about stories committed, otherwise get clarifications from Product Owners
14
Make sure all user stories have tracking bugs/tickets
15
Finalize testing scope document
16
Create and upload (unit) test cases
17
Arrange test case review meeting

Day 3 to 12
18
Update relevant information (i.e "Post Resources", modules touched, dependencies, CM/DBA tickets, Change Requests, etc.)
19
Verify the correctness of builds deployed onto QA environments
20
Work with CM team to resolve environment specific issues (if any)
21
Update test case document as per the feedback/suggestions received
22
Check Definition of done, details about WHAT and WHEN user stories will be DEV and QA complete, testing notes, etc.
23
Check whether roll-back plan is identified for all user stories?
24
Identify user stories which need Demos
25
Update QC/Rally/etc. with QA / Dev status
26
Test code changes on Dev boxes before pushing the changes to QA environment
27
Deploy code to QA after development and initial testing on DEV boxes is complete
28
Do Dovetails after every release
29
Update release wiki with dovetail information
30
Make sure all DB changes are committed to SVN with corresponding tracking ID
31
Create/Modify Hudson jobs every time the branch name changes
32
Run automation scripts in QA and Stage environments regularly
33
Coordinate with other dev teams (about release work distribution)
34
Coordinate with other QA teams (about release work distribution)
35
Communicate with Dev and Scrum master on sprint related issues (in any)
36
Ensure all user stories are in verified in QA environment
37
Ensure Performance testing is done for stories (if required) in QA
38
Ensure required hardware/software/applications/etc is set for Performance testing for stories (if required) in Stage
39
Complete Demos
40
Follow up with the user stories that needs to be verified and accepted by product Owners
41
Provide acceptance in QA environment
42
Send QA acceptance email communication to all scrum teams
43
Create release branches
43
Create release RPMs

Day 13 & 14
44
Ensure all user stories are verified in Stage environment
45
Ensure Performance testing in complete in Stage
46
Provide Stage team environment acceptance
47
Send stage acceptance email to all scrum teams

Day 15
48
Update Definition of done
49
Participate in the release
50
Verify user stories in Production
51
Provide Production environment acceptance
52
Send Production acceptance email to all scrum teams

Post Release Work
53
Follow up with the user stories which needs to be verified by Product Owners after release
54
Close all tracking tickets (bugs / user stories) which went to production
55
Arrange retrospective meeting, discuss with team and come up with retrospective notes
56
Share retrospective information with entire team

- Mothukuru Sreenivas

No comments:

Post a Comment