| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | = Analysis = |
| | 4 | |
| | 5 | |
| | 6 | == Overview == |
| | 7 | Make read documents. Make structure for some of the things. Think about open questions table. |
| | 8 | == Task requirements == |
| | 9 | The Internal backlog is located here: http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en |
| | 10 | * Impediments sheet: |
| | 11 | If there are solutions for unresolved tasks, mark them as resolved and insert hyperlinks to corresponding tasks (or task results) from the wiki. |
| | 12 | * Smells sheet: |
| | 13 | Review smells. Assign team members to fix open smells. (you can use dev mail list, or ticket system) |
| | 14 | * Documents sheet: |
| | 15 | Create a column for each team member. This column should contain last read date for this member. |
| | 16 | * Daily Availability sheet: |
| | 17 | Each member should have two columns. The first should contain amount of working hours for this date, the second should contain free text. Remind the members to fill in regularly their availability. (you can use mail list) |
| | 18 | * Open Questions sheet: |
| | 19 | |
| | 20 | == Task result == |
| | 21 | ^(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.))^ |
| | 22 | |
| | 23 | == Implementation idea == |
| | 24 | ^(It is advisable to include some rough implementations ideas.)^ |
| | 25 | |
| | 26 | == Related == |
| | 27 | http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en |
| | 28 | |
| | 29 | == How to demo == |
| | 30 | ^(In this section you must add instructions for the demo of the task.)^ |
| | 31 | |
| | 32 | = Design = |
| | 33 | |
| | 34 | = Implementation = |
| | 35 | ^(Implementation results should be described and linked here (from the wiki or the repository)^ |
| | 36 | |
| | 37 | = Testing = |
| | 38 | |
| | 39 | = Comments = |
| | 40 | |
| | 41 | = Log = |
| | 42 | ^(Link the log of the task here)^ |
