4 Factors Affecting The Development of the Project Charter

March 29, 2009 | Author: PM Hut | Filed under: Project Plan Development

4 Factors Affecting The Development of the Project Charter
By Siraj Qureshi

There are 4 factors which could have substantial impact on the development of Project charter which are as follows:

  1. Contract: A contract from the customer’s acquiring organization is an input if the project is being done for an external customer.
  2. Project Statement of Work: The SOW is a narrative description of the products or services to be supplied by the project. For internal projects, The Project Initiator or the Project Sponsor provides the SOW based on business needs, product/service requirements. For external projects, the SOW can be received from the customer as part of a bid document, for example: request for proposal, request for information, request for bid, or as part of a contract. The SOW may include the business need(s), the product scope description, and the strategic planning.

  3. Enterprise Environmental Factors ( EEF): When developing the project charter, all of the organization’s enterprise environmental factors and systems that surround and influence the project’s success must be considered. The EEF may include the following items: organization culture and structure, infrastructure, human resource, PMIS, personal administration, industry standards…

  4. Organizational Process Assets ( OPA): When developing the project charter and subsequent project documentation, all of the assets that are used to influence the project’s success can be drawn from the organizational process assets. The organizational process assets can be organized differently, depending on the type of industry, organization, and the application area. For example, the organizational process assets could be grouped into the following 2 categories:

    • The organization’s process and procedures for conducting work. For example: the organization policies, standards, standardized guidelines, templates, project closure guidelines, change and risk control procedure etc…
    • The organization corporate knowledge base for storing and retrieving information. For example: project files, historical information, configuration and change management knowledge base, issue and defect management database, change control, issue and defect resolution and action items results, documentation from previous project…

Siraj is a Senior Consultant working with a reputable in the US. He has managed several IT projects for CMM level 5 organizations. Also, he is an MCP and has expertise in .Net technologies and he has around 12 years of software management and development experience. He is passionate about learning new and emerging technologies. His main interests are SDLC, .Net Framework, ASP.NET, AJAX, WCP, WPF, Web development, Application designing, Code generation, Performance tuning etc. If you have any suggestion or you want to share something, please drop in your comments or you can reach him at siraj9786@gmail.com. Your suggestions will be appreciated.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

Related Articles

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories