4.5.31: Scenario 30 – Post-Delivery Review and Lessons Learned
- Page ID
- 54836
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)Scenario 30 – Post-Delivery Review and Lessons Learned
Scenario Context
Project Reckon has now been formally delivered and released.
The system is:
-
Functionally complete
-
Stable under expected usage
-
Integrated into the iPET platform
-
In active use by stakeholders
However, the project experienced:
-
Scope drift and baseline misalignment
-
Budget overrun beyond original tolerance
-
Schedule adjustments
-
Architectural refactoring and regression
-
Stakeholder confidence fluctuations
-
Process tightening and rebalancing
The project has succeeded.
But not without cost.
C-Bay leadership has now requested a post-delivery review.
Email from Julie Rama
Subject: Project Reckon – Post-Delivery Summary
Hi,
I wanted to take a moment to thank you for your collaboration throughout Project Reckon.
We have successfully delivered the system and completed rollout activities.
1. Final Project Status
-
System stability: High
-
Defects: Minimal and manageable
-
User adoption: Positive
-
Integration: Stable
2. Final Metrics
-
Budget: +11.2% over original baseline
-
Schedule: Delivered within revised timeline
-
Scope: Expanded beyond original URD
3. Observations
From our perspective:
-
The project ultimately achieved its objectives
-
Early instability was resolved through structured intervention
-
Process discipline improved significantly over time
4. Next Phase
We will transition into:
-
Support and maintenance
-
Incremental enhancements
-
Continuous improvement
5. Request
C-Bay leadership has requested a formal summary of:
-
What went well
-
What could have been improved
-
Key lessons for future projects
We would appreciate your perspective.
Best,
Julie
Internal Email from C-Bay Leadership
Subject: Project Reckon – Lessons Learned
Hi,
Now that Project Reckon has been delivered, I would like a clear assessment of:
-
Where we lost control and why
-
What decisions had the greatest impact
-
What we would do differently next time
-
How we can improve future outsourced initiatives
This is important for our long-term strategy.
Please provide a structured review.
Thanks,
[Executive Name]
Attachment A – Final Summary
| Category | Outcome |
|---|---|
| Scope | Expanded |
| Budget | +11.2% |
| Schedule | Adjusted |
| Stability | High |
| User Feedback | Positive |
Student Assignment
You are the Project Manager at C-Bay.
Project Reckon has been successfully delivered.
However, leadership now requires a clear and honest evaluation of the project.
You must:
-
Reflect on decisions made throughout the project
-
Identify where control was lost and regained
-
Evaluate trade-offs
-
Extract lessons for future projects
Prepare a formal post-delivery review.
Required Submission Structure
Your memorandum must include:
1️⃣ Executive Summary
-
Was the project successful?
-
What were the key outcomes?
-
Was success achieved efficiently?
2️⃣ What Went Well
-
What decisions contributed positively?
-
What processes worked effectively?
-
What enabled recovery and success?
3️⃣ What Could Have Been Improved
-
Where was control lost?
-
What decisions led to instability?
-
What early signals were missed?
4️⃣ Critical Decision Analysis
Identify 2–3 key decisions and evaluate:
-
What was the context?
-
What was the decision?
-
What were the consequences?
5️⃣ Lessons Learned
-
What principles should guide future projects?
-
What should be done differently next time?
-
What controls should be implemented earlier?
6️⃣ Recommendations for Future Projects
Provide specific recommendations on:
-
Scope management
-
Vendor governance
-
Change control
-
Risk management
-
Communication
7️⃣ Final Reflection
-
What did you learn as a Project Manager?
-
How has your approach to managing outsourced projects evolved?
Learning Focus
Scenario 30 introduces:
-
Reflective leadership
-
Accountability for outcomes
-
Learning from complexity
-
Translating experience into future practice
-
Strategic thinking beyond delivery
Students must demonstrate:
-
Honesty
-
Insight
-
Structured reflection
-
Ability to connect actions to outcomes
Key Insight
Success is not just:
-
Delivering the project
It is:
-
Understanding how it was delivered
This scenario reinforces:
The value of a project is not only in its outcome —
but in what it teaches the organization.
Final Practicum Insight
Across all 30 scenarios, students should now understand:
-
Projects drift gradually, not suddenly
-
Control must be maintained continuously
-
Every decision has second-order effects
-
Trade-offs are unavoidable
-
Leadership requires judgment, not just process