ISTQB_Managing the Product_2.3 Defect Management_TM-2.3.3 (K2) Explain the specifics of defect management in Agile software development

 

Key Concepts – Defect Management in Agile

Agile defect management differs from traditional approaches in its flexibility, collaboration, and lower formality. Key principles include:

• Lightweight & informal process

• Rapid communication (verbal/chat) over documentation

• Defect reporting only when needed

• Backlog usage for unresolved defects

• Team maturity and collaboration affect process

• Adaptability depending on co-location, risk, regulations

📌 When to Create Formal Defect Reports in Agile:

1. Blocks current sprint activities and can’t be fixed immediately.

2. Can’t be resolved within the same iteration/day.

3. Needs resolution with or by other teams/suppliers.

4. Developer explicitly requests a defect report.

5. Regulatory or contractual reasons.

---

📋 Summary Table with Example

Situation	Defect Report Needed?	Why?
Minor UI issue fixed immediately	❌ No	Fixed quickly within team, no formal tracking needed
Defect blocks current development task and takes time to fix	✅ Yes	Blocks sprint activity and not resolved immediately
Defect involves external API integration with another vendor	✅ Yes	External dependency – needs traceability
Co-located team finds and fixes a bug same day	❌ No	Agile encourages informal fixes when quick and clear
Team member requests defect report for tracking	✅ Yes	Explicit request mandates report creation
Security vulnerability found, high risk, needs sign-off	✅ Yes	Regulatory/risk-based requirement

---

🧠 Mind Map for Quick Revision

               +------------------------------+
               |  Agile Defect Management     |
               +------------------------------+
                          |
     +--------------------+---------------------+
     |                                          |
Informal Communication               Formal Defect Reports Needed When:
(chat, verbal, tools)                 - Blocker in sprint
                                      - Cannot fix in iteration
                                      - Involves other teams/suppliers
                                      - Requested by team member
                                      - Regulatory/compliance needed
     |
     +--------------------+---------------------+
     |                                          |
Lightweight Tracking            Add to Product Backlog if unresolved
Team Determines Level           Strategy set in test policy, team customizes
of Formality (based on context)

Short Scenarios
A developer finds a minor styling bug during a sprint and fixes it within an hour. Should a defect report be created?
a) Yes

b) No

✅ Answer: b) No
A defect is found that needs coordination with a supplier to fix. What should be done?
a) Fix it within the team

b) Ignore it until the supplier fixes it

c) Create a defect report

✅ Answer: c) Create a defect report
An Agile team is working on a mobile app. A tester finds a crash issue during testing. The developer is currently on leave and the defect blocks a major feature.
a) Wait until the developer returns

b) Raise a formal defect report

c) Ignore until next iteration

✅ Answer: b) Raise a formal defect report

A team finds a medium-priority bug in a sprint, but it’s Friday evening and the sprint ends Monday. Fixing will take two more days.
a) Postpone it to next sprint

b) Create a defect report and add to backlog

✅ Answer: b) Create a defect report and add to backlog
Question 1:
In Agile, what typically triggers the need to formally log a defect?
a) All bugs must be reported

b) The customer requests a report

c) Defect cannot be fixed immediately or involves other teams

✅ Answer: c)
Question 2:
Which situation is least likely to require a formal defect report in Agile?
a) Defect resolved within a few hours by the developer

b) Cross-team integration failure

c) Regulatory issue found during UAT

✅ Answer: a)
Question 3:
Why might Agile teams avoid formal defect reports for minor issues?
a) They don’t test thoroughly

b) Documentation is not allowed

c) To speed up collaboration and avoid overhead

✅ Answer: c)
Question 4:
An Agile team working across time zones should consider more formal defect reporting because:
a) Co-location enables more chat

b) Time zones make informal communication difficult

c) All issues are fixed instantly

✅ Answer: b)
Question 5:
Where are unresolved defects typically stored in Agile?
a) Stored in emails

b) Left in the tester's notebook

c) Added to the product backlog

✅ Answer: c)
Question 6:
Team A finds a defect that Team B must fix. What’s the best step?
a) Fix it internally

b) Log a defect report and notify Team B

✅ Answer: b)
Question 7:
Defect tracking policy in Agile is generally set by:
a) The product owner

b) The test automation engineer

c) The organizational test strategy, then refined by team agreement

✅ Answer: c)
Question 8:
Which factor does NOT influence Agile defect management formality?
a) Team co-location

b) Coffee machine quality

c) Risk associated with the product

✅ Answer: b)

Question 9:
In an Agile team, when is a defect most likely added to the backlog?
a) When fixed immediately

b) When not fixed in the same iteration

✅ Answer: b)
Question 10:
Agile teams should always document their defect management process because:
a) Testers need work

b) Developers forget

c) It ensures clarity, traceability, and consistency

✅ Answer: c)