What you may notice in a product organization:

• The same or similar mistakes are repeated project after project.
• Your manager says she is interested in post mortems, post partems, post project reviews, or retrospectives.
• No time is taken at the end of projects to learn what worked and what didn’t.
• Your manager says he is interested in improving the product development process or product quality (maybe software, hardware, or both).
• Your manager say she is interested in improving how products are brought to the marketplace.

• The same or similar mistakes are repeated project after project.
• Your manager says she is interested in post mortems, post partems, post project reviews, or retrospectives.
• No time is taken at the end of projects to learn what worked and what didn’t.
• Your manager says he is interested in improving success rate of delivering information systems on time and within budget.
• Your manager says he wants to improve the image of his organization with your business users.
• Your manager says she is interested in improving how projects are managed.

We Offer Project Retrospectives

What differentiates us is our skill in dealing with the human issues that are inevitable during close examination of individual and team behaviors and outcomes. We combine intellect, empathy, compassion, courage, enthusiasm, humor, and acceptance to create an environment safe enough to encourage maximum learning and growing.

Overview: A project retrospective is a facilitated meeting during which project community members review a project that has ended. A project retrospective may also be used when a project has been acknowledged as beyond recovery. The purpose of a project retrospective is to examine in an explicit and public way what worked, what didn't, and how to do better future projects. The focus of a project retrospective is on learning from shared experiences not on finding fault or placing blame. A project retrospective is a relatively inexpensive way to capture useful lessons from a project so they can be used to increase the success rate of future projects.

Typical results:

• a collective understanding of what happened and why
• actionable lists: what to do differently next time, lessons learned, what worked well, and topics for further discussion
• new insight added to the "project wisdom" collective
• repaired damage to a project team
• acknowledgment and appreciation of accomplishments
• documented effort data

1. We schedule and conduct a pre-meeting individual interview thirty minutes to one hour with each project community member.
2. We schedule and conduct one or more full-days facilitated meeting for project community members.
3. You produce and publish a retrospective report with our guidance.