3 ms·
The best way to approach this is to find out what the questions are that the stakeholders have and then work out how to best answer them. This is generally not
by iamflimflam1 3y ago
The best way to approach this is to find out what the questions are that the stakeholders have and then work out how to best answer them.
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?
- hasoleju 3y agoGood point. I will make the spent effort vs. estimated effort of a feature more transparent. This will show the risk of features getting delayed because no one is working on them. If it is transparent that no one is working on a topic, one can drill down to see what the reasons are. Stakeholders than can help to unblock that situation.