Page one for this query is retrospective templates built around a facilitated meeting: sticky notes on a timeline, a blameless discussion, a list of what went well. The most rigorous of them, a project post-mortem template, argues specific data beats a vague retrospective, citing "we estimated 16 weeks and delivered in 18" as the standard a finding should meet. But naming that two-week gap is where its own template stops. Attributing it to a cause is still a discussion prompt, filled in from what the room remembers weeks later.
This pack reconstructs the gap from the record instead. Estimate versus Actual by workstream quantifies exactly where the schedule slipped. Delay Attribution then traces each portion of that slippage to a cause on file. That means a ticket's status history showing time genuinely blocked on another team, a dated entry in the Scope Change Log, or a ticket whose logged time simply ran past its estimate with nothing blocking it. That last case is what an underestimate looks like once recollection drops out of the count.
At Talbrook Systems, a fictional B2B software company, a customer data export pipeline planned for 12 weeks took 19, a 58 percent overrun spread across four workstreams. The retro meeting's notes blamed a vendor's API access delay as the main reason. The ticket history says otherwise. That block cost 8 of the 35 lost days, the smallest of four traced causes, while three tickets that ran past their estimate with no recorded blocker cost 12, the largest share. Nobody named the second one in the room, because it never became one memorable event.
Engineering Project Retrospective Template