Project Retrospective: Root Causes & Process Fixes

Thanks for taking a few minutes to reflect on this project. Your responses are completely confidential and anonymized. Your honest read on what worked, what didn't, and what should change helps us actually fix things next time. About 6-8 minutes.

Overall, how successful was this project relative to its original goals (scope, timeline, quality)?

Rate how each part of the project went.

Which of these contributed to the project's biggest setbacks? Select all that apply.

• Unclear or shifting requirements
• Scope creep
• Insufficient staffing or skills
• Poor communication across teams
• Unrealistic timeline or estimates
• Technical debt or legacy systems
• Lack of stakeholder buy-in
• Dependency delays from other teams
• Unclear ownership or decision rights

In your own words, describe the single most significant failure or near-miss moment on this project — what happened, and when did the team first notice something was off?

Rank these potential process changes from most to least valuable for this team to adopt on the next project. (Template note: replace with your own candidate process changes before launching, based on internal input.)

1. Add a formal scope-freeze milestone before build starts
2. Hold a weekly cross-team sync on dependencies
3. Build explicit buffer time into estimates
4. Run a lightweight retro after every sprint, not just at the end
5. Clarify ownership with a RACI-style breakdown
6. Increase automated test coverage before release
7. Improve handoff documentation between teams

Reconstruct the actual sequence of events behind the single biggest setback the respondent described: what decision or signal came first, who noticed it, how long it took to escalate, and what was tried before it became a real problem. If they named a process change they ranked highest, probe what would concretely block their team from adopting it next time and what would need to be true for it to actually stick.

Realistically, without extra management pressure, how likely is your team to actually adopt the process change you ranked highest?

Which best describes your role on this project?

• Project or program lead
• Individual contributor / builder
• Product or business owner
• Engineering or technical lead
• QA or testing
• Prefer not to say

How long were you involved with this project?

• Less than 1 month
• 1-3 months
• 4-6 months
• More than 6 months
• Prefer not to say

That's everything — thank you for the candid feedback. Responses across the team will be compiled into a root-cause summary and a short list of process changes for leadership to review before the next project kicks off.