Project Management Lec 1
Project Management Lec 1
What is a project?
⚫ “Series of actions to achieve a result”
Project management: History
⚫ Already the Egyptians… (Crucifixion raids or east India trips
were organized as projects, but without any management
philosophy)
⚫ 1911 Taylorism/Scientific Management: Henry LGantt invents
the Gantt scheme
⚫ 1931: Karol Adamiecki creates the first network diagram, the
so called Harmonogram
⚫ 1942-45: The Manhattan project (USA). 2 billion dollar
turnover, at most 120.000 employees. Goal control, parallel
activities
⚫ 1950ies: Operations analysis, RAND Corporation
⚫ 1957: The Sputnik chock, initiating the Polaris project
Project: Definition
⚫ ”Series of actions to achieve a result”
⚫ Single occurrence – a unique, non-repetitive assignment
⚫ Time limitations – with a pre-defined date of delivery
⚫ Clear purpose – specified from one or more goals (well
defined, measurable and realistic), do not mix project goals and
effect goals
⚫ Unpredictable structure – it consists of a number of complex
activities with mutual interdependencies
⚫ Own organisation – e.g. Not in the original line of work
⚫ Procurer – internal or external acquirer that has expectations
on the result
What is a project plan?
⚫ The aim of a project plan is to go through, document and
agree upon important issues that define the work in the
project.
Project organization
Project Management: concepts
⚫ System theory
⚫ Project triangle
⚫ Work Breakdown Structure (WBS)
⚫ Gantt-scheme
How do you calculate time?
⚫ Have a good guess?
⚫ Calculate?
⚫ Guess at minimum
(A),probably(B) and maximum
(C)
⚫ Calculate
⚫ (A + 3B + C)/5
Information and communication
⚫ Common problem in projects
⚫ Lack of communication and structure is often a problem
in projects
⚫ Difficulty in involving the project members, the customer,
the procurer and other stakeholders.
Meeting and meeting techniques
⚫ To succeed it is necessary to have a goal with the meeting
and an agenda.
⚫ Meeting are necessary, but need to be efficient. A good
way of organising is an agenda.
Different meetings
⚫ Steer group meetings
⚫ At milestones or when needed
⚫ Protocol written by PM
⚫ Project Management Meetings
⚫ Every Friday
⚫ Protocol written by PM
⚫ Project Meetings
⚫ Every second Monday
⚫ Protocol written by PM.
Project risks
⚫ The only thing we truly know about the future is that we
do not know anything about it.
Risk management
⚫ Risk management is concerned with identifying risks and
drawing up plans to minimise their effect on a project.
⚫ A risk is a probability that some adverse circumstance will
occur
⚫ Project risks affect schedule or resources;
⚫ Product risks affect the quality or performance of the
software being developed;
⚫ Business risks affect the organisation developing or
procuring the software.
The risk management process
⚫ Risk identification
⚫ Identify project, product and business risks;
⚫ Risk analysis
⚫ Assess the likelihood and consequences of these risks;
⚫ Risk planning
⚫ Draw up plans to avoid or minimise the effects of the risk;
⚫ Risk monitoring
⚫ Monitor the risks throughout the project;
The risk management process
Risk identification
⚫ Technology risks.
⚫ People risks.
⚫ Organisational risks.
⚫ Requirements risks.
⚫ Estimation risks.
Risks and risk types
Risk analysis
⚫ Assess probability and seriousness of each risk.
⚫ Probability may be very low, low, moderate, high or very
high.
⚫ Risk effects might be catastrophic, serious, tolerable or
insignificant.
Risk analysis (i)
Risk analysis (ii)
Risk planning
⚫ Consider each risk and develop a strategy to manage that
risk.
⚫ Avoidance strategies
⚫ The probability that the risk will arise is reduced;
⚫ Minimisation strategies
⚫ The impact of the risk on the project or product will be
reduced;
⚫ Contingency plans
⚫ If the risk arises, contingency plans are plans to deal with
that risk;
Risk management strategies (i)
Risk management strategies (ii)
Risk monitoring
⚫ Assess each identified risks regularly to decide whether or
not it is becoming less or more probable.
⚫ Also assess whether the effects of the risk have changed.
⚫ Each key risk should be discussed at management
progress meetings.
Risk indicators
Key points
⚫ Good project management is essential for project success.
⚫ The intangible nature of software causes problems for
management.
⚫ Managers have diverse roles but their most significant activities
are planning, estimating and scheduling.
⚫ Planning and estimating are iterative processes
which continue throughout the course of a
project.
Key points
⚫ A project milestone is a predictable state where a formal
report of progress is presented to management.
⚫ Project scheduling involves preparing various graphical
representations showing project activities, their durations
and staffing.
⚫ Risk management is concerned with identifying risks
which may affect the project and planning to ensure that
these risks do not develop into major threats.