| | 1 | = Analysis team working process = |
| | 2 | == Overview == |
| | 3 | The responsibilities of the Analysis team are: |
| | 4 | * Rescheduling tasks between iterations |
| | 5 | * Creating tickets for the unplanned tasks |
| | 6 | * Adding importances to the tickets in the schedule |
| | 7 | * Analysing the tasks of the next Iteration |
| | 8 | * Analysing bugs in collaboration with other teams |
| | 9 | * Reviewing testing done by the Release team |
| | 10 | * Updating and improving [wiki:PLATFORM_STANDARDS_ANALYSIS] |
| | 11 | == Opening == |
| | 12 | After the sprint opening the Analysis team should: |
| | 13 | * Create the Iteration page for the next sprint |
| | 14 | * Add importances to the tasks |
| | 15 | * Discuss if there are tasks with bad schedule or estimate and add them for discussion on the weekly meeting. |
| | 16 | * Create a custom Iteration page for the Analysis team |
| | 17 | == Choosing tasks == |
| | 18 | * On weekly meeting each team member declares the tasks that he/she will analyse until the next meeting. |
| | 19 | * It is advisable to choose similar tasks - of one category for example. |
| | 20 | * Each member should choose tasks with about 15 effort. |
| | 21 | * When done with declared analysis, team members continue with other tasks. |
| | 22 | == Reviews == |
| | 23 | * The analysis team reviews the testing phase of the tasks. |
| | 24 | == Closing == |
| | 25 | * At the end of the iteration each task of the next iteration should be analysed and passed analysis review. |
| | 26 | == Comments == |
