Changes between Version 2 and Version 3 of UNPLANNED_FEATURE_SCHEDULE_R0
- Timestamp:
- 11/29/08 07:36:59 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UNPLANNED_FEATURE_SCHEDULE_R0
v2 v3 18 18 Provide a schedule of releases that acts as an overview for the project to ensure the project is on track. 19 19 20 == Task requirements == 21 ^(Necessary requirements that the task must fulfill.)^ 22 23 I have NO idea how this is different than Task Result. 24 20 25 == Task result == 21 26 Document approved by the team and Nick giving an overview of the schedule and what can be expected in each release. … … 24 29 This can either be a stand alone document, a google document or a wiki page. 25 30 31 == Related == 32 ^(Here you can add related tasks that could be useful or helpful.)^ 33 26 34 == How to demo == 27 35 Provide a link to the document. 36 37 = Design = 38 39 PAP: if you think you can design a schedule, then ok :) I have no idea what design means in terms of a schedule 28 40 29 41 = Implementation = 30 42 ^(Implementation results should be described and linked here (from the wiki or the repository))^ 31 43 44 = Testing = 45 46 How does one test a schedule? 32 47 33 48 = Comments =