Copy these prompts into ChatGPT, fill in your project details, and get retrospective drafts ready to share with stakeholders. No more staring at blank documents when the retro is due tomorrow.
These prompts pair well with Jasper AI for Project Managers-specific tone control, or Copy.ai for fast iteration.
Sprint Retrospective Documentation
You are a Scrum Master writing a sprint retrospective summary for stakeholders.
Sprint: {sprint_number} Team: {team_name} Sprint goal: {sprint_goal_statement} Goal achievement: {fully_achieved / partially_achieved / not_achieved} Key metrics: {velocity}, {completed_story_points}, {bugs_found} Biggest win: {specific_achievement} Main blocker: {primary_impediment} Team mood: {high / medium / low}
Write a 300-word stakeholder-ready sprint retrospective. Open with goal achievement status and key metrics. Include one specific win with business impact. Address the main blocker and mitigation steps. Close with three concrete actions for next sprint.
When to use it: Friday afternoon when leadership asks for the retro summary before you leave.
Pro tip: If your sprint goal wasn’t achieved, lead with what was delivered instead of what wasn’t. Stakeholders care more about value than story points.
You are documenting a failed sprint for lessons learned.
Sprint duration: {sprint_length} Original commitment: {planned_story_points} Actual delivery: {delivered_story_points} Major incident: {incident_description} Time lost: {hours_or_days} Root cause: {technical / process / people / external} Team size: {number_of_developers} Recovery actions taken: {immediate_fixes}
Write a 400-word lessons learned document using the 5 Whys framework. Start with what went wrong without blame. Drill down through five levels of why this happened. End with three process changes to prevent recurrence. Tone should be analytical, not defensive.
When to use it: When a sprint goes badly and you need to document learnings for the retrospective database.
Pro tip: Focus on system failures, not people failures. Even when someone made a mistake, ask why the system allowed that mistake to happen.
You are writing a retrospective for a sprint that exceeded expectations.
Team: {team_name} Planned velocity: {original_velocity} Actual velocity: {achieved_velocity} Percentage increase: {percentage_over_plan} New practice introduced: {process_change} Team feedback on change: {positive / mixed / negative} Quality metrics: {bug_count}, {test_coverage} Stakeholder reaction: {very_positive / positive / neutral}
Write a 250-word success retrospective. Identify what specifically drove the performance improvement. Analyze if this velocity is sustainable or one-time. Include any quality trade-offs. Recommend whether to continue the new practice. Frame as data-driven analysis, not celebration.
When to use it: When your team crushes their sprint goals and you need to capture what worked.
Pro tip: High velocity often comes with hidden technical debt. Always check code quality metrics before declaring victory.
You are documenting team dynamics issues from a sprint retrospective.
Team size: {team_members} Issue type: {communication / collaboration / conflict / motivation} Specific incident: {what_happened_when} People affected: {number_without_names} Impact on delivery: {delayed / quality_issues / no_impact} Current team satisfaction: {high / medium / low} Previous similar issues: {yes / no} Proposed solution: {specific_intervention}
Write a 300-word team dynamics retrospective for your manager. Describe the issue objectively without naming individuals. Explain delivery impact with examples. Propose one specific intervention with timeline. Include how you’ll measure improvement. Keep tone professional and solution-focused.
When to use it: When team issues surface in the retro and your manager needs to know.
Pro tip: Always propose a specific intervention, not vague “team building.” Concrete actions like pair programming rotations or daily check-ins work better than workshops.
You are writing a technical debt retrospective after a sprint focused on cleanup.
Technical debt addressed: {specific_debt_items} Time invested: {developer_days} Measurable improvements: {performance_gains / maintainability_score / bug_reduction} Remaining debt: {priority_items_left} Developer satisfaction change: {improved / same / worse} Business value delivered: {customer_facing_improvements} Velocity impact: {faster / slower / same} Stakeholder buy-in: {strong / weak / resistant}
Write a 350-word technical debt retrospective proving ROI to stakeholders. Open with measurable improvements achieved. Translate technical gains into business language. Address the remaining debt with prioritized recommendations. Close with velocity predictions for future sprints. Use data, not developer feelings.
When to use it: After convincing stakeholders to let you spend a sprint on technical debt cleanup.
Pro tip: Measure everything before and after the debt sprint. Page load times, deployment frequency, and bug rates are easier for stakeholders to understand than code complexity scores.
Project Milestone Reviews
You are writing a milestone retrospective for a project approaching deadline.
Milestone: {milestone_name} Original deadline: {planned_date} Actual completion: {actual_date} Budget status: {under / on / over} by {amount_or_percentage} Scope delivered: {percentage_of_planned_features} Quality status: {bug_count}, {test_coverage} Stakeholder satisfaction: {high / medium / low} Team burnout level: {high / medium / low} Critical path risks: {top_two_risks}
Write a 400-word milestone retrospective for the steering committee. Lead with deadline and budget status. Explain any scope changes with business justification. Address quality concerns honestly. Highlight critical path risks for remaining milestones. Recommend resource adjustments if needed. Executive summary tone.
When to use it: When you hit a major project milestone and need to brief the steering committee.
Pro tip: If you’re behind schedule, always come with a recovery plan, not just problems. Executives want solutions, not status updates.
You are documenting lessons learned from a cancelled project milestone.
Cancelled milestone: {milestone_name} Reason for cancellation: {market_change / budget_cut / technical_blocker / strategy_shift} Work completed: {percentage_done} Sunk costs: {amount_spent} Reusable deliverables: {components_to_salvage} Team morale impact: {high / medium / low} Stakeholder communication: {transparent / delayed / poor} Decision timeline: {days_from_issue_to_cancellation}
Write a 300-word lessons learned document for the project portfolio office. Analyze the cancellation decision objectively. Identify early warning signs that were missed. Document what work can be salvaged for future projects. Recommend process improvements for faster decision-making. No blame, just systems thinking.
When to use it: When a project gets cancelled and the PMO wants to capture lessons for future projects.
Pro tip: Focus on decision-making speed, not the decision itself. Most cancelled projects fail because organizations take too long to admit failure.
You are writing a retrospective for a milestone delivered with major scope cuts.
Original scope: {planned_features} Delivered scope: {actual_features} Features cut: {removed_functionality} Reason for cuts: {time / budget / quality / technical_complexity} Stakeholder reaction: {accepting / disappointed / angry} User impact: {minimal / moderate / significant} Technical debt created: {shortcuts_taken} Recovery plan: {how_to_restore_cut_features}
Write a 350-word scope change retrospective for stakeholders. Explain why cuts were necessary with data. Assess user impact honestly. Document technical debt created by shortcuts. Present a costed plan for restoring cut features in future releases. Maintain confidence while being transparent about trade-offs.
When to use it: When you had to cut scope to hit a deadline and stakeholders want to understand the impact.
Pro tip: Always quantify the cost of restoring cut features. Stakeholders need to understand that “just adding it back” isn’t free.
You are documenting a milestone that succeeded due to external vendor performance.
Milestone: {milestone_name} Vendor: {vendor_name} Vendor deliverables: {specific_contributions} Internal team role: {integration / oversight / coordination} Vendor performance: {exceeded / met / below_expectations} Communication quality: {excellent / good / poor} Issue resolution speed: {fast / adequate / slow} Cost performance: {under / on / over_budget} Lessons about vendor management: {key_insights}
Write a 300-word vendor performance retrospective for procurement. Assess vendor delivery against contract commitments. Document communication and issue resolution effectiveness. Identify best practices for managing this vendor relationship. Recommend contract modifications for future phases. Include cost performance analysis. Procurement-friendly language.
When to use it: When a vendor plays a major role in milestone success and procurement wants lessons learned.
Pro tip: Document vendor communication preferences and escalation paths that worked. This information is gold for future vendor relationships.
You are writing a retrospective for a milestone achieved with distributed team coordination.
Team locations: {geographic_distribution} Time zone spread: {hours_difference} Communication tools used: {primary_platforms} Meeting cadence: {frequency_and_format} Cultural challenges: {language / work_style / holiday_conflicts} Productivity compared to co-located: {higher / same / lower} Major coordination successes: {what_worked_well} Coordination failures: {what_broke_down}
Write a 350-word distributed team retrospective for HR and future project managers. Analyze productivity vs co-located teams with specific examples. Document communication patterns that worked. Identify cultural considerations that impacted delivery. Recommend tool and process improvements. Include timezone optimization strategies.
When to use it: After completing a major milestone with a distributed team and the organization wants to scale remote work practices.
Pro tip: Track decision-making speed across time zones. Async decision-making often becomes the bottleneck, not development work.
Cross-Team Collaboration Reviews
You are documenting a retrospective for a project requiring coordination between development and marketing teams.
Project: {project_name} Development deliverables: {technical_outcomes} Marketing deliverables: {campaign_elements} Handoff points: {number_of_exchanges} Communication gaps: {specific_breakdowns} Timeline conflicts: {competing_priorities} Success metrics: {shared_kpis_achieved} Relationship quality: {improved / maintained / damaged} Process lessons: {coordination_insights}
Write a 350-word cross-functional retrospective for department heads. Identify successful collaboration patterns with examples. Document handoff failures and root causes. Analyze competing priorities that created conflict. Recommend process improvements for future dev-marketing projects. Include shared metrics that aligned both teams.
When to use it: When a project requires tight dev-marketing coordination and department heads want to improve cross-functional work.
Pro tip: Focus on handoff quality, not handoff frequency. Too many touchpoints often create more confusion, not better alignment.
You are writing a retrospective for a project that required legal, compliance, and engineering coordination.
Regulatory requirements: {compliance_standards} Legal review cycles: {number_of_iterations} Engineering rework: {technical_changes_required} Approval timeline: {days_from_submission_to_approval} Risk mitigation: {compliance_risks_addressed} Process efficiency: {smoother / same / more_complex_than_expected} Documentation quality: {audit_ready / needs_work / insufficient} Stakeholder alignment: {strong / moderate / weak}
Write a 400-word regulatory compliance retrospective for the chief risk officer. Document the approval process timeline with bottlenecks identified. Assess documentation quality for audit readiness. Analyze engineering rework caused by late compliance feedback. Recommend earlier legal engagement for future regulated projects. Risk management focus.
When to use it: After completing a project in a regulated industry and the risk officer wants process improvements.
Pro tip: Map compliance feedback timing to engineering cost. Late legal changes are exponentially more expensive than early guidance.
You are documenting a retrospective for a project requiring coordination with external client teams.
Client organization: {client_name} Client team size: {number_of_client_stakeholders} Communication protocols: {formal / informal / mixed} Decision-making authority: {clear / unclear / constantly_changing} Client feedback quality: {detailed / vague / contradictory} Change request frequency: {number_of_scope_changes} Relationship status: {stronger / maintained / strained} Revenue impact: {profit_margin_effect} Contract lessons: {commercial_insights}
Write a 350-word client collaboration retrospective for account management. Assess client communication effectiveness with examples. Document scope change patterns and decision-making clarity. Analyze relationship health and revenue impact. Recommend account management improvements for similar client types. Include contract structure lessons learned.
When to use it: After completing a major client project and account management wants to improve future client relationships.
Pro tip: Document client decision-makers’ communication preferences and authority levels. This intelligence is crucial for future projects with the same client.
You are writing a retrospective for a project requiring coordination between in-house teams and external consultants.
Consultant firm: {consulting_company} Consultant expertise: {specialized_skills_provided} Knowledge transfer quality: {excellent / adequate / poor} Integration challenges: {cultural / technical / process_differences} Cost vs internal estimate: {percentage_difference} Timeline impact: {faster / same / slower_than_internal} Internal team learning: {skills_gained} Ongoing support needs: {post_project_dependencies}
Write a 300-word consultant collaboration retrospective for finance and operations. Compare consultant delivery to internal capability estimates. Assess knowledge transfer effectiveness with specific examples. Document integration challenges and solutions. Analyze total cost of ownership including ongoing support. Recommend make-vs-buy criteria for future similar projects.
When to use it: After working with external consultants and finance wants to evaluate the make-vs-buy decision for future projects.
Pro tip: Measure knowledge retention three months after consultants leave. True knowledge transfer shows up in your team’s ability to maintain and extend the consultant’s work.
You are documenting a retrospective for a project requiring coordination between product, engineering, and customer success teams.
Feature delivered: {product_functionality} Engineering complexity: {technical_difficulty_level} Customer feedback integration: {user_input_incorporated} Support impact: {ticket_volume_change} User adoption rate: {percentage_uptake} Cross-team communication: {daily / weekly / ad_hoc} Priority conflicts: {competing_roadmap_items} Success metrics achieved: {shared_goals_met}
Write a 350-word product delivery retrospective for the VP of Product. Analyze feature adoption against engineering investment. Document customer success insights that shaped the product. Assess cross-team communication effectiveness. Identify priority conflicts that slowed delivery. Recommend collaboration improvements for future feature development.
When to use it: After shipping a major product feature and the VP wants to optimize the product development process.
Pro tip: Track the time from customer feedback to feature delivery. This cycle time is a key indicator of product-engineering-success alignment.
Stakeholder Communication Reviews
You are writing a retrospective on stak