Firefox OS/Sprint Review: Difference between revisions
Jump to navigation
Jump to search
m (Lakrits moved page FirefoxOS/Sprint Review to Firefox OS/Sprint Review: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling of its name is consistent with the conten...) |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Sprint Reviews = | = 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 reviews are recommended to happen every 2 weeks(at the end of each sprint cycle) in the feature development phase, giving everyone an opportunity to look back at all the awesome work that they have done | ||
== Sprint Review Template == | == Sprint Review Template == | ||
| Line 22: | Line 22: | ||
= Workflow = | = Workflow = | ||
Each team will have 5minutes to present and you could pick a few highlights from your user stories. | * Each team will have 5minutes to present and you could pick a few highlights from your user stories. | ||
* Submit this to Release | * Submit this to Release Manager by EOD before review meeting | ||
* | * EPM to deliver completed slide | ||
* Demo from a nightly build | * Demo from a nightly build | ||
* Don’t demo anything not “done” | * Don’t demo anything not “done” | ||
= | == More Instructions == | ||
* | * Make a copy of the template from [http://bit.ly/1izpdqU here] | ||
* Save anywhere on your google drive and make required edits to add your team's status | |||
* Then move or copy it to a sub-folder for that sprint [https://drive.google.com/a/mozilla.com/#folders/0B6kijnluCiEsNXltMUxiNDhiWW8 here] which is the location for Sprint #n Demo's making sure to export as a team_2.0sprintn in Google "Presentation" format | |||
Latest revision as of 14:09, 1 February 2015
Sprint Reviews
- Sprint reviews are recommended to happen every 2 weeks(at the end of each sprint cycle) in the feature development phase, 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 Manager by EOD before review meeting
- EPM to deliver completed slide
- Demo from a nightly build
- Don’t demo anything not “done”