If you want secure, reliable systems, you need all stakeholders actively communicating. This means involving both IT operations and developers in discussions after deployments, to ascertain if anything went wrong and can be avoided, and what went well or could be refined. Integrating your postmortems and retrospectives facilitates collaboration and improves processes.
How many times have you finished testing on a release and said "Boy, I never want to go through one like that again." Or have you ever had a project canceled and said "If only I would have known at the beginning, what I know now, I would have done things a lot differently." Or when you finished testing on release one, said “next time I want to do it differently,” then said the same thing on releases two, three, and four? If any of these thoughts resonate with you, then I think you will be interested in the Lessons Learned process. Lessons Learned is a powerful post-mortem process that can be used at the end of a project, phase, or deliverable to evaluate how things went, and what could be improved.
Randy Slade, Kaiser Permanente Information Technology
Testing is a tough job! Most test professionals learn the hard way what works and what doesn't. Retrospectives are focused, facilitated reviews of a defined piece of work. Learn how software project retrospectives are used as a test process improvement technique to capture the essence of a work, provide closure, and establish a springboard for active improvement in an organization.
You've just finished your software release. You have signed off, and it's been shipped. You're done, right? No! The moment a project ends is the perfect time to reflect on the entire project to see what there is to learn-the unique moment when the project can be viewed in its entirety. You can look at the completion of your project as having "paid your tuition." So, now what are you going to learn from it? In this presentation, Norm Kerth explores the benefits, pitfalls, and experiences with this project management tool. Explore ways to use retrospection to improve future projects in your organization.