Version 2 (modified by sriggins, 16 years ago) (diff) |
---|
Analysis
The release schedule document needs to give an overview of each release, including:
- What can be expected to be functioning
- 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
- This could be an iteration number or a date. Nick?
Overview
Provide a schedule of releases that acts as an overview for the project to ensure the project is on track.
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
This can either be a stand alone document, a google document or a wiki page.
How to demo
Provide a link to the document.
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Comments
(Write comments for this or later revisions here.)