Jump to content

Project Management/Project Charter

Add links
From Wikiversity
Project Management
  1. Introduction
  2. Organization
  3. Process
  4. Communication
  5. Project Charter
  6. Scope Statement
  7. Change Management
  8. Work Breakdown Structure
  9. Schedule
  10. Resource Allocation
  11. Quality Management
  12. Cost
  13. Risk
  14. Procurement
  15. Closure
Download Learning Guide

Project Charter

Objectives and Skills

[edit | edit source]

Objectives and skills for the project charter portion of Project+ certification include:[1]

  • Explain the requirements to complete a pre-project setup
    • Identify the project
    • Validate the project
    • Prepare a project charter
    • Obtain approval (signature) for project charter
  • Explain the components of a project charter
    • Key project deliverables
    • High level milestones
    • High level cost estimates
    • Identify stakeholders
    • General project approach
    • Problem statement
    • High level assumptions
    • High level constraints
    • High level risks
    • Project objectives

Objectives and skills for the project charter portion of Project+ PK0-004 certification include:[2]

  • Classify project roles and responsibilities
    • Sponsor/champion
      • Approval authority
        • Funding
        • Project charter
        • Baseline
        • High-level requirements
      • Control
      • Marketing
      • Roadblocks
      • Business case/justification
    • Project manager
      • Manage team, communication, scope, risk, budget, and time
      • Manage quality assurance
      • Responsible for artifacts
    • Project coordinator
      • Support project manager
      • Cross-functional coordination
      • Documentation/ administrative support
      • Time/resource scheduling
      • Check for quality
    • Stakeholder
      • Vested interest
      • Provide input and requirements
      • Project steering
      • Expertise
    • Scheduler
      • Develop and maintain project schedule
      • Communicate timeline and changes
      • Reporting schedule performance
      • Solicit task status from resources
    • Project team
      • Contribute expertise to the project
      • Contribute deliverables according to schedule
      • Estimation of task duration
      • Estimation of costs and dependencies
    • Project Management Office (PMO)
      • Sets standards and practices for organization
      • Sets deliverables
      • Provides governance
      • Key performance indicators and parameters
      • Provides tools
      • Outlines consequences of non-performance
      • Standard documentation/templates
      • Coordinate resources between projects

Readings

[edit | edit source]
  1. Wikipedia: Project charter
  2. Kent State: Identify and Develop a Project that Supports your Organization's Core Mission
  3. Wikipedia: Project management#Initiating
  4. Wikipedia: Stakeholder management
  5. PM by PM Blog: What are Project Assumptions and PM by PM Blog: What are Project Constraints?
  6. Zewo Guidelines for Projects and Programmes: What is a project objective?
  7. University of Wisconsin: Stage 2: Initiate the Project
  8. Project Manager: A Quick Guide
  9. Six Sigma: Six Sigma Project Charter
  10. Project Charter Example: Example with Template

Multimedia

[edit | edit source]
  1. YouTube: MS Project 2010 Allocating Resources
  2. YouTube: What is a Project Charter
  3. YouTube: Project Charter Fundamentals
  4. YouTube: How To Create a Project Charter
  5. YouTube: How to write a Project Charter
  6. YouTube: Resource histogram explained for project management
  7. YouTube: Resource Management Example

Activities

