Chief Information Officers (CIO)

1. Chief Information Officers(CIO)

2. Module 6 IT Project Management Prince 2 Framework

3. To present and provide basic concepts and techniques of IT Project Management using PRINCE 2 Framework Objectives of Module 6

4. Pre Project Initiation Stage Subsequent Stages Final Stage Directing a Project P3 Directing IT Project Management Prince 2 Process Model Start Up P1 Managing a Stage Boundary P6 Managing a Stage Boundary P6 Closing a Project P7 Managing Initiating a Project P2 Controlling a Stage P4 Controlling a Stage P4 Manage Product Delivery P 5 Manage Product Delivery P 5 Delivering

5. PRINCE 2 PROJECT MANAGEMENT Themes Th1: Business Case (why) Th2: Organization (who) Th3: Planning (where, how, when and how much) Th4: Progress Assessment Th5: Risk Management (what if ) Th6: Quality Th7: Change Management

6. The PRINCE2 principles Pr1: Business Case Pr2: Continuous learning Pr3: Roles and responsibilities Pr4: Manage by stages Pr5: Management by Exception Pr6: Product-based focus Pr7: Tailor

7. PRINCE 2: Project Documents D1: Mandate D2: Business Case D3: Project Brief D4: Project Initiation Document (PID) D5: Work Package D6: Status Report (or Project Board Report) D7: Project End Report (closure document) D8: Exceptions Report D9: Lessons Report D10: Issue Register D11: Risk Register D12: Lessons Learned Register

8. PROJECT MANAGER SKILLS • leadership skills; • to be open to conviction; • to be able to deal with conflict; • negotiation skills; • ability to motivate; • ability to solve problems

9. Relationship between PRINCE2 themes and building blocks

10. PROJECT MANAGEMENT TECHNIQUES Product-Based Planning (T1) 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

11. PROJECT MANAGEMENT TECHNIQUES Other Project Planning Techniques PERT: Project Evaluation and Review Techniques CPM: Critical Path Method

12. Other Techniques • Quality Check (T2) • Configuration Management (T3) • Lessons Learned and Customer Satisfaction (T4)

13. Project and portfolio management systems Ability to Execute Completeness of Vision

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 Document Management (B1)

15. Reasons for acting • Objectives/benefits • Most important results • Scope • Limitations • Relations with Other Projects Mandate - <number> <project name> (B2)

16. Context of project <<why is it needed, what is the preceding history, how does it fit into the programme? Project background <project name> B3

17. Geography • Customer • Processes Involved • System Involved • Departments Involves • Products Involved Scope - <project name> (B4)

18. Corporate risk • Operational risk … • Infrastructural risk … • Supplier risk Business Case risk analysis - <project name> (B5)

19. Budget • Profit and Loss Statement • NPV • Pay Back Period • Internal Rate of Return Cost benefit cash flow - <project name>(B6)

20. In house Development • Based on Specific Technology • Big Bang Implementation • Step by Step Alternatives A, B, C Project Approach-<project name> (B7)

21. Resource Name • Input Product Name • Tasks • Indicative Time frame Resources - <project name> (B12)

22. Product name • Activities • Start Date • Completion Date • Planned Vs Actual Planning <date> - <project name> (B13)

23. Project Evaluation and Review Technique PERT / CPM