Changes between Version 27 and Version 28 of PROCESS


Ignore:
Timestamp:
11/13/08 16:48:22 (17 years ago)
Author:
kyli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PROCESS

    v27 v28  
    114114Each taken task in the current sprint should pass trough the following phases: 
    115115 
    116  * '''analyzing''' 
     116 * '''analysis started''' 
    117117  * task is waiting to be taken, and someone to determine What should be done? 
    118118  * to learn how to write good analysis, see [wiki:PLATFORM_STANDARDS_ANALYSIS Platform Standards Analysis] 
    119119  * there should be at least one example how to do one or more things that should be done. 
    120120  * It should take not more than 0.25 of the task effort. 
    121  * '''analyzed''' 
     121 * '''analysis finished''' 
    122122  * It is already determined what should be done. 
    123123  * the task is waiting for review (Wait for the review of the analysis before starting the design otherwise your work can be for nothing!) 
    … …  
    125125  * the reviewer look through the analysis to see if it is correct 
    126126  * the analysis should apply to [wiki:PageTemplates/TaskPageTemplate#Analysis its template] 
    127  * '''analysis accepted''' - the reviewer decides that the analysis of the task is correct 
    128  * '''designing'''  
     127 * '''analysis ok''' - the reviewer decides that the analysis of the task is correct 
     128 * '''design started'''  
    129129  * The implementer is designing the task or in other words tries to decide How it should be done? 
    130130  * It is not compulsory but recommended that the design should be made by the implementer. 
    … …  
    132132  * Designing is not only getting an idea of how to do it, but a detailed concept, step by step. 
    133133  * For many tasks the design phase should take most of the time. 
    134  * '''designed''' 
     134 * '''design finished''' 
    135135  * The task is already determined how should be done. 
    136136  * It is designed and is waiting for review. 
    … …  
    138138  * The reviewer look through the design to see if it is correct. 
    139139  * The reviewer can imagine himself as an implementer and see if he/she can implement the task following the design without problems. 
    140  * '''design accepted''' - The reviewer decides that the design of the task is correct. 
    141  * '''implementing''' 
     140 * '''design ok''' - The reviewer decides that the design of the task is correct. 
     141 * '''implementation started''' 
    142142  * The implementer makes an attempt to complete the task. 
    143143  * He/she should follow the design strictly. 
    144144  * He/she should write in Implementation section of the task the result of the implementation. 
    145  * '''implemented''' - The implementer decides that the implementation of the task is ready. 
     145 * '''implementation finished''' - The implementer decides that the implementation of the task is ready. 
    146146 * '''review''' - The reviewer look through the implementation to see if it is correct. 
    147  * '''implementation accepted''' 
     147 * '''implementation ok''' 
    148148  * The reviewer decides that the implementation of the task is correct. 
    149149  * The implementation section must be filled. 
    150  * '''testing''' - There should be appropriate tests written for the task. 
    151  * '''tested''' - Testing state is done, waiting for review 
     150 * '''test started''' - There should be appropriate tests written for the task. 
     151 * '''test finished''' - Testing state is done, waiting for review 
    152152 * '''review''' 
    153153  * the reviewer looks for missing or wrong tests 
    154154  * if there are any decides they can be added later 
    155155  * if they are too important or wrong they should be fixed - the review fails. 
    156  * '''testing accepted''' 
     156 * '''test ok''' 
    157157 
    158158 * Notes