| Aspect | Details |
|---|---|
| Definition | Team meeting to reflect, identify lessons, and plan improvements. |
| Usage | Both in Agile (each iteration) and sequential models (project end). |
| Focus Areas | Process, people, organization, collaboration, tools. |
| Steps in Retrospective | 1. Introduction 2. Collect Data 3. Derive Improvements 4. Decide Actions 5. Close |
| Data Types | - Qualitative: Feedback, feelings, events- Quantitative: Metrics |
| Tester’s Role | Raise testing-related issues and share insights. |
| Outcome Documentation | Agile: Action trackingSequential: Formal report shared in org. |
Key Points to Remember
-
Retrospectives support continuous improvement.
-
They should be regular, especially in Agile.
-
Avoid doing too many improvements at once.
-
Document everything (actions, outcomes) clearly.
-
Testers contribute a unique perspective and should raise test-related issues.
Real-Time Example
Scenario:
Your Agile team just finished Sprint 4. During the retrospective:
-
The team noticed test cases were not completed on time.
-
Defects were not logged consistently.
-
The tester suggested that the root cause was unclear requirements and late test environment access.
Actions Taken:
-
Agreed to involve testers earlier during requirement discussions.
-
Decided to set up test environments at the start of the sprint.
-
Assigned the Scrum Master to track test environment readiness.
Q1. During a retrospective, the team discovers that the same type of defect appeared in three past sprints. What should be done?
A. Add more test cases without changing the process
B. Assign blame to the developer
C. Apply root cause analysis to understand and fix the issue
D. Skip the issue as it has already been resolved in production
✅ Correct Answer: C
Why? Root cause analysis helps to fix the actual cause, not just the symptom.
Q2. What is a key reason retrospectives are helpful in Agile development?
A. To punish team members for failures
B. To delay delivery timelines
C. To continuously improve the team’s way of working
D. To replace testing with reviews
✅ Correct Answer: C
Why? Retrospectives encourage learning and continuous improvement.
Q3. Which data types are used in retrospectives?
A. Only metrics like defect count
B. Only feelings and opinions
C. Both quantitative and qualitative data
D. Only business goals
✅ Correct Answer: C
Why? Retrospectives use both metric data and team member experiences.
Q4. What is the role of the tester in a retrospective?
A. Only listen to developers
B. Focus only on non-functional testing
C. Share test-related issues and contribute ideas for improvement
D. Review code coverage
✅ Correct Answer: C
Why? Testers bring in a unique perspective and should actively participate.
1. During a sprint retrospective, the team identifies that testing feedback was delayed. What is the best improvement step?
A. Increase test automation coverage
B. Add more testers to the team
C. Move testing to a later stage
D. Conduct a root cause analysis of the delay
✅ Correct Answer: D
2. In a sequential development project, a retrospective is held at the end of testing. Which of the following would be an appropriate action?
A. Record unresolved defects in a backlog
B. Note lessons learned and circulate them across the organization
C. Plan for the next iteration’s improvement
D. Replace qualitative feedback with metrics only
✅ Correct Answer: B
3. What data should be prioritized in retrospectives for objective process improvements?
A. User satisfaction surveys
B. Manager opinions
C. Quantitative test effectiveness metrics
D. Team feelings
✅ Correct Answer: C
4. Which of the following is a key tester contribution in a retrospective?
A. Assigning coding tasks
B. Raising test tool licensing issues
C. Highlighting quality risks and inefficiencies
D. Avoiding root cause discussions
✅ Correct Answer: C
5. Which retrospective step ensures that improvement actions are properly implemented?
A. Collect Data
B. Derive Improvements
C. Decide on Improvement Actions
D. Close Retrospective
✅ Correct Answer: C
🧪 Exam-Style Test Simulation (10 Questions)
1. What is the main goal of retrospectives in Agile?
A. Ensure test coverage is complete
B. Measure code quality
C. Reflect and improve processes
D. Write automated scripts
✅ Answer: C
2. What step comes directly after collecting data in a retrospective?
A. Document results
B. Assign action items
C. Derive improvements
D. Conduct root cause analysis
✅ Answer: C
3. Which of the following is a quantitative metric used in retrospectives?
A. Team morale score
B. Number of defects found per test case
C. Developer opinion on code quality
D. Story satisfaction rating
✅ Answer: B
4. What supports continuous improvement in retrospectives?
A. Conducting them once per year
B. Ignoring testing issues
C. Regularly reviewing actions and outcomes
D. Skipping root cause analysis
✅ Answer: C
5. Retrospective documentation in Agile should include:
A. All completed test cases
B. Executive reports only
C. Actions and related metrics
D. User stories
✅ Answer: C
6. In the introduction phase of a retrospective, the facilitator must:
A. Present defect reports
B. Establish a blame-free environment
C. Assign test cases
D. Review stakeholder KPIs
✅ Answer: B
7. What is an example of a qualitative input in a retrospective?
A. Velocity chart
B. Number of executed test cases
C. Team member’s feelings on collaboration
D. Defect aging report
✅ Answer: C
8. What approach helps identify why the same defect type recurs?
A. Test design technique
B. Exploratory testing
C. Root cause analysis
D. Regression analysis
✅ Answer: C
9. What best describes a tester’s contribution in retrospectives?
A. Create scripts
B. Escalate management issues
C. Suggest improvements in test process
D. Take over defect triage
✅ Answer: C
10. In sequential development, retrospective findings should be:
A. Destroyed after project ends
B. Shared only with testers
C. Communicated across the organization
D. Ignored to save time
✅ Answer: C
No comments:
Post a Comment