[edit | edit source]
  1. Review Wikipedia: Project Management#Initiating and Wikipedia: Stakeholder analysis and wikiHow: Make Your Project Charter.
    • Identify the project.
      • Know the Project Vision. The first measure taken when determining a Project Charter is to identify the project vision. The vision encapsulates the purpose of the project and is the fixed end goal for the project team.
      • Identify your objectives. Then supported on the vision, list three to five targets to be reached by the project. Every aim should be Specific, Measurable, Attainable, Real and Time-bound (SMART).[3]
    • Create a team if necessary for the project.
    • Using a stakeholder mapping method, identify the primary stakeholders.
  2. Select a Project Charter template from one of the following sites:
  3. Add your project information to your selected template to create your project charter.
    • Although the format of project charters can vary tremendously, they should include at least the following basic information:
      • The project’s title and date of authorization
      • The project manager’s name and contact information
      • A summary schedule, including the planned start and finish dates; if a summary milestone schedule is available, it should also be included or referenced
      • A summary of the project’s budget or reference to budgetary documents, an estimate of the approximate cost of the project in money and time.
      • A brief description of the project's high level objectives, including the business need or other justification for authorizing the project
      • Project success criteria, including project approval requirements and who signs off on the project
      • A summary of the planned approach for managing the project, which should describe stakeholder needs and expectations, important assumptions, and constraints, and should refer to related documents, such as a communications management plan, as available
      • A roles and responsibilities matrix
      • A sign-off section for signatures of key project stakeholders
      • A comments section in which stakeholders can provide important comments related to the project

Lesson Summary

[edit | edit source]
  • The initiating processes determine the nature and scope of the project.[4]
  • Although ideas for projects usually abound in non-profit organizations, proposal writers can try to generate fresh ideas by reading newspapers, journals or newsletters related to your organization's mission and talking to colleagues about what topics seem to be getting the most attention in your field. Try to find a unique approach to solving a problem or combination of problems. [5]
  • Most projects fail due to poor definition. This is the leading cause of scope creep, which leads to unavailable resources and more time and budget necessary to completely satisfy scope. Since the plan reflects the work, resources, budget, and time necessary to satisfy the scope it is easy to see the critical importance of understanding the project definition and description. It is also necessary to ensure agreement from all stakeholders before planning. Let stakeholders review the draft of the project definition document, and get their sign-off, before moving to the planning phase of the project. [6]
  • The project charter is usually a short document that refers to more detailed documents such as a new offering request or a request for proposal.[7]
  • The project charter is formally accepted and approved by the project sponsor and other designated stakeholders. Formal approval acknowledges the completion, review and acceptance of all the deliverables produced during the Initiate Stage. Signatures on the project charter document mark final approval of the charter, which is the go-forward agreement. [8]
  • Project Charter is a statement of the scope, objectives, and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project objectives, identifies the main stakeholders, and defines the authority of the project manager. It serves as a reference of authority for the future of the project.[7]
  • Project Management Office (PMO) is a department within a business, agency, or enterprise that defines and maintains standards for project management within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects.
  • A key deliverable is an item - either tangible or intangible - produced as a part of a project. [9]
  • Milestones are deliverables or major events to be achieved on a specified date. They can be viewed as ”how are we doing” thresholds indicating whether a project is on track to finish as expected. [10]
  • A high-level budget is a summary of the estimated costs to complete the high-level project milestones. Generally, there are three types of costs that can be included in a high-level budget: Labor costs, Material costs, Non-labor costs. [11]
  • Stakeholder analysis is the process of identifying the individuals or groups that are likely to affect or be affected by a proposed action, and sorting them according to their impact on the action and the impact the action will have on them.[12]
  • The objective of the project management approach is to define the project management methodologies that will be used on the project. The approach should be based on the project management framework but should also include reference to and iterative development, or prototyping methodologies that will be utilized. [13]
  • A problem statement is a clear description of the issue(s), it includes a vision, issue statement, and method used to solve the problem. A problem statement expresses the words that will be used to keep the effort focused and it should represent a solveable problem. [14]
  • Project Assumptions are events or circumstances that are expected to occur during the project life-cycle. [15]
  • Project Constraints are restrictions imposed by Stakeholders or Environment that limits Project Team’s options. [16]
  • During the early phases of project planning, assessments must be made as to whether the project can be completed successfully. Usually these are GO/ NO GO decisions. While very little detail may be known at this point, the high-level risks should attempt to be identified and assessed. These steps include: identifying risks at the highest level of the work tasks; analyzing the associated costs and benefits of the project to determine the relative risks of potential gains; and developing high-level mitigation strategies to reduce the impact of potential events. [17]
  • The project objective describes the project’s outcomes: intended and direct, short- and medium-term effects on the target group. The project objective must lie within the scope of the project, and one must be able to directly attribute the effects to the project. [18]

