Analysis
Overview
Provide a schedule of releases that acts as an overview for the project to ensure the project is on track.
Task requirements
The release schedule document needs to give an overview of each release, including:
- What can be expected to be functioning in each release
- This does not need to be overly detailed, as it is very hard to guess every feature that will be completed due to unforeseen issues
- We want this to be a guideline that others can use to ensure the health of the project
- When each release will be made available
Task result
Document approved by the team and Nick giving an overview of the schedule and what can be expected in each release.
Implementation idea
The schedule data will be collected from the task index, the resources spreadsheet and from Milo.
Related
UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0
UNPLANNED_FEATURE_SCHEDULE_DELIVERY_R0
How to demo
Provide a link to the document, and email the link to the team for UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0.
The schedule can be found here: RELEASE_SCHEDULE
Design
- The schedule will have 11 releases
- Each release date was decided upon by Steve, Milo and Nick
- Each release date will follow the previous sprint by approximately 4-5 weeks, to allow for testing and bug fixing
- The dates for each release are:
- Release 1 - 08-12-15
- Release 2 - 09-02-13
- Release 3 - 09-03-15
- Release 4 - 09-04-15
- Release 5 - 09-05-15
- Release 6 - 09-06-15
- Release 7 - 09-07-15
- Release 8 - 09-08-15
- Release 9 - 09-09-15
- Release 10 - 09-10-01
- Release 11 - 09-10-15
- Each release may contain the following:
- New features expected in the release
- Release phase (alpha, beta)
- Goals for this release (bugs fixed, etc)
Implementation
The RELEASE_SCHEDULE was implemented as a wiki page and can be found here
Testing
N/A
Comments
Don't forget to link the resulting document in PROJECT_OVERVIEW during some of the next revisions of this task. (kyli)