Changes between Initial Version and Version 1 of INTERNAL_BACKLOG_STRUCTURE_R2


Ignore:
Timestamp:
01/19/09 10:17:49 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • INTERNAL_BACKLOG_STRUCTURE_R2

    v1 v1  
     1[[BackLinksMenu]] 
     2 
     3[[TicketQuery(summary=INTERNAL_BACKLOG_STRUCTURE_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] 
     4= Analysis = 
     5^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^ 
     6 
     7== Overview == 
     8^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^ 
     9 
     10== Task requirements == 
     11^(Necessary requirements that the task must fulfill.)^ 
     12 
     13== Task result == 
     14^(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.))^ 
     15 
     16== Implementation idea == 
     17^(It is advisable to include some rough implementations ideas.)^ 
     18 
     19== Related == 
     20^(Here you can add related tasks that could be useful or helpful.)^ 
     21 
     22== How to demo == 
     23^(In this section you must add instructions for the demo of the task.)^ 
     24 
     25= Design = 
     26 
     27= Implementation = 
     28^(Implementation results should be described and linked here (from the wiki or the repository))^ 
     29 
     30= Testing = 
     31 
     32= Comments = 
     33^(Write comments for this or later revisions here.)