1

IT Project ManagementPrince 2 Framework

2

3

Objectives of Module 6

To present and provide basic concepts and techniques of IT Project Management using PRINCE 2 Framework

IT Project Management Prince 2 Process Model

4

Pre ProjectInitiation

StageSubsequent

StagesFinal Stage

Directing a Project P3

Start Up P1

Managing a Stage Boundary P6

Directing

Managing a Stage Boundary P6

Closing a Project P7

Initiating a Project P2

Controlling a Stage P4

Controlling a Stage P4

Managing

DeliveringManage Product

Delivery P 5

Manage Product

Delivery P 5

5

PRINCE 2 PROJECT MANAGEMENT ThemesTh1: Business Case (why)Th2: Organization (who)Th3: Planning (where, how, when and how much)Th4: Progress AssessmentTh5: Risk Management (what if )Th6: QualityTh7: Change Management

6

The PRINCE2 principlesPr1: Business CasePr2: Continuous learningPr3: Roles and responsibilitiesPr4: Manage by stagesPr5: Management by ExceptionPr6: Product-based focusPr7: Tailor

7

PRINCE 2: Project DocumentsD1: MandateD2: Business CaseD3: Project BriefD4: Project Initiation Document (PID)D5: Work PackageD6: Status Report (or Project Board Report)D7: Project End Report (closure document)D8: Exceptions ReportD9: Lessons ReportD10: Issue RegisterD11: Risk RegisterD12: Lessons Learned Register

8

• leadership skills;• to be open to conviction;• to be able to deal with conflict;• negotiation skills;• ability to motivate;• ability to solve problems

PROJECT MANAGER SKILLS

9

Themes No. Related Building Blocks

Business Case Th1 B2, B3, B4, B5, B6Organisation Th2 B1, B2, B12, B15, B22, B24

Planning Th3 B13, B22Progress Assessment Th4 B5, B6, B16, B22, B23, B25

Risk Management Th5 B2, B5, B14, B22, B25, B30, B31

Quality in projects Th6 B11, B17, B21, B22Change Management Th7 B1, B22, B23, B30, B31

Relationship between PRINCE2 themes and building blocks

10

PROJECT MANAGEMENT TECHNIQUES

Product Breakdown (B10) analyses the products in terms of product parts. If you then determine the quality requirements for these products, you have the basis for the planning. A plan that is based on the Product Breakdown shows the sequence of the project activities

Product-Based Planning (T1)

11

PROJECT MANAGEMENT TECHNIQUES

Other Project Planning TechniquesPERT: Project Evaluation and Review Techniques

CPM: Critical Path Method

12

Other Techniques

•Quality Check (T2)•Configuration Management (T3)•Lessons Learned and Customer Satisfaction (T4)

Project and portfolio management systems

13

Oracle SAP

Planisware

CA Clarity

HP PPM Plan View Primavera Systems Compuware

Microsoft Project Daptiv

EPK Group

Atlantic Global Cardinis Solutions

Augeo Software

Serena Software

Power Steering Instantis Innotas Sciforma

ITM Software

Ability to Execute

Completeness of Vision

Document Management (B1)

14

•Revision History

•Approvals

•Distribution

This building block shows the versions of a document and the most important changes in successive versions. In ‘Revision History’ the ‘status’ field provides the opportunity to indicate the stages that the document has passed through

Mandate - <number> <project name> (B2)

15

•Reasons for acting•Objectives/benefits•Most important results•Scope•Limitations•Relations with Other Projects

Project background <project name> B3

16

Context of project

<<why is it needed, what is the preceding history, how does it fit into the programme?

Scope - <project name> (B4)

17

•Geography•Customer•Processes Involved•System Involved•Departments Involves•Products Involved

Business Case risk analysis - <project name>

(B5)

18

•Corporate risk• Operational risk …• Infrastructural risk …• Supplier risk

Cost benefit cash flow - <project name>(B6)

19

• Budget• Profit and Loss Statement• NPV• Pay Back Period• Internal Rate of Return

Project Approach- <project name> (B7)

20

•In house Development

•Based on Specific Technology

•Big Bang Implementation

•Step by Step Alternatives A, B, C

Resources - <project name> (B12)

21

•Resource Name•Input Product Name•Tasks•Indicative Time frame

Planning <date> - <project name> (B13)

22

•Product name•Activities•Start Date•Completion Date•Planned Vs Actual

Project Evaluation and Review Technique PERT / CPM

23