Please login or join to subscribe to this thread
In my case, the dashboard is totally independent of the approach/method that is used in the initiatives that componed the program. Adding to that the program is composed by initiatives that are running based on agile approach and non-agile approch simultaneously. The key is what your audience need to know as information, taking into account information is not the same than data. In our case, our dasboard have traffic light indicators for finance, schedule, resource, scope, risk plus an overall indicator that is created from the others.Adding to that we published bright spots and hot spots.
As Sergio has indicated, the information provided to your senior stakeholders should be driven by their needs in terms of specific measures and the format of those.
In general, at this level, I'd expect to see such information as:
- Benefits realized vs. planned
- Earned value metrics - program & project level
- Top issues & risks
- Key "asks" of the senior leadership team
- Key milestones accomplished since last reporting period and key upcoming milestones
You can also include among other things listed above by Stalwarts, trends, forecast, revenue leakages (in case you are handling revenues) which could come up as your progress in the project, could be few lines on - what would be doing differently and continue to show few times as a summary through out the project, instead of merely writing BAU.
If you want to show EVM metrics, S curves are useful. You can create them using Project Add/in SCurvesPro. Also, you may interpret project data to create Visual Reports in Excel or in a more specialized BI Software like Power BI.
The purpose of executive status meetings is twofold:
1. make them trust you about the future
2. ask for support they can give
ad 1 means being open about risks to avoid surprises and telling them how the project will end (if you show EV then focus on EAC)
ad 2 means even if you do not need anything, ask for something that helps and is easy to give - they will feel good about it
Both are intended to create trust, so do not destroy it by bragging about your achievements.
Be aware that culture on this level is probably different (competitive) to your teams cultures (collaborative).
Please login or join to reply