|
in which MH brainstorms a project governance structure |
boss
grandboss
project sponsor
project team: business analysts, developers, technology and business project managers
what is your availability/commitment to projects?
when will you be available to work on a new project?
how much time are you spending on x project?
is everything going okay?
percentage availability
what is the burn rate? is the burn rate too fast, too slow?
are there any roadblocks? (and how can I help?)
what do you need in order to be successful?
who are my constituents?
who am I communicating to?
what are the benchmarks against which we will measure our success? (KPI, CTQ, etc.)
what am I building? (exacting specifications)
what is it supposed to do?
what is the structure of the system I am working in?
what systems need to talk to each other?
when is it due?
what do I need to do next?
who are my systems representatives?
do my people have everything they need?
what do you need in order to be successful?
who are my systems representatives?
do my people have everything they need?
what do you need in order to be successful?
$ budget (broken down by chunk of work)
$ spent so far
$ available
target date estimated
today's date
deliverable % complete - progress to task
time increment: daily, weekly, monthly, quarterly, calendar-year, fiscal year
work increment: task, deliverable, phase, project, program