| | 10 | = Analysis = |
| | 11 | ^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^ |
| | 12 | |
| | 13 | == Overview == |
| | 14 | ^(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.)^ |
| | 15 | |
| | 16 | == Task requirements == |
| | 17 | ^(Necessary requirements that the task must fulfill.)^ |
| | 18 | |
| | 19 | == Task Result == |
| | 20 | ^(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.))^ |
| | 21 | |
| | 22 | == Implementation idea == |
| | 23 | ^(It is advisable to include some rough implementations ideas.)^ |
| | 24 | |
| | 25 | == Related == |
| | 26 | ^(Here you can add related tasks that could be useful or helpful.)^ |
| | 27 | |
| | 28 | == How to demo == |
| | 29 | ^(In this section you must add instructions for the demo of the task.)^ |
| | 30 | |
| | 31 | = Design = |
| | 32 | |
| | 33 | = Implementation = |
| | 34 | |
| | 35 | = Testing = |
| | 36 | |
| | 37 | = Log = |
| | 38 | ^(Link the log of the task here)^ |
