Firefox OS/Sprint Review: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
== Sprint Review Template == | == Sprint Review Template == | ||
* This | * This should be downloaded from [http://bit.ly/1izpdqU here] and looks exactly like below | ||
[[File:Sprint_Review_Template.png|800px|centre]] | [[File:Sprint_Review_Template.png|800px|centre]] | ||
Revision as of 21:17, 9 May 2014
note: This page is WIP --Bhavana (talk) 14:08, 9 May 2014 (PDT)
Sprint Reviews
- Sprint reviews are recommended to happen every 2 weeks at the end of each sprint cycle, giving everyone an opportunity to look back at all the awesome work that they have done
Sprint Review Template
- This should be downloaded from here and looks exactly like below
Goals
- Lightweight presentation : take 10 mins to build
- Provide visibility into what the team is working on
- Space constrained to keep it relevant and concise
- Demo’s are exciting!!
Deliverable
At the end of each sprint each team is asked to compile a single slide presented at the meeting
- 1. Sprint Delivery : Section contain high level information on what was delivered. (Ideally should be identical to section 4 of previous sprint)
- 2. Demo’s : Information on demo’s on what will be shown along with a recorded video if you can
- 3. Stats : Basic stats about sprint ( Blockers : XX, User stories : YY, Regressions : zz with the bug count and hyperlink to the query)
- 4. What’s Next : This is basically to give information on what the team is going to work next ( Will become Section #1 in the next meeting)
Workflow
Each team will have 5minutes to present and you could pick a few highlights from your user stories.
- Submit this to Release Manger by EOD before review meeting
- Product owner to deliver completed slide
- Demo from a nightly build
- Don’t demo anything not “done”