Agile Retrospective Make it Pro-active and not Reactive For Better Efficiency and Results.

Agile Retrospective Make it Pro-active and not Reactive For Better Efficiency and Results.

Agile retrospective team gets together end of every sprint/iteration to check what went right and what did not go right and what improvements needs to be done. In this phase please be aware that teams often take actions for things that did not go right. These actions have to be taken so that it does not just solve the problem with the actions but in future in all the upcoming iterations and releases these similar issues should never occur again. So a framework or mechanism has to be made in place so that this issue never occurs again and it will proactively solve this issue for all releases.  Let me give an example:-

Example:

Retrospective Issue: Defects did not have adequate impacting testing leading to more induced defects and defect testing field in the BugZilla tool did not have this field filled.

 Corrective Action: Ensure team fills the impacting testing column to the BugZilla tool (so that adequate impacting testing is done for the defect and constant audit is done).

Preventive Action: Ensure that the impacting testing column in the Bugzilla is a mandatory field to fill (so that team will do impacting testing for the defects) and start automating all the impacting test cases (if not automated).

[Please comment below and Post this article  in your Facebook, Twitter, Linked-In, Whats-app, Google Accounts, Forward to your Company allowed mailing list if applicable also   if you find this useful]