The primary objective of your Portfolio Project is to familiarize you with proje

Question

The primary objective of your Portfolio Project is to familiarize you with project management skills relevant to the process groups of planning, execution, monitoring and control, and closing. In Week 8 you will finalize a portfolio of documents representing your understanding of core components and competencies of IT project management, including project charter, project scope statement, work breakdown structure, change management processes, communication management, quality management, and project closure plan.

You may choose a real project in your current organization, in another organization, the case study provided in the text (described below),

The following components are required for your final submission:

Project Charter

Project Scope Management Plan

Work Breakdown Structure (WBS)

Communication Management Plan

Project Risk and Change Management

Quality Management Plan

Project Closure Plan

Additionally, craft an executive summary and a conclusion. The executive summary must offer a high-level description of the project you have developed throughout the course. The conclusion should focus on your self-assessment as a project manager assigned to an IT project. Address the key elements you identified in the previous modules and identify additional areas that you think would be beneficial to the success of your project.

Your total project should be 8-12 pages including title and reference pages

Explanation / Answer

Project Initiation
Purpose

The purpose of Project Initiation is to evaluate proposed projects and to reach a consensus on the projects to be selected. During Project Initiation, the Project Charter is presented, and the strength of a project’s Business Case and the viability of the proposed solution are evaluated. A determination is made as to whether the project is consistent with the institution’s business and/or strategic plan, and if the Project Planning (High Level) budget is affordable.

The Project Charter process may actually be part of the budget cycle, serving as the justification for budget requests. In this case, Project Charters may need to be created a full budget cycle prior to the project’s anticipated initiation.
The purpose of Project Planning (High Level) is to begin to define the overall parameters of a project and to establish the appropriate project management and quality environment required to complete the project. The major deliverable for this process is the Project Initiation Plan.

Development of the Project Initiation Plan is a pivotal starting point for the project that will serve as the foundation for all future efforts. The completion of this process is marked by the sign off and approval of the Project Initiation Plan.

Successful projects begin with a detailed project definition that is understood and accepted by Stakeholders. Putting everything down in writing helps ensure a commitment among Project Team members and between the team and the Stakeholders. As part of Project Planning (High Level), a Project Initiation Plan is developed which is comprised of the business case (refined from the Charter), overall goal, specific objectives, success criteria, scope, high level schedule, stakeholder accountabilities, the communication plan, benefits and costs, governance and resourcing, the management approaches and a high level risk plan These documents, once approved, ensure a consistent understanding of the project, help to set expectations, and identify resources necessary to move the project to the next level of detailed planning. Potential problems are identified so that they can be addressed early in the project.
List of Processes

The three major processes in Project Initiation are:

    Develop Project Charter, where the initial business case is made; where the Proposed Solution is described, along with alternatives considered; and where the budget and resources are identified for the Project Planning (High Level)

    Evaluate Project Charter, where the business case and proposed solution are evaluated for moving to Project Planning (High Level)

    Select Project Charter, where a consensus is reached on the project’s feasibility and relative importance in comparison to other proposed projects, and a decision is formally made regarding the Project Charter

The following roles are involved in carrying out the processes of Project Initiation. Detailed descriptions of these roles can be found in the Project Roles & Responsibilities section.

    Project Sponsor or Project Director

    Charter Team

    Project Selection Committee

Tasks Associated with Developing the Project Charter

    1.1.1 Develop Business Case
    1.1.2 Develop Proposed Solution
    1.1.3 Describe Alternatives Considered
    1.1.4 Develop Budget and Resources for Project Planning (High Level)
    1.1.5 Develop Project Governance

Deliverables

    Project Initiation Plan (PIP) – the key deliverable produced during Project Planning (High Level). The initial plan will be refined during Project Planning (Detail Level) and iteratively throughout the entire project management lifecycle and will serve as the main guide to follow during Project Execution and Control. The Project Initiation Plan incorporates the deliverables described in each Task of this section: the refined business case (refined from the Charter), overall goal, specific objectives, success criteria, scope definition, high level schedule, stakeholder accountabilities, a communication plan, benefits and costs, governance and resourcing, the management approaches and a high level risk plan.

The Project Initiation Plan is used to:

    Provide a foundation for the projects with the overall scope and objectives

    Present a preliminary budget for the Project

    Gain confidence of the funding source to be able to proceed to Detail Planning

    Guide Project Planning (Detail Level)

    Document project planning (High level) assumptions

    Facilitate communication among internal and external Stakeholders and understand accountabilities

    Define key management reviews as to content, extent and timing

    Approved or Rejected PIP or a Request for Additional Information – The PIP is signed by the appropriate authorized people, indicating one of the three possible outcomes:

        PIP approval to proceed to Project Planning (Detail Level) and Project Execution and Control.

        Request for additional information, or

        The PIP is rejected and a decision is made to halt the project.

Related Questions

Navigate

• Browse (All)
• Browse T
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.