Professional Documents
Culture Documents
20220222-FH-project Management Basic Lecture - V4.0
20220222-FH-project Management Basic Lecture - V4.0
MANAGEMENT
BASICS
Version 4.0 – 02/2022
◈ This document was designed to support the Project Management lecture at the FH
Wels, and shall be the basis for the preparation to the level D certification from
PMA (Project Management Austria).
◈ The Project Management approach of this document is based upon PM- Baseline
(pma) as well as International Competence Baseline (IPMA) which can be found in
the up to date version on www.p-m-a.at.
◈ For clarity, project managers will always be referred to in the male gender but it is
clearly understood that the female gender would equally apply.
◈ This publication may only be used for personal usage. No part of this publication may be
reproduced in any form without written permission by the authors listed below.
0. Preamble
1. Terminology
2. Project start
3. Project coordination
4. Project controlling
5. Project closing
6. Literature
Preamble
Source: Studie GPM in Kooperation mit der EBS Universität für Wirtschaft und Recht (2015)
Project teamwork and project controlling as well as decisions do have the biggest impact on project
success or failure
If you consider the project critical constructive, what in your opinion are the main reasons, that the project
proceeded more or less successfully)*
Source: S. 134 „Evidenzbasierte Erfolgsfaktoren im Projektmanagement, BPM-Labor Hochschule Koblenz, Prof. Dr. Komus“ (2015)
Terminology
temporary
complex endeavour social system
organisation
considerable
own culture
target oriented
unique specific roles
own rules
limited
structural organisation
new
momentum
dynamic
responsibilities
unique
repetitiveness
recurring / repetitive
internal
Customer
external
Scope
Risk
v
Organisation
Resources/ Time
Costs
Organisation
Org-chart Communication R.A.C.I. Matrix
& roles & rules
Scope
Deliverable Work WP-
plan Breakdown Specification
Structure
Time
Milestone plan Gantt-chart
Resource/
Resource-plan
Cost Cost-plan Cash-Flow
Risk
Risk-analysis
Project coordination
Project marketing
Project closing
Project start Project controlling
Project start
◈ It is the aim of project start process to create a complete and integrated planning of
the project, and to finalise the project assignment including signatures
Develop
project organisation Risk analysis
2 5
3
1 4
Definition of project objectives
create project assignment
Project boundaries &
context analysis
Plan triple constraints;
scope, time, resource
and cost
◈ Project boundaries form the basis of the project assignment, and are defined in the dimensions time,
scope and social.
TIME
◈What is the scheduled start- and end-date of the project?
Project Management BASICS © VOON-Management GmbH Slide 20
◈Which events can be assigned to the start- and end-date?
SCOPE
◈What are the project objectives?
◈Which non-objectives do we have?
◈What has to be delivered at the end of the project?
◈Which main tasks / phases does the project consist of?
◈What is the project budget?
SOCIAL
◈Who is project sponsor ?
◈Who is project manager?
◈Which skills are needed in the project team?
Context analysis
◈ Goal of the context analysis is to make transparent the influence of external factors onto the
Project
◈ Context analysis is defined in the dimensions time, task and social.
TIME
Project Management BASICS © VOON-Management GmbH Slide 21
◈What happened before project start?/ Which documents are already existing?
◈How was this project initiated?
◈What is going to happen with the project results?
◈Which activities following the project could there be?
SCOPE
◈To whichsoever strategies and company objectives are there relations within the company?
◈Are there other projects which might contribute something to our project results?
SOCIAL
◈Are there stakeholders which do have an influence on the project success?
◈Who are the users/ persons affected of/by the project?
Time & Scope Context analysis
◈ The project stakeholder analysis is amongst others the basis for project marketing
and practicing crisis prevention
Project organisation
(internal environment)
It is distinguished between
Customer PS internal (persons within
PTM
(external environment) PW the project team)
Customer Project stakeholders and external
manager
PTM stakeholders!
Media Medien
(external environment) Project
CEO
Supplier XY Department A
Supplier
(external environment) Company internal
(external environment)
Develop
project organisation Risk analysis
2 5
3
1 4
Definition of project objectives
create project assignment
Project boundaries &
context analysis
Plan triple constraints;
scope, time, resource
and cost
Individual roles
Group roles
◈ Project sponsor (PS)
◈ Steering committee (PSC)
◈ Project manager (PM)
◈ Project team
◈ Project team member (PTM)
◈ Core team
◈ Project worker (PW)
◈ Sub teams
Project team
Project-
manager Project-
team member
Project-
team member
Core team
Project-
worker
PS GOALS
◈ Represent and promote company’s interests
◈ Initiating projects
◈ Leading the project manager
TASKS
At Project start
◈ Choose/select project manager
◈ Target agreement and signing of project assignment
◈ Ensuring provision of resources
At Project controlling
◈ Make strategic decisions
◈ Participate at project sponsor meetings
◈ Ensuring provision of resources
At Project closing
◈ Formal project acceptance
◈ Performance appraisal, feedback for project manager and project team
◈ Project evaluation
PM GOALS
◈ Responsibility to achieve project goals
◈ Leading the project team
◈ Design of PM-processes, creation of PM-documentation
TASKS
At Project start
◈ Know-How transfer from pre project phase
◈ Planning of project, design of project organisation, team building
◈ Agreement on project objectives, creation of project assignment
At Project controlling
◈ Analyse project status
◈ Agreement on controlling measures
◈ Create status report and adjust with project sponsor
At Project closing
◈ Planning of post project phase, allocation of remaining
◈ Create project close down report, emotional project close down
◈ Know-How transfer into permanent organisation
PTM GOALS
◈ Contribute to achieve project objectives
◈ Leading sub teams/ project workers
◈ Support as subject matter expert (SME)
TASKS
At Project start
◈ Collaboration in project planning
◈ Take over work package responsibility
At Project controlling
◈ Reporting to project manager
◈ Complete assigned work packages
At Project closing
◈ Collaboration in transferring know-how into the permanent organisation
◈ Feedback
◈ Project meetings are a management tool, by which information is exchanged, results are
aligned and decisions made
◈ The project culture can be defined as sum of values, norms and rules of a project
◈ Project specific values deliver a scale for, what is being seen as good, valuable and
desirable in the project
Topic Rules
Rules for
collaboration ◈
Agreed deadlines are always met
◈
Different working styles are treated with respect
◈
If conflicts should arise they are addressed openly and in a
factual manner
◈
Only aligned findings are communicated to the outside world
Rules for
meetings ◈
We participate regularly and on time at project meetings
◈
All participants are prepared for project meetings
◈
Agenda und goals are distributed at least 1 day in advance
◈
Attendees are authorised to make decisions
Rules for
documentation ◈
All project relevant documents are stored in the project folder and
regularly updated
Project Management BASICS © VOON-Management GmbH Slide 37
Procedure within Project start
Develop
project organisation Risk analysis
2 5
3
1 4
Definition of project objectives
create project assignment
Project boundaries &
context analysis
Plan triple constraints;
scope, time, resource
and cost
S M A R T
◈ Written agreement between project sponsor and project manager, and should
therefore be signed by both parties
Develop
project organisation Risk analysis
2 5
3
1 4
Definition of project objectives
create project assignment
Project boundaries &
context analysis
Plan triple constraints;
scope, time, resource
and cost
Scope
◈ The deliverable plan can be used as basis for creating the work breakdown structure
◈ Forms of presentation:
◈ Mind map
◈ List
◈ Object structure plan
◈ Basis for target agreements (work packages) between project manager and team
members
1
Project
0
PROJECT -
- - - -
MANAGEMENT PHASE 2 PHASE 3 PHASE 4 PHASE 5
1
1
1
0
0
- - - -
-
WP-Name WP-Name WP-Name WP-Name
1.
1.
1.
1.
1.1.1
Project started
0
(MST 1)
0%
- - - -
Project -
1.
WP-Name
1.
1.
1.
1.
0
0
0
-
Project - - -
-
1.
1.
1.
controlling WP-Name WP-Name WP-Name MST 6
1.
1.
0
0
- -
- - WP-Name
1.
Project
1.
1.
1.
MS WP-Name
0
0
0
coordinat
0
ion T2
Process orientation
- -
Project -
1.
MST 4 MST 5
1.
1.
marketing
0
0
-
1.
Project
0
close
down
-
1.1.7
Project finished
0%
(MST 7)
Project content
P activities
Project Management BASICS © VOON-Management GmbH Slide 46
Extended view
WBS
green
WP-Name progress
green/ yellow/ red
1.2.
WBS-Code
WP-responsible
2
WP progess
0%
Allocation of tasks
In steps of 25%
(0/ 25/ 50/ 75/ 100)
Start End
start and end date
for each work
package
Project Management BASICS © VOON-Management GmbH Slide 47
WP specification
◈ Are used for target agreements between project manager and work
package responsible
◈ The project responsibility assignment matrix is based upon the work breakdown
structure and project organisation and is represented in a matrix
◈ Definition:
◈ Cooperation („C“)
Project assistant
Project manager
Project worker 1
Project worker 2
Project worker 3
External client
Project owner
Project coach
WBS-
Code
WP-Title
1.1 Projektmanagement
1.1.1 Project started R … Responsible A … Accountable C … Contrib
1.1.2 Project planning I A R C C C C C C I I I C I … to be informed
1.1.3 Project controlling I I R C C C C C C I I I C
1.1.4 Project coorrdination R C C C C C
1.1.5 Project marketing R C C C C C
1.1.6 Project close down I A R C C C C C C I I I
1.1.7 Project finished
1.2 Phase 2
1.2.1 WP-Name R C
1.2.2 WP-Name R
1.2.3 WP-Name I I C R C
1.2.4 MST 2
1.3 Phase 3
1.3.1 WP-Name R C C
1.3.2 MST 3
1.3.3 WP-Name R C
1.3.4 WP-Name R C C
1.3.5 MST 4
Milestone plan
◈ Milestones split the project into smaller and manageable stages and sub- ordinate
objectives
◈ Milestone planning is base upon the work breakdown structure and is visualised in
tabular representation
MILESTONE PLAN
WBS-
Milestone Baseline date Forecast date Actual date
code
1.1.1 Project started Milestones in order of
1.2.4 MST 2
plan dates not in order of
1.3.2 MST 3
the WBS-code
1.3.5 MST 4
1.4.5 MST 5
1.5.3 MST 6
1.1.7 Project finished
2016
WBS Milestone JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
1.2.5 MST 1
1.3.6 MST 2
1.4.3 MST 3
2016
WBS-
NAME START ENDE
JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
code
1.
project
1.1
project management
1.1.1
project started
1.1.2
project start
1.1.3
project controlling
1.1.4
project coordination
1.1.5
project marketing
1.1.6
project closing
1.1.7
project closed
1.2
trial planing
1.4
completion
1.4.1
create analysis
1.4.2
compare analysis to literature
1.4.3
present documentation/ reports
1.4.4
result reached
◈ The objective of resource planning is to determine and display the required project
resources over time.
◈ Subject matters in resource planning are work packages or phases from the work
breakdown structure (dependent od planning granularity).
Programmer
Tester
Quality assurance
Design
SUM
◈ Subject matters in cost planning are work packages or phases from the work
breakdown structure (dependent od planning granularity).
◈ Types of costs can be differentiated according to functional criteria, such as
personnel costs, material costs, equipment costs, administrative and sales costs,
costs for minimising risks, according to cost centres as direct and
indirect costs, and according to activity, as fixed or variable costs
Personnel cost
Material costs
Contracted service
Other costs
SUM
◈ Planning the costs per phase or work package and the total costs of the project
Develop
project organisation Risk analysis
2 5
3
1 4
Definition of project objectives
create project assignment
Project boundaries &
context analysis
Plan triple constraints;
scope, time, resource
and cost
◈ Project risks are events or developments, which might influence scope (quality),
schedule, cost or return of a project.
◈ Risk management in projects is a project management task, the responsibility rests
with the project manger.
◈ Risk analysis is defined as the likelihood of events occurring together with the
impact of these on the project.
◈ Evaluation of risks is done by comparing the risks analysed (risk expected value)
with the tolerable project risk.
Project coordination
◈ Project coordination begins with the assignment of the project and ends with approval of
the project, and is a continuous process.
Project controlling
◈ The objectives of project controlling are to analyse the project status, and agree on
and/or undertake control measures
◈ The project controlling process takes place on specific key dates several times
during a project. Project controlling begins with its initiation and ends when a
project progress report has been filed.
Social
project controlling
Creation of
status report
2
4
1 3
Collect
actuals
Controlling of scope,
schedule, resource and
costs, risks and project
environment
Social
project controlling
Creation of
status report
2
4
1 3
Collect
actuals
Controlling of scope,
schedule, resource and
costs, risks and project
environment
◈ Methods: Flash light, mood barometer, one point or multi point voting, discussions
Project organisation
(internal environment)
Customer PS PTM
(external environment) PW
Customer Project
manager PTM
CEO
Supplier XY Department A
Social
project controlling
Creation of
status report
2
4
1 3
Collect
actuals
Controlling of scope,
schedule, resource and
costs, risks and project
environment
Scope
1.
project
1.1
project management
1.1.1
project started
1.1.2
project start
1.1.3
project controlling
1.1.4
project coordination
1.1.5
project marketing
1.1.6
project closing
1.1.7
project closed
1.2
trial planing
1.2.1
define trial
1.2.2
choose sample
1.2.3
creat test series plan
1.2.4
research literature
1.2.5
plan closed
1.3
execution
1.3.1
prepare samples
1.3.2
nitride and coating
1.3.3
preparation of trial finished
1.3.4
execute test
1.3.5
tests finished
1.4
completion
1.4.1
create analysis
1.4.2
compare analysis to literature
1.4.3
present documentation/ reports
1.4.4
result reached
DE- VIATION
REMAIN
FORE-
BASE CAST
ACTUAL
Social
project controlling
Creation of
status report
2
4
1 3
Collect
actuals
Controlling of scope,
schedule, resource and
costs, risks and project
environment
◈ The project progress report is the formal result of the project controlling process
◈ Project progress reports describe the respective status of the project as well as the
planned controlling measures
Project closing
◈ Of which items does the project close down report consist of?
Literature
DOWNLOAD
-Management GmbH
VOLITION the process of building, maintaining and realising intentions Motivated
& with willpower to success
Start End
Project -
1
Project manager
0%
Start End
-
- MST 2
- - -
Project- PHASE I PHAS 2 PHASE 4
1
MANAGEMENT
1.2
E
1.
1.3
1
0
Start End
0%
0%
Start End Start End End Start End
Start
Project
controlling -- WP-Name - WP-Name - WP-Name - WP-Name -
Project started
1.1.3
1.1.1
WP-responsible WP-responsible
1.3.
WP-responsible WP-responsible
1.4.
1.5.
1.2
WP-responsible
1
0%
1
0%
0%
0%
0%
0%
Start
Start End
End Start End Start End Start End Start End
Projec close -
- MST 1
t Projectn WP-Name - WP-Name - WP -Name -
planning -
dow
1.5.2
1.
onsible
1.1.2
WP-responsible
1.2.
WP-responsible
1.4.
WP-res ponsible
0
WP-responsible Start End
2
2
WP-resp 0%
0%
0%
MST 3MST 4
inished WP-Name - WP-Name - WP-Name -
1.4. 1.
1.
Project f
0
0
WP-responsible WP-responsible WP-responsible
1.2.
1.3.
Start End Start End
3
3
0%
0%
0%
End
Start End Start End Start End
WP-Name - WP-Name -
1.
WP-responsible
1.3.
WP-responsible
1.4.
0
4
0%
0%
0
2016
lestone JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV
oject startet
ST 1
ST 2
ST 3
oject finished
2016
NAME STAR ENDE JA FEB MAR APR MA JUN JUL AUG SE OCT N
N Y P
T
work package
05.01.16 01.03.16
1
work package 2
01.03.16 30.06.16
work package 3
30.06.16 29.09.16
work package
30.06.16 30.11.16
4
milestone 30.11.16
Project Management BASICS