• English
    • Deutsch (German)
  • Login
CPCCPCCPCCPC
  • Idea into project
  • Initiation
  • Planning
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
  • Execution
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
  • Controlling
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
    • Project Controlling
  • Closure
  • Agile
    • Scrum-Rollenmodell
    • User Stories
    • Daily Scrum
    • Quality Gates agile Methodik
  • Program Management
    • Relationship Program & Project Mgmt.
    • Program Mgmt. Process
    • Key Components
    • Do´s & Don´ts
    • Best Practices
    • Certification Possibilities
    • Further Links and Literature
  • FAQs
  • Forum
  • Login

Initiation

Within the framework of the Initiation Process the feasibility of a project is analyzed, strictly before any significant effort goes into planning or executing the project.

Input

  • External objects: Underlying information about project scope and project stakeholder’s expectations

Process Steps

1. Collecting of information – also from the pre-project phase, when it’s available

The aim of this step is to establish a reliable basis of information, for all subsequent activities. Information about predefined project constraints (time limit, budget, scope…) should be analyzed likewise.

2. Formulating and validating the project description

To achieve clear project results, a project description is necessary. For this it is important to formulate statements describing why the project is required.

3. Categorizing the project

The project category is determined using a tool. On this basis the general framework, as well as the scope and course of the project management (i.e. minimum requirements), is determined.

4. Generating the project charter

The project charter ensures that all stakeholders gain insight into the project. For this, the project outcomes and expectations are documented and the project costs are roughly determined. The costs should be roughly determined according to the predefined project scope, the timeline and estimations about required resources.

5. Submitting the project charter

The project charter forms the initial planning document which is valid once approved by all key stakeholders. Also, the project charter serves as input document for the project plan and is subsequently replaced by the project plan.

6. Executing quality gate initiation

By executing quality gate initiation it is ensured that all information included in the project charter  is reviewed in terms of completeness, consistency and contribution to the overall understanding of the project. The information included in the project charter also needs to provide an understanding of the project complexities/challenges before moving on to the next steps.

Output

Project Categorization:

  • The project category is determined according to the criteria built into the project categorization tool (e.g. size, duration, cost, significance, background…).
  • It defines minimum requirements for the project management approach.
  • The minimum requirements derived from the project category indicate the correct measure of intensity project management, according to which the project should be conducted.

Project Charter:

  • Ensures all stakeholders gain insight into the project.
  • Documents business requirements and business objectives aims, high-level cost estimate / business case, key deliverables, restrictions, assumptions and dependencies as well as timeline, project organization and project risks.
  • Forms the initial planning document, valid upon approval by all key stakeholders.
  • Serves as input document for the project plan and is subsequently replaced by the project plan.

Why is it useful to execute the initiation process?

Project initiation describes a process to orderly propose and to initially analyze, validate, plan, review and approve/reject a project subsequently. The initiation process thus is aiming at only starting projects that are needed and aligned to the overall corporate strategy. Also the initiation process verifies if the project is realistically planned, if there are sufficient resources allocated to the project and if the project is committed to by participating organizations. Orderly carrying out the initiation process will increase the probability of the successful completion of a project.

Deliverables and Project Procedure

Deliverables:

  • Deliverables are physical objects or measurable outputs of project activities.
  • They include preliminary results of products or services that are necessary to achieve the final project objective.
  • They are always measurable since they can be counted, or monitored in some way.
  • Please note: deliverables may be hardware, software, services, processes, documents or any combination thereof.

Project Procedure:

  • The project procedure is the “strategy”, by which the final project objective is achieved.

General Project Procedure

Tips & Tricks – Initiation

Make sure that the project charter includes all necessary information (objectives, prime benefits, project procedure etc.)

Including the project team and the steering committee in scoping and planning, validates assumptions, creates a sense of security and establishes a common understanding.

Prototypes, models and simulations make scope and project objectives tangible and have a big impact on the success of the project.

The project charter is the basis for the work breakdown structure. You should therefore be careful to include a clear and intelligible definition of the deliverables.

You should document assumptions and dependencies as well as relevant topics that are outside of the project scope.

Overview Templates

Project Categorization
Project Charter

Overview Templates

Project Categorization
Project Charter
  • Dashboard
  • Idea into Project
  • Initiation
  • Planning
  • Execution
  • Controlling
  • Program Management
  • Closure
  • Agile
  • FAQs
  • Forum
Copyright 2019 CPC | All Rights Reserved
  • Idea into project
  • Initiation
  • Planning
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
  • Execution
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
  • Controlling
    • Integration
    • Scope
    • Time
    • Human Resource
    • Supplier
    • Cost
    • Risk
    • Quality
    • Stakeholder
    • Communication
    • Project Controlling
  • Closure
  • Agile
    • Scrum-Rollenmodell
    • User Stories
    • Daily Scrum
    • Quality Gates agile Methodik
  • Program Management
    • Relationship Program & Project Mgmt.
    • Program Mgmt. Process
    • Key Components
    • Do´s & Don´ts
    • Best Practices
    • Certification Possibilities
    • Further Links and Literature
  • FAQs
  • Forum
  • Login
  • English
    • Deutsch (German)
CPC