You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

caveat emptor

in which MH brainstorms a project governance structure

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 do my stakeholders need to know?

my boss

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?

my grandboss

percentage availability

project sponsor

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?

project team

business analysts

who are my constituents?
who am I communicating to?
what are the benchmarks against which we will measure our success? (KPI, CTQ, etc.)

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

  • No labels