1. 8D. Step 4. Root Cause Analysis. Part 1: FishBone
    1. Detailed Problem Description
      1. Thanks to a detailed description of the problem through 5W + 2H, we get a more detailed representation of it in comparison with the original (http://www.xmind.net/m/fcnd).
      2. Regression testing (main scenarios) is carried out in the end of 14 iteration (before the release), a large number of regression bugs with high priority and severity lead to delay in product release, because the basic customers scenarios do not work correctly.
  2. For Root Cause Analysis we use the Ishikawa diagram (Fish Bone) and "5 Why " method. Lead a brainstorming session and identify all the possible causes of the problem. Answer by question: Why did it happen? For all possible causes you can use most deeper analyse. The maine aim: to find root course and further solution. Note: do not find a guilty person and we try to find problems in process. After all possible reasons were considered, you need to prioritize hight likely causes for next analyse ("5 Why " method)
  3. We decided: Testers do not have feedback from developers
  4. MAN
    1. There is not enough knowledge in the business area
    2. There is not enough qualification in testing / analysis / development
    3. Many distractions
    4. Low motivation
    5. Blurred vision
    6. Non-constructive perception of criticism
    7. Inattention to the details of functional implementation specified in the US
  5. Management
    1. We misjudged the time for the US implementation
    2. US priority was estimated wrong
    3. Risks were estimated wrong
  6. Method
    1. There are no acceptance test cases for US
    2. No atomic tasks for programmers for US
    3. The procedure for working with requirements is not clear
    4. Acceptance test cases were not passed
    5. Different understanding of US contents
    6. Features depend on services implemented by other teams in other projects
    7. There is no formalized US transfer procedure: from developer to tester
    8. Insufficient preparation for iteration planning
    9. US are changed during sprint
    10. Lack of prototyping the interface
    11. Testers do not have feedback from developers
  7. Environment
    1. Some external programs block our software
    2. The required versions of the required software are not installed
    3. Iterations with related groups are not synchronized
    4. Ploblems with servers
  8. Mashine
    1. Required software were not available
    2. Errors with a project build in CI
  9. Materials
    1. The US description is not atomic
    2. Conflict new and existing features (Product was started with another Team)
    3. Iteration changes caused significant changes in the bases scenarios
    4. The functionality implemented in the early iterations does not correspond to the stakeholder requremetns
    5. Changes in implementation not approved in the JS and TK after the sending of the functional to the development
    6. Problems with Autotests