Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Transformation management and PMO

When to hold a project lessons-learned review, and when to forgo it

In brief

A project lessons-learned review is the examination, by those who took part in it, of what a project or a phase teaches for the future: end-of-project review, retrospective in an agile approach, post-incident review. Management Square offers a decision guide here: when to hold it, what to focus it on, whom to bring together, which conclusions to keep and to whom to entrust the follow-up, and when to forgo it.

Page contents

Held at closure, a project lessons-learned review comes at the moment the team disperses. Those who have learned something move on to other work, the next project may start with other people, and the report risks ending up in a file nobody has any reason to reopen. The exercise can therefore be well run and change nothing.

We suggest holding it when three conditions are met: it takes place at a time when its conclusions can still be of use, it focuses on a bounded subject, and a designated person has the power to act on them. This guide takes them in order (timing, subject and participants, follow-up), then describes the cases where it is better to forgo it than to rush it.

When a project lessons-learned review is still useful

The term, abbreviated in French as REX, covers several practices, which differ first of all in their timing.

In the Scrum framework, the exercise is built into the team’s rhythm. The Scrum Guide (scrumguides.org, November 2020 version, read on 12 November 2026) calls the event that concludes each Sprint the Sprint Retrospective. Its purpose is “to plan ways to increase quality and effectiveness”. The Scrum Team inspects how the last Sprint went “with regards to individuals, interactions, processes, tools, and their Definition of Done”, then identifies the most helpful changes. The Guide adds that the most impactful improvements “are addressed as soon as possible” and may be added to the Sprint Backlog for the next Sprint. Its duration is capped: three hours at most for a one-month Sprint.

Two other forms belong to common usage, and we present them as such. The end-of-project review, or end-of-phase review, brings the team together once the work has been delivered. The post-incident review takes place in the days following an outage or a failed cutover, without looking for someone to blame; our page SRE and observability describes it for operations.

These forms differ in the distance between the exercise and the next opportunity to apply what it teaches. The retrospective finds this opportunity in the next Sprint, with the same team. The closure review only finds it in the next project, if it resembles the first. The decision criterion follows from this: place the exercise where follow-up remains possible. On a long project, this means holding it at the end of a phase, after a cutover or after a missed milestone, without waiting for closure. The facts are recent, and the next phase can benefit from them.

A bounded subject, and the people to bring together

A lessons-learned review that tries to cover everything risks producing a list of regrets. We suggest bounding the subject to a few questions chosen before the session. For example: why the estimate for data migration turned out to be too short; what enabled the cutover to go as planned; at what point the dependency on the neighbouring system could have been seen.

The useful material is the gap between what the plan assumed and what happened, with the information available to those who decided, at the moment they decided. What worked is examined on the same footing as what went wrong.

The session brings together those who did the work and those who decided: project team, user representatives, operations, the supplier where the relationship allows. The candour of what is said depends on the facilitation and on the rule announced. Facilitation falls to a person outside the project’s line of management, for example a member of the project office, or PMO, or a project manager from another team. The rule is stated when opening the session: it concerns situations and decisions, and leaves aside the assessment of people.

Neighbouring exercises have a different purpose. The project review decides the next steps of a project in progress, before those with authority over it. The project audit establishes the facts: a third party independent of the project checks them against the evidence, cross-checks them and draws options from them for a sponsor. The lessons-learned review, for its part, gathers what participants take away, without verifying what they say. On a project in difficulty whose real state is disputed, asking it to do the work of an audit exposes the team to a session it may take for a trial.

Few conclusions, each with a recipient

The session minutes are only a record. The exercise produces a short list of conclusions, which common usage also calls “lessons learned” and which we suggest sorting into three kinds:

  • a common rule to change (an estimation model, the criteria for a milestone, a standard clause, a pre-cutover checklist), addressed to the person who owns that rule;
  • a specific project to alert, the one about to encounter the same situation: the conclusion goes to its project manager, in person, at the framing stage;
  • a finding with no follow-up, recorded as such so as not to suggest that an action will follow.

