MIS 578 Chapter 3 Flashcards
Project Charter
A project charter is like an informal contract between the project team and the sponsor
Why is a project charter used?
The project charter is used to authorize PROJECT MANAGER to proceed, help develop common understanding, help team and sponsor to commit, and screen out poor projects.
What is a preliminary scope statement?
It is a more detailed version of scope overview section of the charter
Typical elements of a charter
1) Title
2) Scope overview
3) Business case
4) Background
5) Milestone schedule w/ acceptance criteria
6) Risks, assumptions, & constraints
7) Spending approvals or budget estimates
8) communication plan requirements
9) Team operating principles
10) Lessons learned
11) signatures and commitment
Title
A meaningful title helps people understand the project quickly.
Scope overview
The “what” of the project. The project in a nutshell: what needs to be delivered and what work
is involved in creating it.
This is the “elevator speech” – a half minute summary of the project. Ideally, sponsor provides
rough draft or at least input. Each of these sections should be of one to four sentences.
Business Case
The “why” of the project. How the project will benefit the organization – how it supports the
organization’s strategy.
This is the “elevator speech” – a half minute summary of the project. Ideally, sponsor provides
rough draft or at least input. Each of these sections should be of one to four sentences.
Background
Optional. More details under business case if needed.
If team wants more detail than four sentences in any of the previous sections, the extra details
can be included in this optional section.
Milestone schedule with acceptance criteria
Powerful visual summary of high-level schedule combined with how key stakeholder will
evaluate progress at each point.
Table with four columns one each for milestones, dates, stakeholder (who will judge), and
acceptance criteria can be used. Six-step process includes describing current situation,
describing desired end state, describing end state stakeholder and acceptance criteria,
determining milestones, determining expected completion dates for each milestone, and
identifying stakeholder and acceptance criteria for each milestone.
Risk, assumptions, & constraints
Risks are uncertain events, assumptions are factors believed to be true, and constraints are
limitations. Each can influence the project.
This section can vary. At a minimum, brainstorming is done about risks and one risk is noted per
Post-It® Note, determining by group consensus the likelihood and the impact of each risk,
creating contingency plans and assigning ownership for each big risk.
Spending approvals or budget estimates
Preliminary project budget or at least pre-approval to cover minor expenses.
Listing any preliminary budget or at least authorization to spend minor amounts of money
without further approval.
Communication plan requirements
Table with stakeholders identified along with what each needs to know, when, and the most
effective way for them to receive it.
A five-column table is created listing stakeholders, what the project team needs to learn from
each, what the project team needs to share with each, the timing for each communication, and
the method that will be most effective for the stakeholder to receive and understand it.
Team operating principles
Guidelines to enhance team functioning. Often include meetings, decision-making, accomplishing work, and showing respect.
Either existing team principles are discussed or new ones are formulated.
Lessons learned
How the current project will be better because of learning on previous project(s).
Useful practices are identified to copy or tailor from previous projects and/or less useful
practices to be avoided.
Signaturess and commitment
Public and personal commitment to the project.
Signature blocks are created to be signed after ratifying charter.