Review code changes, open coding issues, publish release notes. Every one is ready to run, and you can adjust it in plain language.
Show each delivery team member's sprint work and blockers.
Get a sprint report by assignee with completed work, open work, points, and blockers, linked from your chat thread.
Review client code patches and log findings for the delivery team.
Get a second opinion on your code patch, with actionable findings in the shared review document before your team merges the change.
Draft notes on changes between versions of client software.
Get a release note draft in your docs after your repository publishes a version, with a clear summary and links to the changes behind it.
Show client delivery teams which sprint issues need attention.
Your team gets a sprint halftime report in its shared document, with point progress against current scope and links to work needing attention.
Explain progress and blockers in client project sprints.
Your Friday sprint report brings progress, blockers, and likely carryover together in a shared document, with links to the issues behind each claim.
Document sprint progress and blockers for client delivery teams.
Get a sprint report in a shared document for the sprint you choose. See progress and blockers, with links back to the issues.
Document client sprint progress and open blockers for sharing.
Get a dated sprint report you can share. See completed work and point progress, plus blockers and issue links.
Draft client sprint updates from current issue progress and blockers.
Get a sprint report draft with current counts and point progress. Review blockers and linked issues before sharing it.