* Color coding the status of each feature in the roadmap using a ppt slide.
* Listing all major milestones with desired due date and current status
I'm hesitant to start time tracking of individual tickets and contributors because I think this is not the truely important kpi. But this is something that gets recommended often when I google "software development progress report".
Have you seen any great reports in the past?
This is generally not a status report - that is largely useless and pretty boring.
What can be useful are things like project risks and mitigations.
What are the things that might derail projects and how are we managing the risks (if at all!).
Anything that the stakeholders can contribute or fix to e.g. we’ve got a bunch of open questions/blockers that need to be escalated.
The problem with most progress reports is they tend to always report things are on track until suddenly they aren’t. This is the most frustrating thing for stakeholders. Why didn’t we see this problem coming - how can it be that everything was fine and now it isn’t?
I loved the old ones even more: https://web.archive.org/web/20080401021836/http://www.bay12g...
The power goals especially, as they made it clear what all these little "features" set out to achieve. They were beautiful to read, and sometimes reading about the feature can be even more exciting than getting the feature itself.
But apparently these were hard to update so Tarn stopped. I think today, you could probably use something like Jira to add and label tickets and then pull it out with the API and export into HTML.