Key Terms

[edit | edit source]
  • business case - Used to justify the investment. Includes the project objective, high-level requirements, and time and cost goals.[19]
  • constraint - A limitation or restriction.[20]
  • contract - An agreement between two or more parties.[21]
  • cost - The value of money that is correlated to an item or service.[22]
  • deliverable - A product or service produced or provided as part of a project.[23]
  • enterprise environmental factors - Includes relevant government or industry standards, the organization’s infrastructure, and marketplace conditions.[24]
  • initiating - Processes defining and authorizing a project and/or project phase.[25]
  • milestones - Specific points along a project timeline.[26]
  • objectives - Goals.[27]
  • organizational process assets - include formal and informal plans, policies, procedures, guidelines, information systems, financial systems, management systems, lessons learned, and historical information that can influence a project’s success.[28]
  • problems - Undesirable situations that prevent an organization from achieving its goals.[29]
  • project - A temporary endeavor undertaken to create a unique product, service, or result.[30]
  • project charter - A document that formally recognizes the existence of a project and provides direction on the project’s objectives and management.[31]
  • project manager - A professional in the field of project management.[32]
  • risk - Potentially gaining or losing of something[33]
  • schedule - A plan for carrying out a process or procedure, giving lists of intended events and times.[34]
  • scope - All the work involved in creating the products of the project and the processes used to create them.[35]
  • stakeholders - People involved in or affected by project activities.[36]
  • stakeholder analysis - A technique for analyzing information to determine which stakeholders’ interests to focus on and how to increase stakeholder support throughout the project.[37]
  • statement of work - a document that describes the products or services to be created by the project team.[38]
  • task - An activity that needs to be accomplished within a period of time.[39]
  • template - A preset format for a document or file, used so that the format does not have to be recreated each time it is used.[40]

Review Questions

[edit | edit source]
Enable JavaScript to hide answers.
Click on a question to see the answer.
  1. The ______ processes determine the nature and scope of the project
    Initiating
  2. Although ideas for _____ usually abound in non-profit organizations, proposal writers can try to generate fresh ideas by reading newspapers, journals or newsletters related to your organization's mission and talking to colleagues about what topics seem to be getting the most attention in your field. [4]
    Projects
  3. Most projects fail due to poor definition. This is the leading cause of scope _____, which leads to unavailable resources and more time and budget necessary to completely satisfy scope.
    Creep
  4. The project _____ is usually a short document that refers to more detailed documents such as a new offering request or a request for proposal.
    Charter
  5. The project charter is formally accepted and approved by the project _____ and other designated stakeholders.
    Sponsor
  6. Project Charter is a statement of the _____, objectives, and participants in a project.
    Scope
  7. A key _____ is an item - either tangible or intangible - produced as a part of a project.
    Deliverable
  8. _____ are deliverables or major events to be achieved on a specified date. Milestones can be viewed as ”how are we doing” thresholds indicating whether a project is on track to finish as expected.
    Milestones
  9. A high-level budget is a summary of the estimated costs to complete the high-level project milestones. Generally, there are three types of costs that can be included in a high-level budget: _____ costs, _____ costs, Non-labor costs. [10]
    Labor, Material
  10. _____ analysis is the process of identifying the individuals or groups that are likely to affect or be affected by a proposed action, and sorting them according to their impact on the action and the impact the action will have on them.[11]
    Stakeholder
  11. The objective of the project management approach is to define the project management _____ that will be used on the project.
    Methodologies
  12. A problem statement expresses the words that will be used to keep the effort focused and it should represent a _____ problem.
    Solvable
  13. Project _____ are events or circumstances that are expected to occur during the project life-cycle.
    Assumptions
  14. Project _____ are restrictions imposed by Stakeholders or Environment that limits Project Team’s options.
    Constraints
  15. During the early phases of project _____, assessments must be made as to whether the project can be completed successfully.
    Planning
  16. The project objective must lie within the _____ of the project, and one must be able to directly attribute the effects to the project.
    Scope

