Changes between Version 1 and Version 2 of INTERNAL_BACKLOG_STRUCTURE_R2


Ignore:
Timestamp:
01/19/09 11:13:23 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • INTERNAL_BACKLOG_STRUCTURE_R2

    v1 v2  
    33[[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|)]] 
    44= 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  
    75== 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  
     6Internal backlog structure improves backlog usability 
    107== Task requirements == 
    11 ^(Necessary requirements that the task must fulfill.)^ 
    12  
     8 * Add an Improvements sheet which contains improvement suggestions. Required fields: 
     9  * Name 
     10  * Description 
     11  * Date 
     12  * Reporter 
     13  * Status (applied, not applied, won't be applied) 
     14  * Comments 
    1315== Task result == 
    1416^(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.))^