Part of a series on customising Microsoft® Project® to make working with schedules more useful.
This post describes how to generate universally-readable “soft” PDF Gantt charts to circulate to stakeholders, with dynamically generated labels that provide them with useful information about the view, and provide you with useful information about how you might re-create the view.
Following on from my post on watermelon reporting, I wanted to share another, related, phenomenon with you – “green side up” reporting. This describes the phenomenon where the health of programmes and portfolios is reported more favourably the higher up the organisation the reports are circulated; that is to say that in the project world everything looks green when viewed from above.
How do watermelons get into project reports? and why should you watch out for them?
“Watermelon reporting” describes the phenomenon where according to a project status report things appear to be green on the outside (i.e. the project’s RAG status is reported as green, with no issues), but if you delve a little deeper and look inside, it’s actually red right through (i.e. there are serious issues). Continue reading “Watch out for watermelons in project reports”
How do you give senior management a “helicopter view” of all the change that is going on in an organisation, so that they can make informed decisions on how to spend their change budget? Here’s how I tackled it…