Each conclusion of the first two kinds carries a name, an action and a date. The name is that of a person with the power to change something. The team that is breaking up cannot play this role.

What remains is to check that the follow-up has happened. In an organisation with a project office, this responsibility may fall to it: it keeps the list of open conclusions, presents them at the framing of comparable projects and checks that the common rules have been changed. Our page on setting up a PMO describes the mandate that makes this role possible. Failing that, the sponsor designates this person before the session.

The proof that a lessons-learned review has been useful is found in the next project: an estimate made differently, a milestone whose criteria have changed, a check added before a cutover.

The cases where it is better to forgo it

A rushed lessons-learned review has a cost: it can wear down the trust of those who were asked to speak, to the detriment of the next session. Several situations justify abstaining, or waiting.

The first is the absence of a recipient. If nobody can change a rule or alert another project, the session will produce only a document.

An ongoing dispute is another. When a dispute sets the organisation against a supplier, or an internal inquiry into responsibility is under way, everyone weighs their words. The exercise waits for the outcome of the dispute; in the meantime, the facts are established by other means, with your lawyers if the contract is at issue.

The same applies when the sponsor expects a name. A session commissioned to designate a culprit changes in nature: everyone may prepare their defence there.

The moment may also have passed: the team dispersed long ago, and memories may have rearranged themselves around the final result. A few targeted interviews, on a specific question, are then better than a plenary session.

Finally, the conclusions of the previous lessons-learned review may still be pending. Holding a new session before having dealt with or closed them only lengthens the list.

Forgoing it is stated: the decision is recorded at closure, with its reason. And before putting a session in the diary, one check comes before all others, that of the recipient: their name, and what they have the power to change. As long as that name is missing, the session can wait.

Insights

Further reading

All insights
Product owner or product manager, two functions to distinguish before appointing anyone

In the Scrum Guide, the product owner is the person accountable for the value of a product and for its Product Backlog; product manager is a job title, absent from that guide, which in practice refers to the person in charge of a product's trajectory. Management Square compares product owner and product manager here (horizon, scope, counterparts, decisions) and describes the possible set-ups.

Read the analysis
Before an acquisition, the questions an IT due diligence asks of the target's information system

An IT due diligence, or acquisition audit of the information system, examines before an acquisition or an equity investment the state of the applications, dependencies, security, contracts and the system's capacity to be integrated or separated. Management Square presents here an investment committee's questions on these subjects, the evidence to request and what each answer changes in the transaction.

Read the analysis
Why do IT projects fail? A reading through the signs of drift

An IT project fails, under the convention adopted here, when it misses its deadline, its cost, its scope or the expected benefit beyond the variance its sponsor had accepted. Rather than a list of causes, Management Square offers a reading method here: the observable signs of drift at each stage of the project, what each one can reveal and the response it calls for.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between a project lessons-learned review and a retrospective?

The retrospective is one form of lessons-learned review, which the Scrum framework places at the end of each Sprint. The November 2020 Scrum Guide describes the Sprint Retrospective as the event that concludes each Sprint: the Scrum Team inspects how the past Sprint went and identifies the most helpful changes to improve its effectiveness. In common usage, a project lessons-learned review rather refers to a review held at the end of a phase or project, whose conclusions are also addressed to other teams.

Who should facilitate a project lessons-learned review?

We suggest entrusting facilitation to a person outside the project's line of management, for example a member of the project office or a project manager from another team. The manager of the project under review takes part, but finds it difficult to facilitate an exercise that partly concerns their own decisions. The facilitator sets the rule from the outset: the session describes situations and decisions, it does not assess people.

Is a lessons-learned review needed when the project went well?

Yes, if the organisation wants to know what it can reproduce. A project may meet its commitments thanks to a practice worth repeating, or thanks to circumstances that will not recur: an already experienced team, a stable scope, an available supplier. The lessons-learned review then serves to tell the two apart and to pass the practice on to the next project.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.