Assessments

[edit | edit source]
  1. Take Go Skills: Project Charter Quiz
  2. Review Quizlet: Project Charter
  3. Take Quizlet: Project Charter
  4. Review Quizlet: Process Groups and Project Charter

References

[edit | edit source]
Type classification: this is a lesson resource.
  1. ↑ CompTIA: Project+ Certification Exam Objectives: PK0-003
  2. ↑ CompTIA: Project+ Certification Exam Objectives: PK0-004
  3. ↑ http://www.wikihow.com/Make-Your-Project-Charter
  4. ↑ https://en.wikipedia.org/wiki/Project_management#Initiating
  5. ↑ http://literacy.kent.edu/Oasis/grants/first2.html
  6. ↑ https://www.projectsmart.co.uk/project-planning-the-first-line-of-defence-for-preventing-failed-projects.php
  7. ↑ 7.0 7.1 https://en.wikipedia.org/wiki/Project_charter
  8. ↑ https://pma.doit.wisc.edu/initiate/7/what.html
  9. ↑ http://study.com/academy/lesson/key-deliverables-in-project-management-definition-lesson-quiz.html
  10. ↑ https://pma.doit.wisc.edu/initiate/4/what.html
  11. ↑ https://pma.doit.wisc.edu/initiate/5/what.html
  12. ↑ https://en.wikipedia.org/wiki/Stakeholder_analysis
  13. ↑ http://www.information-management-architect.com/project-management-approach.html
  14. ↑ http://www.ceptara.com/blog/how-to-write-problem-statement
  15. ↑ http://www.pmbypm.com/what-are-assumptions
  16. ↑ http://www.pmbypm.com/project-constraints
  17. ↑ https://www.chandleraz.gov/Content/PM102HighLevRiskIdGDE.pdf
  18. ↑ http://impact.zewo.ch/en/impact/step1_define_objectives/project_objective
  19. ↑ https://shelf.brytewave.com/#/books/9781337431095/cfi/6/26!/4/278/4/2/2@0:0
  20. ↑ https://en.wikipedia.org/wiki/Constraint
  21. ↑ https://en.wikipedia.org/wiki/Contract
  22. ↑ https://en.wikipedia.org/wiki/Contract
  23. ↑ https://en.wikipedia.org/wiki/Deliverable
  24. ↑ https://shelf.brytewave.com/#/books/9781337431095/cfi/6/26!/4/284/4@0:54.0
  25. ↑ http://www.dictionary.com/browse/initiate?
  26. ↑ https://en.wikipedia.org/wiki/Milestone_(project_management)
  27. ↑ https://en.wikipedia.org/wiki/Objective
  28. ↑ https://shelf.brytewave.com/#/books/9781337431095/cfi/6/26!/4/284/4@0:54.0
  29. ↑ https://www.merriam-webster.com/dictionary/problem
  30. ↑ https://www.merriam-webster.com/dictionary/problem
  31. ↑ https://en.wikipedia.org/wiki/Project_charter
  32. ↑ https://en.wikipedia.org/wiki/Project_manager
  33. ↑ https://en.wikipedia.org/wiki/Risk
  34. ↑ http://www.dictionary.com/browse/schedule
  35. ↑ https://en.wikipedia.org/wiki/Scope_(project_management)
  36. ↑ https://en.wikipedia.org/wiki/Stakeholder_(corporate)
  37. ↑ https://en.wikipedia.org/wiki/Stakeholder_analysis
  38. ↑ https://shelf.brytewave.com/#/books/9781337431095/cfi/6/26!/4/278/4/2/2@0:0
  39. ↑ https://en.wikipedia.org/wiki/Task_(project_management)
  40. ↑ https://en.wikipedia.org/wiki/Template

References

[edit | edit source]

<References/

Retrieved from "https://en.wikiversity.org/w/index.php?title=Project_Management/Project_Charter&oldid=2651756"