Analysis

An analysis should provide all needed information and clear description what has to be done.
You have to:

• list the requirements for creating analysis for tasks. An analysis should contain:
  • brief overview of the task
  • what has to be done
  • example how to be done
  • overview of the whole task but strict analysis of the current revision
  • other requirements...
• analysis should be done at least one sprint before
• the analysis have to be made by one developer and one QA
• notice what the results of an analysis are
• make analysis template and give at least two examples of good analysis
• point where to keep the analysis (wiki page with the task and the current revision for example)

Design

Analysis can be kept in the task page in each iteration in section Analysis. We should think about global section platform standards (and other?) docs which has links to the sections of the task phases. Create a document here which has the following content:

1. strict analysis requirements
2. where to make the analysis (in task page for current revision, section Analysis)
3. where to keep the new created analysis
4. who has to make the analysis (QA and Developer)
5. analysis templates
6. good and useful examples (team discussion which of the analyzes are the best)

How to write analysis