Contemporary Project Management: Project Chartering

Overview of a Project Charter

  • A Project Charter is an informal contract between the Project Team and the Sponsor, serving as a foundational document for project success.
    • Defines expectations, goals, and responsibilities between parties.
    • It is a living document, evolving as project conditions change.

Purposes of a Project Charter

  • Authorization: Grants permission for the project manager to allocate resources and proceed.
  • Common Understanding: Aligns the project manager, sponsor, and team on project goals.
    • Fosters trust, communication, and commitment among participants.
  • Screening Projects: Helps quickly evaluate projects that are not viable before further investment.

When is a Project Charter Needed?

  • Charters are necessary when projects involve:
    • Multiple departments or complex operations.
    • A clear set of goals and resources required.
    • Stakeholder interests that span beyond initial scopes.

Key Elements of a Project Charter

  1. Title: Unique and meaningful, reflecting key characteristics.
  2. Scope Overview: Defines project boundaries and helps avoid scope creep.
  3. Business Case: Justification of the project aligned with organizational goals.
  4. Background: Contextual details supporting the scope and business case (optional).
  5. Milestone Schedule: Timeline of major deliverables and acceptance criteria.
  6. Risks, Assumptions, Constraints: Documenting known variables affecting project success.
  7. Resource Estimates: Preliminary budget considerations and required commitments.
  8. Stakeholder List: Identification of key participants and their interests.
  9. Team Operating Principles: Agreed norms and processes for team collaboration.
  10. Lessons Learned: Insights from previous projects to inform the current initiative.
  11. Signatures and Commitment: Formal acknowledgment from all key parties.

Constructing a Project Charter

  • The charter is developed collaboratively, often starting with the project sponsor's draft of the Scope Overview and Business Case.
  • The Milestone Schedule outlines major tasks and target completion dates, which can be created using tools like Microsoft Project.
  • Thorough documentation of Risks, Assumptions, and Constraints should inform project planning, ensuring all potential issues are addressed.
  • Engage with stakeholders regularly to gather feedback and revise the charter as needed.

Agile Projects vs. Plan-Driven Projects

  • Agile charters focus on adaptability and provide a product roadmap instead of detailed specifications.
  • Emphasizes iterative development, flexibility, and minimal upfront commitment, allowing adjustments as the project evolves.
  • The Definition of Done becomes crucial in Agile, ensuring all team members understand what constitutes project completion.

Ratifying the Project Charter

  • The ratification process includes presenting the draft to stakeholders, answering questions, and getting signatures from the project manager, sponsor, and core team.
  • Effective negotiation throughout this process ensures all concerns are addressed and expectations are clear.

Start Rating a Project Using MS Project

  • Begin by setting up the project environment in MS Project, defining the start date, and outlining the project structure.
  • Use the Gantt Chart view to organize tasks and milestones, facilitating clear visibility on timeline and dependencies.

Summary

  • A Project Charter is essential for aligning project stakeholders on high-level goals.
  • It should include critical elements like the Scope Overview, Business Case, Milestone Schedule, Acceptance Criteria, Risks, and sign-off commitments.