| 1 | | Analysis |
| 2 | | * Regularly update the tracked items |
| 3 | | * Keep the backlog structure consistent and easy to use |
| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | = Analysis = |
| | 4 | == Overview == |
| | 5 | The goal of this task is to analyse and repair current internal backlog if needed. This maintenance is performed regularly. |
| | 6 | == Task requirements == |
| | 7 | * Impediments - Review existing impediments, discuss with team which are overcame and which not. Mark these, which are already fixed. |
| | 8 | * Smells - Review existing smells, ask who is assigned to fix them and view current status. If the smell is corrected, mark it in the Smells sheet. |
| | 9 | * Documents - Search for newly created important documents and include them here. |
| | 10 | * Daily and Global availability - Review if each member has filled in availabilites for a fixed period (a month for example). |
| | 11 | == Task result == |
| | 12 | Maintained http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en |
| | 13 | == Implementation idea == |
| | 14 | - |
| | 15 | == Related == |
| | 16 | [wiki:INTERNAL_BACKLOG_STRUCTURE_R0] |
| | 17 | == How to demo == |
| | 18 | Show the internal backlog at http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en and describe maintained parts. |
| | 19 | = Design = |
| | 20 | = Implementation = |
| | 21 | = Testing = |
| | 22 | = Log = |
| | 23 | [include:INTERNAL_BACKLOG_MAINTENANCE_R0_LOG] |
