Project Initiation and Project Charter
- Initiating process group, and project scope management key terms
- Project charter
- Constraints and assumptions
- Identify stakeholders
- Collect requirements
- Project scope statement
- Scope management plan
- Define scope
- Decomposition process
- Work breakdown structure
- WBS dictionary
- Some common reasons why projects fail
- Misunderstood customer needs – requirements
- Inappropriate budgets or schedules
- Over extended burned out project team members
- Results that fall short of current quality or tech standards
- Projects that don’t fit with organizations strategic goals
- Process Groups – Initiating
- Project selection methods – Usually selected by measuring their value to the project owner
- Internal business needs
- External influences:
- Problems
- Opportunities
- Business requirements
- Formal decision models
- Benefit Measurement (comparative)
- Murder board
- Peer reviews
- Cost/benefit
- Scoring model
- Economic model
- Constrained optimization (mathematical programming algorithms)
- Linear
- Non-linear
- Integer
- Dynamic
- Multi-objective
- Benefit Measurement (comparative)
- Develop Project Charter
- Developing a document that formally authorizes a project or project phase.
- Documenting initial stakeholder requirements
- Identify stakeholders – Identifying and documenting relevant information for all people or organizations impacted by the project.
- Inputs
- Project statement of work
- Business case
- Contract (when applicable)
- Enterprise environmental factors (EEF)
- Organization Process Assets (OPA)
- Tools and techniques – Expert judgment
- Outputs – Project Charter
- The project charter
- Projects are authorized by someone external to the project
- Sponsor
- PMO
- Steering committee
- Project is issued/signed by: Sponsor, initiator, Mgt
- At a level of authority to be able to fund the project
- This signatures authorizes the project
- Identifies the PM as early as possible
- Recommended that PM participate in charter development; may be delegated to PM.
- PM should always be assigned prior to planning
- Charter provides authority to PM to use resources
- Documents: Initial project requirementsthat will satisfy the stakeholders needs and expectations
- Develop Charter Inputs
- Statement of work
- Narrative description of product or services
- Business need
- Product scope description
- Product characteristics
- Relationship to business need
- Strategic plan – should support strategic goals
- Business case to justify project
- Market demands
- Organizational need
- Customer request
- Technical advance
- Legal
- Social
- Ecological
- Contract (external customer)
- Enterprise environmental factors
- Marketplace conditions
- Gov’t or industry standards
- Organizational infrastructure
- Organizational Process assets
- Org standards
- Processes and policies
- Template (project charter)
- Historical information
- Lessons learned knowledge base
- Tools and techniques
- Expert judgment – used throughout the project process
- Provided by any group or individual with specialized knowledge or training
- Internal experts: SME’s, PMO, Stakeholders,
- External Experts: Consultants, Professional associations, Industry groups
- Used to assess the inputs used to develop the project charter and address technical and management details during the process
- Expert judgment – used throughout the project process
- Outputs – what should be included
- Project purpose/description
- Business need
- Project justification
- PM assigned and level of authority defined
- Summary budget, milestones, hi-level risks
- Resources pre-assigned
- Project objectives/success criteria/sign-off
- High-level requirements
- Product scope description = deliverables and business need they will satisfy
- Narrative description of product or services
- Statement of work
- Projects are authorized by someone external to the project
10. Signed and authorized by project sponsor/initiator/senior management
Next Up: Project Scope