Review code changes, open coding issues, publish release notes. Every one is ready to run, and you can adjust it in plain language.
Show how sprint work changed before stakeholder reviews.
Your Friday sprint report brings progress, blockers, and likely carryover together in a shared document, with links to the issues behind each claim.
Summarize completed work and remaining blockers for a chosen sprint.
Get a sprint report in a shared document for the sprint you choose. See progress and blockers, with links back to the issues.
Share sprint delivery progress and blockers with stakeholders.
Get a dated sprint report you can share. See completed work and point progress, plus blockers and issue links.
Show delivered backlog work and carryover in a review draft.
Your sprint closeout report shows final issue and point totals. Review linked blockers and carryover before sharing the draft.
Summarize sprint progress for stakeholder review.
Get a sprint report draft with current counts and point progress. Review blockers and linked issues before sharing it.
Share sprint progress and open blockers in a PDF for review.
Your teammate gets a sprint report they can download or print, with progress, open blockers, and links back to the issues.
Put completed work and blockers in the morning sprint report.
Get a morning sprint report on your board before planning, with issue and point progress and links to blockers.
Link completed backlog work and remaining risks for sprint reviews.
Your sprint review deck shows completed work and unresolved blockers, with issue links ready for the meeting.
Keep the sprint's completed work visible to stakeholders.
Your shared sprint report stays current each workday morning. Stakeholders see progress and marked blockers, with links to the issues.
Explain product changes and flag missing user impact.
Get a release note draft that turns rough bullets into clear updates, with possible repeats and missing details called out for your review.