READ ME

Schedule with hours and resources

• Hi!
The Schedule is divided in two pieces (planning and execution)

Please go to execution part (second one in Green color) and check wich activity you have been assigned
to perform, next to that you can find the dates that activity has be be complete in order for the next
one to start (if you believe that activity IS NOT NEEDED we can always make change like remove old
ones and add new ones)

The wbs is divided according to the document “making a rubrick” which you can find in the “Planning
folder” and also on this presentation.

The resources are divided that way so everyone can be involve and learn about all subject and also
after the completion of the wbs the team Will have a meeting about it so everyone can be on the same
page (minutes applicable)
Please check on the final dates!! Any questions or comments please let me know
As you can see the documentation on the drive is
divided in to X folders:
Please save the document that you
Are working on were it belongs!
• 1. Stakeholders involvement and Management (according to make a rubrik doc)
• 2. Project Definition The idea is create a final document from
• 3. Product and Activity Development All the final documents from each folder

• 4. Risk Management I need that if you find more

Subactivities from the one your working
• 5. Estimates and Resources Allocation On to Document it so I can update the
• 6. Schedule and Budget Schedule adding them

• 7. Project Control Thanks!

• Documental Control
• Planning
1. Stakeholders involvement and Management
This folder/final document will cover the following
topics:
All key and secondary stakeholders are
Stakeholders Identified *
identified
Stakeholders!!
Stakeholder Mapping is systematic and used to
Stakeholders mapped build & develop knowledge about stakeholders
and their requirements.

Requirements are systematically[i] identified

Stakeholder requirements identified *
for all stakeholders
Requirements mapping is systematic using
Stakeholder requirements mapped
appropriate methods.

Identifies patterns in s/h requirement map to

inform assessment using a range of
Stakeholder requirements assessed
appropriate methods that inform & organise
s/h requirements into project requirements.

S/h communications link with the project

schedule and decision making as well as using
Stakeholder (s/h) communications planned an appropriate range of communications
methods to provide a clear plan of
involvement.
2. Project Definition
Please document this on the accurate folder
The project type is identified correctly and used to Type of Project
Project Type & Management Approach develop an appropriate and systematic management
approach for the project.

Presentation of objectives shows auditable links with

Project objectives
s/h requirements through mapping & assessment. Objectives

Clear Measures
Measures align with or are integrated with objectives
& identify comprehensive evidence that objectives
Measures
have been achieved.

A comprehensive list of accurate constraints is

Project Constraints identified
identified, is auditable and links to s/h requirements.
Constrain
Presentation of assumptions demonstrates
Assumptions identified application of a systematic approach that links to assumptions
project needs and incorporates stakeholder review.
 3. Product and Activity Development
Please document this where it belongs
Identified products are auditable and aligned with
products defined*
project objectives
Our product

WBS development has identified activities through

processes / activities identified* systematically defining all the work needed to complete
the project. Reseach method

The network is part of a systematic development that ?

Accessible Network chart* demonstrates completeness, alignment with the activity
list and a suitable workflow through the project.

WBS aligns with PBS and is developed to identify

processes required to complete the products. The level
Structure of WBS
of breakdown is developed as part of a systematic Wbs
process.

Resources are allocated to all activities. Roles and

Resource allocation with clear accountability accountabilities have been allocated with consideration Resource allocation
of skills and development needed.
4. Risk Management
External factors have been considered as part of a systematic Scan risk involve
Environment scanning
review to identify a range of risk sources.

All main* risks are identified as part of a systematic, multi-pass

Risk identification* and auditable process that identifies risks at all levels and from Identify them
all sources.

Identified risks are described to show that risk definition is part

Risk definition*
of a systematic, multi-pass and auditable process. Definy them

Identified risks are assessed as part of a systematic process that

Qualitative risk analysis
informs risk prioritisation, response and management.
Numbers

The response to risks is developed as part of a systematic

Risk response* process that identifies mitigation and contingency plans, risk
owners and timescales that are built into the broader plan.

Management actions provide a systematic process that

Risk management demonstrates control and management of risks throughout the
project. Risk review includes capture of lessons learnt.
5. Estimates and Resources Allocation
Estimates are developed as part of a systematic process that
Estimates* considers the level of associated risk and resource
allocation.

Time estimates systematically develop estimates for both

estimates time*
duration of work and elapsed time.

Cost estimates are systematically developed with

estimates cost* consideration of cost components and associated value of
work
 6. Schedule and Budget
The project schedule is developed as part of a systematic
Clear Gantt chart for the project
process that aligns activity planning with project review.

The s-curve is accurate and is developed as part of a

S curve for the cost systematic process that informs plan development and
management.

Resource profile systematically allocates all identified

resource profile for the team
activities, considering team roles and development needs.

Rolling wave planning is appropriate for this project and has

Rolling wave approach (if appropriate for the project*) been applied as part of a systematic and integrated
approach.
7. Project Control
The progress monitoring method is part of a systematic review process that identifies and uses collected data to
Progress monitoring*
inform management decisions and actions, and identifies lessons learnt.

The change process is systematic and embedded into and integrated with the project quality planning and control
Change and Configuration Management
process.

There is a systematic method of project review and reporting that informs stakeholders, aligns with project
Project Governance (review and reporting)
requirements and activity plans

The data assessment process systematically assesses data and presents information for project review and decision
Data assessment and presentation
making. The process informs lessons learnt and draws from lessons learnt in other projects.

The approach to the project is “get it right first time”. Quality management is part of a systematic process designed to
Quality planning & assurance
prevent rework and test that work aligns with project objectives

Project-related decisions are planned through systematic consideration of stakeholders, team roles, project activities
Planning for Decision making
and schedule.

Transition of the project to the client Handover to the client is part of a systematic approach to project closeout that is consistent with requirements.

There is a systematic lessons learnt capture and dissemination process that contributes to audited continuous
Lessons learnt
development.
Documental Control

• Design Changes documented

• Minutes (agreements, achievements)
• Activity LOG (lessons learnt)
• VIVA PRESENTATION (9 nov)
• FINAL PRESENTATION (12 dec)
• And more….
Planning
• Stuffs like this

• GUIDELINES