This Lessons Learned Updates Software Development document shows how Eduardo Montes incrementally updated the ProjectAdm lessons learned register after each major project event — not just at closure. This example captures the mid-project updates made at each of the five milestone gates, illustrating how the Uncertainty Performance Domain's continuous learning principle works in practice on a 28-sprint SaaS development project.

What Are Lessons Learned Updates?

Lessons Learned Updates are iterative additions to the lessons learned register made throughout the project lifecycle, as described in PMBOK 8's Uncertainty Performance Domain. Rather than waiting until project closure to capture all learning, updates are recorded when events occur — after a risk materializes, following a change request, or at the end of a sprint retrospective. Each update enriches the organizational process assets repository with timely, specific knowledge that can be accessed by other running projects in the organization, not only by future projects. Regular updates also reduce the risk of knowledge loss if key team members depart before closure.

What This Lessons Learned Updates Software Development Includes

This document captures the five milestone-gated updates made to the ProjectAdm lessons learned register throughout the project:

• M1 Update (Jan 31, 2025) — Architecture Phase — Added: AWS multi-region setup took 40% longer than estimated (12 days vs. 8 days planned) due to IAM role configuration complexity; recommendation: allocate dedicated AWS setup sprint before development begins; also added: CodeIgniter 4.4.4 migration from 4.3 required 3 days of unplanned refactoring — always pin framework version in project charter
• M2 Update (Apr 30, 2025) — MVP Core — Added: Stripe sandbox testing revealed webhook signature validation bug in the PHP library (ISS-004 precursor); fixed in Sprint 7 before production but should have been caught in Sprint 1; added to Definition of Done: webhook validation test for all payment endpoints; also added: team velocity stabilized at 42 story points/sprint by Sprint 6 (higher than 40 projected from Phoenix)
• M3 Update (Jul 31, 2025) — SaaS Engine — Added: ISS-002 MariaDB query optimization required 3 sprint stories and delayed Advanced Filtering acceptance; root cause: no query performance budget defined during planning; recommendation: define p95 response time threshold for all database-heavy features before Sprint 1; also added: CR-002 Gantt chart delivered 2 weeks early by Marcus Webb using D3.js library — library evaluation should happen in Sprint 0
• M4 Update (Oct 31, 2025) — Advanced Features — Added: AI suggestion engine (ISS-001) exceeded API rate limits in Sprint 18 stress test; resolved with request queuing and exponential backoff; recommendation: treat third-party API rate limits as a first-class risk in risk register; also added: dark mode (CR-001) completed 1 sprint early because Camila Rocha had documented a CSS custom properties system in Sprint 2 — documentation investment pays off in change velocity
• M5 Update (Feb 28, 2026) — Go-Live — Added: Spanish localization (ISS-005) took 40% longer than estimated due to context-specific translation errors in UI strings; recommendation: engage native-speaker translator for UI strings, not general-purpose translation tool; also added: Lucas Park's 321-test suite ran in 8.4 minutes at M5 (threshold: 10 minutes) — acceptable but approaching limit; recommend parallel test execution for Sprint 29+ maintenance
• Cross-Milestone Insight — The three-week delay caused by ISS-002 in Sprints 14–16 was the most impactful negative event of the project; the corrective action (Bruno Silva reallocation) was effective but required 3 weeks to show results; future projects should define reassignment protocols in the Resource Management Plan before such events occur

How Eduardo Montes Used This Lessons Learned Updates Software Development

Eduardo Montes maintained the Lessons Learned Updates Software Development register in a shared Notion page accessible to all team members, updating it within 48 hours of each milestone review. Two of the M3 updates (ISS-002 query performance, CR-002 library evaluation) were immediately applicable to a parallel project at ProjectAdm International — the updates were shared with the other project's PM before their Sprint 5 planning session, potentially preventing the same database performance issue from occurring. This real-time knowledge sharing is the primary value of continuous lessons learned updates over a single end-of-project document.

How to Use This Lessons Learned Updates Software Development Document

Use this example to establish a rhythm of capturing learning at natural project pause points — milestone reviews, sprint retrospectives, and change request closures. The ProjectAdm approach of updating within 48 hours of a milestone review kept the entries fresh and specific. If you wait until project closure to capture all lessons, the most valuable insights — the mid-project pivots, the near-misses, the team dynamics — will be lost to memory.

Download the Template and Deepen Your Knowledge

Ready to create your own lessons learned updates? Download the blank Lessons Learned Updates Template (PMBOK 8).

• Download the Lessons Learned Updates Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Lessons Learned Updates in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Word (.docx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Uncertainty