MDN/Archives/Dev Milestones: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
The Kuma development team is using the Scrum method of agile software development. Our sprints are two weeks and code is pushed weekly. See below for details on what bugs are addressed in each sprint. | The Kuma development team is using the Scrum method of agile software development. Our sprints are two weeks and code is pushed weekly. See below for details on what bugs are addressed in each sprint. | ||
=== Sprint ending July | === Sprint ending July 18, 2012 === | ||
* Meetings | * Meetings | ||
Revision as of 23:34, 6 July 2012
Product backlog (running list of all remaining work)
Timeline
- 8-Jun - general testing period starts
- 14-18 June - focused test weekend - kumascript & translation
- 21-24 June - focused test weekend - edit & add content (wiki pages, files, code samples)
- 25-30 June - bug hunt!
- 30-June - deki shut off for updates (browse only) - final content migration, link to kuma "beta" for browsing
- 1-9 July - writing/editing on kuma, continue testing, verify bug fixes
- 10-July - cutover
Development Sprints
The Kuma development team is using the Scrum method of agile software development. Our sprints are two weeks and code is pushed weekly. See below for details on what bugs are addressed in each sprint.
Sprint ending July 18, 2012
- Meetings
- Artifacts
Sprint ending 03-July-2012
- Meetings
- Artifacts