Analysis team working process

Overview

The responsibilities of the Analysis team are:

• Rescheduling tasks between iterations
• Creating tickets for the unplanned tasks
• Adding importances to the tickets in the schedule
• Analysing the tasks of the next Iteration
• Analysing bugs in collaboration with other teams
• Reviewing testing done by the Release team
• Updating and improving PLATFORM_STANDARDS_ANALYSIS

Opening

After the sprint opening the Analysis team should:

• Create the Iteration page for the next sprint
• Add importances to the tasks
• Discuss if there are tasks with bad schedule or estimate and add them for discussion on the weekly meeting.
• Create a custom Iteration page for the Analysis team

Choosing tasks

• On weekly meeting each team member declares the tasks that he/she will analyse until the next meeting.
• It is advisable to choose similar tasks - of one category for example.
• Each member should choose tasks with about 15 effort.
• When done with declared analysis, team members continue with other tasks.

Reviews

• The analysis team reviews the testing phase of the tasks.

Closing

• At the end of the iteration each task of the next iteration should be analysed and passed analysis review.

Comments