Info | ||
---|---|---|
| ||
This is a brainstorm document, not intended as a deliverable for any task, in which MH explores a project governance structure. The questions on this list are answered by deliverables in the REPORTING RUNNING classification. |
THIS PAGE EXISTS IN TANDEM WITH REPORTING
I am a builder (or three, or twelve). What do I need to learn and know, in order to complete my task?
who are my stakeholders?
boss
grandboss: Kevin, Steve, Marilyn, Terry
project sponsor
project team: business analysts, developers, technology and business project managers
audience/users: faculty, students, staff, MIT community, external
what I need from my stakeholders?
my boss
...
my grandboss
what is your percentage of availability?
what is the distribution of your time, by percentage of your time, across projects for the next time increment?
project sponsor
...
...
project team
business analysts
...
developers
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?
project manager: technology
who are my systems representatives?
do my people have everything they need?
what do you need in order to be successful?
project manager: business
who are my systems representatives?
do my people have everything they need?
what do you need in order to be successful?
what are my options?
the data
$ budget (broken down by chunk of work)
$ spent so far
$ available
target date estimated
today's date
deliverable % complete - progress to task
communication media
time increment: daily, weekly, monthly, quarterly, calendar-year, fiscal year
work increment: task, deliverable, phase, project, program
size: cost, time, complexity
complexity: lines, modules, objects, components, systems, networks