Page History

...

1. Risk Identification & Risk Assessment
   1. BAs together with the team discuss risks on the ”Requirement Analysis” phase 
2. Risk Treatment
   1. performed by testers, during the “Testing” phase
      1. Test Planning takes the inputs of Risk Assessment to define the testing strategy and effort; the testing scope is agreed
      2. if adopting the scripted testing approach, testers start by detailing exaustively test cases for the most risky item, during Test Design
      3. testers will perform more in-depth testing on the risky items during Test Execution
      4. if important bugs are found on the risky items, the software can go back to "Implementation" phase as-soon-as-possible
3. Risk Monitoring and Reviewing
   1. throughout the project lifecycledevelopment life cycle; special focus is given at testing closure, t

Please note that even though you may be doing Risk Identification and Assessment on the first phase (i.e. "Requirement Analysis"), risk factors are present in all development phases as each one is prone to risks.

...

1. Risk Identification and Assessment
   1. Release planning
      1. Highest-risk tasks must be placed in the earliest sprints
   2. Backlog refinement/grooming
      1. the team can identify and discuss risks together on each PBI (product backlog item)
   3. Sprint planning (by the whole agile team)
      1. Testers can start creating a risk-based analysis by using the stories given for that iteration, identifying the high-risk stories that can be tested on that iteration, and prioritizing the user stories depending on their criticalness to the business
      2. Risk’s impact and likelihood can be evaluated using “Risk Poker” (like planning poker)
2. Risk Treatment
   1. During sprint lifetime, by performing more extensive testing on high-risk stories (including for regression testing purposes)
3. Risk Monitoring and Reviewing
   1. During sprint lifetime

...