Changes between Version 1 and Version 2 of UNPLANNED_FEATURE_SCHEDULE_R0

Timestamp:

11/27/08 02:16:28 (16 years ago)

Author:

sriggins

Comment:

--

UNPLANNED_FEATURE_SCHEDULE_R0

@@ -6 +6 @@
 
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
+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 we're on track.
-
-== Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+Provide a schedule of releases that acts as an overview for the project to ensure the project is on track.
 
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+Document approved by the team and Nick giving an overview of the schedule and what can be expected in each release.
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
-
-== Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
+This can either be a stand alone document, a google document or a wiki page.
 
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
-
-= Design =
+Provide a link to the document.
 
 = Implementation =
 ^(Implementation results should be described and linked here (from the wiki or the repository))^
 
-= Testing =
 
 = Comments =