Organisation [Name]

Department [Name]

Simple Project Plan

<Project Name>

Date: <Date>
Doc. Version: <Version>
Template version: 3.0

Nota: No MEGSI existe uma unidade curricular designada por Gestão de Projetos de
Tecnologias e Sistemas de Informação, na qual é abordada a gestão de projetos de forma
aprofundada. Em DOTI apenas são considerados alguns aspetos fundamentais da gestão de
projetos.

This template is based on PM² V3.0

Document Control Information
Settings
Document Title:
Project Title:
Document Author:
Project Client:
Solution Provider
Project Manager:
Doc. Version:
Sensitivity:
Date:
Value
Simple Project PlanOpenPM² Methodology
<Project Name>
<Document Author>
<Project Client>
<Solution Provider (SP)>
<Project Manager (PM)>
<Version>
<Public, Limited, High>
<Date>

Document Approver(s) and Reviewer(s):

Name Role Action Date
<Approve / Review>

Changes to this document are summarized in the following table in reverse chronological order
(latest version first).
Revision Date Created by Short Description of Changes

<These notes should be deleted in the final version :>

Notes for Templates:

 Text in <orange>: has to be defined.
 Text in <blue>: guidelines and how to use the Template. Should be deleted in the final
version.
 Text in green: can be customised. Should be recolored to black in the final version.

Date: <Date> 2/8 Doc. Version: <Version>

TABLE OF CONTENTS
1 EXECUTIVE SUMMARY...................................................................................................................... 4
2 CONSIDERATIONS ON THE BUSINESS CASE........................................................................................4
3 PROJECT DESCRIPTION..................................................................................................................... 5
3.1 Scope..................................................................................................................................................5
3.2 Stakeholder and User Needs..............................................................................................................5
3.3 Deliverables........................................................................................................................................5
3.4 Constraints..........................................................................................................................................5
3.5 Assumptions.......................................................................................................................................5
3.6 Risks....................................................................................................................................................5
4 TIMING AND COST............................................................................................................................ 6
4.1 Timing and Milestones.......................................................................................................................6
4.2 Cost.....................................................................................................................................................6
5 APPROACH/METHODOLOGY............................................................................................................. 6
6 GOVERNANCE AND STAKEHOLDERS.................................................................................................. 7
6.1 Structure.............................................................................................................................................7
6.2 Roles and Responsibilities..................................................................................................................7
APPENDIX 1: REFERENCES AND RELATED DOCUMENTS...........................................................................8

Date: <Date> 3/8 Doc. Version: <Version>

1 EXECUTIVE SUMMARY
<This section should provide an executive summary. Complete this section last.>

<Este documento descreve os requisitos mínimos do plano do projeto que será necessário apresentar na
unidade curricular de DOTI, no ano letivo de 2022/2023. O plano de projeto deverá delimitar o projeto
principalmente no que respeita ao âmbito, tempo e custo. Outros aspetos relevantes para a gestão de
um projeto, como a qualidade, a comunicação, as contratações, entre outros, não serão considerados no
âmbito de DOTI.>

2 CONSIDERATIONS ON THE BUSINESS CASE

<This section should include any pertinent considerations to the Business Case of the project. Topics such
as the impact and urgency of the current situation described in the business case can be further
elaborated in this section if necessary.>

Date: <Date> 4/8 Doc. Version: <Version>

3 PROJECT DESCRIPTION
3.1 Scope
<This section should present an overall scope statement for the project in a few lines. It should be
complete enough for the management and outsiders to understand the scope of the project.>

3.2 Stakeholder and User Needs

<This section should list the key needs of the stakeholders and users that the project shall address.
Use the questions below to help you describe each need:
 Who is the stakeholder of this need?
 What is the need? What solutions does the stakeholder want?
 What are the reasons that justify addressing this need?
 How is it currently addressed?
It is also important to indicate the relative importance of each need (from the stakeholder/user
perspective).>

3.3 Deliverables
<This section should identify the deliverables or outputs of the project. Think of deliverables as a tangible
or intangible object produced as a result of the project that is intended to be delivered to the Project
Owner’s organisation. A deliverable could be an automated report, a document, a server, a new policy or
regulation, a conference, a training, a campaign, etc. A deliverable may be composed of multiple sub-
deliverables.>

3.4 Constraints
<This section should describe any project constraints that affect the way we can manage this project.
Constraints can come from areas such as the people that can be involved, schedule, budget, resources,
products to be reused or acquired, technology to be employed and interfaces to other products. List the
project constraints based on the current knowledge.>

3.5 Assumptions
<This section should describe any project assumptions related to business, technology, resources,
organisational environment, scope, expectations, or schedules. At this stage, assumptions are considered
to be facts (true); however they need to be further validated to ensure that they are indeed facts.>

3.6 Risks
<This section should highlight the key project risks that are identified at this initial stage and proposes
corresponding risk management strategies. >
ID Risk Description & Details Action
Likelihood1

Risk Level3

Details
Impact2

1
A numeric value denoting the relative probability that the risk should occur (e.g., 1 – low / 5 – high).
2
A numeric value denoting the relative severity of the impact of the risk if it should occur (e.g., 1 – low / 5 – high).
3
The risk level is the product of the likelihood and impact (RL=L*I).

Date: <Date> 5/8 Doc. Version: <Version>

4 TIMING AND COST
4.1 Timing and Milestones
<This section should list the important project points in time of the project lifecycle (i.e. milestones) for
events or project deliverables. The list can include an indication regarding the foreseen timing of the
major project phases, as well as both project and project management deliverables.>

Target Delivery
ID Milestone Description
Date

<Develop a Gantt chart with the project’s main activities and milestones.>

4.2 Cost
<This section should describe project's resources requirements. Summarise here the numbers, type and
cost of staff required, including any special skills or experience. Include all resources required to execute
the project in all user/stakeholder groups including resources required in other organisations and/or
external stakeholders (if any). Justify all the costs.>

I Cost
Resource Requirement Description
D

Total Budget:

5 APPROACH/METHODOLOGY
<This section should mention the chosen methodology that the project will follow.>
Date: <Date> 6/8 Doc. Version: <Version>
6 GOVERNANCE AND STAKEHOLDERS
6.1 Structure
<This section should describe the organisational structure of the project team and stakeholders,
preferably providing a graphical representation.>

6.2 Roles and Responsibilities

<This section should describe the Roles and Responsibilities of the team members.>

Date: <Date> 7/8 Doc. Version: <Version>

 APPENDIX 1: REFERENCES AND RELATED DOCUMENTS
<Use this section to reference (or append if needed in a separate annex) any relevant or additional
information. Specify each reference or related document by title, version (if applicable), date, and source
(e.g. the location of the document or the publishing organisation).>

ID Reference or Related Document Source or Link/Location

1 <Example of a related document> <Example of a location>
<02.Business_Case.XYZ.dd-mm- < U:\ PROJECTS\ProjectX \Documents\>
yyyy.V.1.0.docx>

2 Project folder <Insert project folder location.>

3 <Example of a reference> <Example of a source>

<"The Communication on Risk <20/10/2005, European Commission>
Management, SEC(2005)1327">

Date: <Date> 8/8 Doc. Version: <Version>