2.1.6 Retrospectives and Process Improvement Flashcards
Retrospectives are often held at the:
- end of a p…
- at a re…
- or can be held …
- project or an iteration,
- release milestone
- when needed.
The timing and organization of the retrospectives depend on the particular …
SDLC model being followed.
In these meetings the participants (not only testers, but also e.g. developers, architects, product owner, business analysts) discuss:
- What was “ “ and should …
successful
be retained?
In these meetings the participants (not only testers, but also e.g. developers, architects, product owner, business analysts) discuss:
- What was not “ “ and could …
successful
be improved?
In these meetings the participants (not only testers, but also e.g. developers, architects, product owner, business analysts) discuss:
- How to incorporate the “ “ and retain the …
improvements
successes in the future?
The results should be recorded and are normally part of …
the test completion report.
Retrospectives are critical for the successful implementation of “ “ and it is important that any recommended …
continuous improvement,
improvements are followed up.
Typical testing benefits include:
- Increased test “ “ (e.g by implementing suggestions …
efficiencies / efficiency
for process improvement).
Typical testing benefits include:
- Increased testware “ “ (e.g. by jointly reviewing …
quality
the test processes).
Typical testing benefits include:
- Team “ “ and “ “ (e.g. as a result of the opportunity to … and propose …
bonding
learning
raise issues
improvement points).
Typical testing benefits include:
- Improved test ba… (e.g. as deficiencies in the extent and quality … could be …
basis quality
of the requirements
addressed and solved).
Typical testing benefits include:
- Better cooperation between … (e.g. as collaboration is …
development and testing
reviewed and optimized regularly).
