Changes between Version 2 and Version 3 of UNPLANNED_FEATURE_SCHEDULE_R0


Ignore:
Timestamp:
11/29/08 07:36:59 (16 years ago)
Author:
sriggins
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UNPLANNED_FEATURE_SCHEDULE_R0

    v2 v3  
    1818Provide a schedule of releases that acts as an overview for the project to ensure the project is on track. 
    1919 
     20== Task requirements == 
     21^(Necessary requirements that the task must fulfill.)^ 
     22 
     23I have NO idea how this is different than Task Result. 
     24 
    2025== Task result == 
    2126Document approved by the team and Nick giving an overview of the schedule and what can be expected in each release. 
     
    2429This can either be a stand alone document, a google document or a wiki page. 
    2530 
     31== Related == 
     32^(Here you can add related tasks that could be useful or helpful.)^ 
     33 
    2634== How to demo == 
    2735Provide a link to the document. 
     36 
     37= Design = 
     38 
     39PAP: if you think you can design a schedule, then ok :)  I have no idea what design means in terms of a schedule 
    2840 
    2941= Implementation = 
    3042^(Implementation results should be described and linked here (from the wiki or the repository))^ 
    3143 
     44= Testing = 
     45 
     46How does one test a schedule? 
    3247 
    3348= Comments =