Flashcards
3.2 Assessing Quality Risks and Estimating Test Effort
Cards in this deck (12)
- 13.2.1 Assessing Quality Risks in Agile ProjectsTerm: Quality Risks
Definition: Risks related to the possibility of negative or undesirable outcomes affecting product quality or project success. - 2Challenges in Testing: Proper selection, allocation, and prioritization of test conditions, including determining effort allocation and test sequencing.Risk Assessment: Determined by assessing likelihood and impact of potential problems on product quality or project success.
- 3Quality Risk Analysis in Agile ProjectsRelease Planning: Overview of risks provided by business representatives, with team assistance.
Iteration Planning: Team identifies and assesses quality risks for current iteration. - 4Examples of Quality Risks:🛑Incorrect calculations in reports (functional risk)
🛑Slow response to user input (non-functional risk)
🛑Difficulty in understanding screens and fields (usability risk) - 5Quality Risk Analysis Process during Iteration Planning:1. Gather Agile team members, including testers.
2. List backlog items for current iteration.
Identify quality risks for each item.
3. Assess risks by categorizing and determining level based on impact and likelihood.
4. Determine testing extent proportional to risk level.
5. Select test techniques to mitigate each risk based on quality characteristics. - 6Mitigation and Adjustment:✅Design, implement, and execute tests to mitigate risks.
✅Periodically adjust risk analysis based on new information, re-assess existing risks, and evaluate mitigation effectiveness. - 7Pre-Execution Mitigation:Review user stories thoroughly if problems arise during risk identification as a mitigation strategy.
- 83.2.2 Estimating Testing Effort Based on Content and RiskTerm: Planning Poker
Definition: Consensus-based estimation technique where each team member selects a value from a set of cards representing effort units.
- 9Process:1. Product owner reads user story.
2. Estimators discuss feature, asking questions as needed.
3. Aspects like development and testing effort, complexity, and scope are considered.
4. Estimators privately select cards representing their estimates.
5. Cards are revealed simultaneously.
6. If agreement reached, estimate is set; if not, discussions continue or rules are applied (e.g., median). - 10Why Fibonacci Sequence?Reflects uncertainty growth with story size, facilitating better estimation.
- 11Role of Risk Level:Advisable to include risk level before initiation to factor it into estimation discussions.
- 12ObjectiveEnsure reliable estimation of effort needed for product backlog items and enhance collective knowledge.
Information
- Description
- 3.2.1 Assessing Quality Risks in Agile Projects 3.2.2 Estimating Testing Effort Based on Content and Risk
- Created by
- Esther H
- Views
- 27
- Rating