Project Management

Index

ABCD

Advantages

Business targets

Costs

Demands

Critical Path

Gantt Chart

Lichtenberg Method

Milestone Plan

MuSCoW

  1. Must

  2. Should

  3. Could

  4. Would

Project Maturity

L5 1-1.1 1.1-1.5 1.5-2.0 2.0-3.0
L4 1-1.2 1.2-1.9 1.9-2.6 2.6-3.0
L3 1-1.4 1.4-2.4 2.4-3.0
L2 1.1-1.5 1.5-2.9 2.9-3.0
L1 1.3-1.7 1.7-3.0
1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3.0

Project Quality

Priority & embedment Yes No
1 Is the project embedded in the business?
2 Has effect goals been evaluated by business managers and do they take full responsibility for their realisation?
Goal & delivery Yes No
3 Are all product targets established, known and accepted?
4 Are effect and product targets continously evaluated against business value and requirements?
Competence Yes No
5 Does the client have prior experience of good results from projects of this type and extent?
6 Does the project manager have prior experience of good results from projects of this type and extent?
7 Is competence covered regarding product and business knowledge?
Organisation, responsibility & decision Yes No
8 Does the team understand and accept its roles, responsibilities and authorities?
9 Does the project have a defined steering committee with documented responsibility?
Team & communication Yes No
10 Are the stakeholders identified and a communication plan formulated?
11 Will the project start with a kick-off where targets etc are clarified?
Continous decision making, planning & follow-up Yes No
12 Has the project manager been provided a defined budget and is the project manager allowed to make decisions within the project contract?
13 Are there documented and well established routines for decisions?
Summize the number of "No" answers and divide by 13 0 %

Project Risk

Priority & embedment Yes No
1 Is the project low priority?
2 Might the project be perceived as a threat?
3 Is project responsibility towards the business fuzzy?
4 Does the project consist of unsecured resources?
Resources & competence Yes No
5 Is there a lack of competence in current product or business areas?
6 Does anyone in charge work part time?
7 Does the project depend on anyone who is involved in other projects?
Complexity Yes No
8 Are there any disputes about requirements?
9 Does the project affect a lot of people?
10 Is there a forcing deadline near the planned closure?
Dependencies Yes No
11 Does the project lack a well defiend recipient?
12 Are there any dependencies towards other projects or external stakeholders?
13 Could the project be questioned due to uncertainties within the market or business?
Summize the number of "Yes" answers and divide by 13 0 %

Project Triangle

Choose your colour:
Red, Green or Blue

Project Triangle

Risk Evaluation

Probability × Impact

Probability 1 < 20 %
2
3 50 %
4
5 > 80 %
Impact 1 Low
2
3 Middle
4
5 High
Assign a value (1-5) to probability and a value (1-5) to impact. Multiply these values to get the Risk Value.
Rank the risk from highest to lowest and deal with the highest ranked risks first.
Risk Probability Impact Risk Value Action
... 3 5 15 ...

Risk Strategy

Avoid

  • Adjust the project plan
  • Take action to protect from impact

Transfer

  • Outsorce

Minimise

  • Take action to minimise probability or impact

Accept

ROI

Return on Investment

← Gross benefit → Benifits difficult to define ← Net benefit →
Indirect benifits
Direct result-affecting benifit
Project cost
Cost should never exceed direct result-affecting benifit

S.M.A.R.T.

Specific

Measurable

Acceptable

Realisable

Time-limited

SWOT

Strength Weakness Opportuinty Threat

Positive Negative
Internal Strengths Weaknesses
External Opportunities Threats

WBS

Work Breakdown Structure

Define all parts of the project

WBS example