| Topic | Details |
|---|---|
| Goal | Identify quality risks (product risks) early with input from various stakeholders. |
| Key Role | Test Manager gathers, facilitates, and records quality risk information from relevant stakeholders. |
| Techniques Used | - Expert interviews- Independent assessments- Retrospectives- Risk workshops- Brainstorming- Checklists- Past experience |
| Importance of Stakeholders | - Include all relevant stakeholders- Ensure agreement with project manager- Delegate if unavailable |
| Stakeholder Inclusion Method | - Kick-off meeting can help identify any missing stakeholders. |
| Risk Distribution | Risk is not evenly distributed across test items; e.g., customer UI may have different risks than admin backend. |
| By-products of Risk ID | - Issues unrelated to product quality (e.g., project risks, missing requirements, unclear specs).- These should be communicated separately. |
| Quality Ownership | Test Manager should promote the idea that quality is a shared responsibility. |
| Common Issues Identified | - Missing requirements- Planning weaknesses- Poor documentation |
Question 1
You are a Test Manager for an e-commerce platform. During a risk identification session, one stakeholder suggests that risks related to server performance be evaluated. Another mentions usability issues in the mobile app. What should your next step be?
A. Ask only the development team to submit their quality risk inputs
B. Schedule interviews with only the project manager and developers
C. Ensure participation from all relevant stakeholders, including business and support
D. Focus only on risks related to system performance
✅ Correct Answer: C
Rationale: It's critical to involve all relevant stakeholders for complete quality risk identification.
Question 2
During a retrospective, a recurring theme is poor documentation of requirements leading to missed defects. What role should you, as a Test Manager, play?
A. Inform the business analysts that documentation is not your responsibility
B. Identify this as a product risk and add it to the test plan
C. Raise it as a by-product and communicate it to project management
D. Ignore it as it's a retrospective outcome, not a quality risk
✅ Correct Answer: C
Rationale: This is a by-product of quality risk identification and should be communicated appropriately.
Question 3
Which of the following is not a recommended technique for quality risk identification?
A. Risk workshops
B. Brainstorming
C. Independent assessments
D. Automated test execution
✅ Correct Answer: D
Rationale: Automated test execution is part of test execution, not risk identification.
Question 4
What is the main disadvantage of missing a key stakeholder in the risk identification process?
A. Increased project cost
B. Incomplete identification of quality risks
C. Need for additional training sessions
D. Better focus on technical aspects
✅ Correct Answer: B
Rationale: Missing stakeholders can lead to incomplete risk identification, jeopardizing test planning.
Question 5
Which statement is true about risk distribution in software?
A. All components have equal quality risks
B. Risks are higher in open-source modules
C. Risk distribution varies; customer-facing components may have more usability risks
D. Backend services are always riskier
✅ Correct Answer: C
Rationale: Different components have different risk levels, especially UI vs. Admin functionality.
What should be done if a key stakeholder is unavailable for a risk session?
A. Exclude themB. Delay the session
C. Allow them to delegate
B. Only business risks
C. Project and documentation issues as by-products
D. Test cases
B. Identify and prioritize quality risks with multiple stakeholders
C. Review defects
D. Finalize releases
| risk identification? |
| A. Ensure all documents are signed B. Help cover common risk areas systematically C. Generate KPIs D. Conduct regression testing |
No comments:
Post a Comment