Many organizations separate Agile delivery from project reporting. Teams run Scrum ceremonies while project managers create separate status reports, risk logs, and governance decks for leadership.

Over the years, I’ve found that this creates unnecessary overhead and often results in two versions of the truth.

Instead, I use Scrum events as the primary source of project reporting.

Sprint Planning provides insight into capacity, priorities, dependencies, and upcoming risks. Daily standups reveal blockers, changing assumptions, and emerging issues. Backlog refinement exposes unclear requirements and future constraints. Sprint Reviews demonstrate actual progress and provide direct stakeholder feedback. Retrospectives identify process improvements and recurring delivery problems.

By treating these events as information gathering opportunities rather than just calendar appointments, much of the information needed for status reporting naturally emerges from the team’s normal workflow.

This approach allows me to maintain visibility into scope, schedule, budget, risks, and dependencies without creating a parallel reporting process. Stakeholders receive accurate information because the reports are based on what the team is actually experiencing rather than what someone remembers at the end of the week.

On hybrid projects, I combine this information with my ScrumEVM approach to track the traditional project management baselines of scope, schedule, and cost. This provides leadership with predictive metrics while allowing teams to continue working in an Agile manner.

The result is less administrative overhead, fewer status meetings, and a reporting process that stays connected to reality.

Scrum events are not just ceremonies. They are one of the most valuable sources of project intelligence available to a project manager.