{"id":2339,"date":"2023-02-27T01:52:44","date_gmt":"2023-02-27T01:52:44","guid":{"rendered":"https:\/\/course.oeru.org\/ipm102\/?page_id=2339"},"modified":"2023-02-27T01:52:44","modified_gmt":"2023-02-27T01:52:44","slug":"tasks-project-charter-challenge","status":"publish","type":"page","link":"https:\/\/course.oeru.org\/ipm102\/learning-pathways\/project-charter\/tasks-project-charter-challenge\/","title":{"rendered":"Tasks – Project charter challenge"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n

In this activity, you will write a project charter for your own project.\n<\/p>\n

The charter can include any of the elements that have been described in the resources in this learning path, but the essential elements are:\n<\/p>\n

    \n
  1. Identification Section\n<\/li>\n
  2. Objectives\n<\/li>\n
  3. Scope\n<\/li>\n
  4. Constraints\n<\/li>\n
  5. Major Milestones and Preliminary Cost for the Project\n<\/li>\n
  6. Project Stakeholders\n<\/li>\n
  7. Project Charter Acceptance\n<\/li>\n<\/ol>\n

    When you have completed your scope statement use the criteria in the rubric below to self assess it. This is also the rubric that will be used should you choose to be formally assessed.\n<\/p>\n

    Based on the rubric what elements of your project charter will create problems when implementing your project? Add a short description of what you anticipate to your learning journal.\n<\/p>\n

    \n<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Criteria\n<\/th>\nMark\n<\/th>\n<\/tr>\n
    Identification Section<\/b>\n<\/td>\n<\/tr>\n
    Lists the project name, the date of the current version of the project charter, the sponsor\u2019s name and authority, and the project manager\u2019s name\n<\/td>\n2\n<\/td>\n<\/tr>\n
    The project is named, as are the sponsor and project manager.
    The purpose or problem statement described.\n<\/td>\n    		1\n<\/td>\n<\/tr>\n
    Objectives<\/b>\n<\/td>\n<\/tr>\n
    All objectives are specific, measurable and time bound.
    The deliverables are described with specific requirements stipulated.\n<\/td>\n    		4-5\n<\/td>\n<\/tr>\n
    Most objectives are specific, measurable and time bound.
    The deliverables are described with some requirements stipulated.\n<\/td>\n    		2-3\n<\/td>\n<\/tr>\n
    Objectives may not be sufficiently specific, measurable or time bound to measure as success factors.
    The deliverables are described but may not have requirements stipulated.\n<\/td>\n    		0-1\n<\/td>\n<\/tr>\n
    Scope<\/b>\n<\/td>\n<\/tr>\n
    The scope statement describes at least 3 requirements which may include business requirements, technical requirements, user requirements or regulatory requirements.
    These requirements are written to a level of detail which will clearly identify what is in or out of scope.\n<\/td>\n    		4-5\n<\/td>\n<\/tr>\n
    The scope statement describes at least 3 requirements which may include business requirements, technical requirements, user requirements or regulatory requirements.
    These requirements are described but will require extensive clarification to define what is in or out of scope.\n<\/td>\n    		2-3\n<\/td>\n<\/tr>\n
    The scope statement describes less than 3 requirements which may include business requirements, technical requirements, user requirements or regulatory requirements.
    These requirements lack the detail to guide what is in or out of scope\n<\/td>\n    		0-1\n<\/td>\n<\/tr>\n
    Constraints<\/b>\n<\/td>\n<\/tr>\n
    At least 3 constraints which apply to this project are described. These may include cost, quality, or time. The constraints are described in enough detail for the project manager to know where the quality, cost and time limits are.\n<\/td>\n 4-5\n<\/td>\n<\/tr>\n
    At least 3 constraints which apply to this project are described. These may include cost, quality, or time. There is little description to clarify what the limitations of the project are.\n<\/td>\n2-3\n<\/td>\n<\/tr>\n
    There are less than 3 constraints described and they lack the detail to guide project management decisions.\n<\/td>\n0-1\n<\/td>\n<\/tr>\n
    Major Milestones and Preliminary Cost for the Project<\/b>\n<\/td>\n<\/tr>\n
    At least 3 significant milestones are described on a time line and an approximate budget provided.\n<\/td>\n4-5\n<\/td>\n<\/tr>\n
    At least 3 significant milestones are described.
    There is some indication of total cost.\n<\/td>\n    		2-3\n<\/td>\n<\/tr>\n
    Less than 3 milestones are described.
    There is no indication of total cost.\n<\/td>\n    		0-1\n<\/td>\n<\/tr>\n
    Stakeholders<\/b>\n<\/td>\n<\/tr>\n
    At least 3 relevant stakeholders are listed. Their level of power and interest are clearly described.
    Realistic and comprehensive description of effect on stakeholder and effect on project is provided for all stakeholders.\n<\/td>\n    		4-5\n<\/td>\n<\/tr>\n
    At least 3 relevant stakeholders are listed. There is some description of how significant they are to the project.
    Realistic and comprehensive description of effect on stakeholder and effect on project is provided for most stakeholders.\n<\/td>\n    		2-3\n<\/td>\n<\/tr>\n
    There are less than 3 stakeholder or some listed may not be relevant to the project. This is little indication of how significant they are to the project.\n<\/td>\n0-1\n<\/td>\n<\/tr>\n
    Project Charter Acceptance<\/b>\n<\/td>\n<\/tr>\n
    There is a section which includes the name, role and signature of the project sponsor.\n<\/td>\n0-1\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    <\/p>\n

    \n<\/div>\n

    <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n<\/div>\n<\/div>\n
    \n
    \n