Changes between Version 1 and Version 2 of PROCESS_R3


Ignore:
Timestamp:
01/19/09 08:33:05 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PROCESS_R3

    v1 v2  
    22 
    33[[TicketQuery(summary=PROCESS_R3, 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  
    5  
    6  
    74= Analysis = 
    8 ^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^ 
    9  
    105== Overview == 
    11 ^(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.)^ 
    12  
     6The tasks for imroving the process define rules that ease the work process. 
    137== Task requirements == 
    14 ^(Necessary requirements that the task must fulfill.)^ 
    15  
     8 * Throughly review [wiki:PROCESS] 
     9  * See comments section for some improvement ideas 
     10 * Create sub-pages for the processes of different teams 
     11  * [wiki:PROCESS/Analysis] 
     12  * [wiki:PROCESS/Base] 
     13  * [wiki:PROCESS/Main] 
     14  * [wiki:PROCESS/Server] 
     15  * [wiki:PROCESS/Release] 
     16 * Discuss with team leaders of the functional teams the differences between their processes - you may decide [wiki:PROCESS/Functional] more adequate than Base Main Server. 
     17 * Explain meetings further 
     18  * Interteam meetings 
     19  * Weekly 
     20  * Progress checks 
     21  * Sprint opening 
     22  * Sprint closing [[BR]] 
     23What is done on these meetings, what should one prepare. Exact times are not important - just which meetings are regular and periods. 
     24 * Pair with the team leaders or team members for sub-team team process pages. 
    1625== Task result == 
    17 ^(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.))^ 
    18  
     26Improved [wiki:PROCESS] page. Subpages of the process page linked in it 
    1927== Implementation idea == 
    20 ^(It is advisable to include some rough implementations ideas.)^ 
    2128 
    2229== Related ==