1 / 26

CIF 301 Project Planning Unit 4

CIF 301 Project Planning Unit 4. Project Planning. Introduction Why plan?. The consequences of poor planning (in the order they happen). premature project initiation wild enthusiasm disillusionment chaos search for the guilty punishment of the innocent promotion of the non-participants

taylor-dillard
Download Presentation

CIF 301 Project Planning Unit 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIF 301 Project PlanningUnit 4

  2. Project Planning • Introduction • Why plan?

  3. The consequences of poor planning(in the order they happen) • premature project initiation • wild enthusiasm • disillusionment • chaos • search for the guilty • punishment of the innocent • promotion of the non-participants • definition of the requirement

  4. Planning components • Objectives • Programme • Schedule • Budget • Forecast

  5. Planning components • Organisation • Policy • Procedures • Standards

  6. Planning Frameworks • There are many planning and project frameworks • Two examples are: • Step Wise • Prince 2

  7. Step Wise • Step Wise has 10 defined steps …. • Step 0 Select project • called step 0 because it is outside main project planning process • Step 1 Identify project scope and objectives • Step 2 Identify project infrastructure • Step 3 Analyse project characteristics • Step 4 Identify project products and activities

  8. Step Wise • Step 5 Estimate effort for each activity • Step 6 Identify activity risk • Step 7 Allocate resources • Step 8 Review / publicise plan • Step 9 Execute plan • Step 10 Lower levels of planning • Within each step are various sub-sections

  9. Step Wise • Step 1 Identify project scope and objectives • Identify objectives and measures of effectiveness in meeting them • Establish a project authority • Identify all stakeholders in the project and their interests • Modify objectives in the light of stakeholder analysis • Establish methods of communication with all parties

  10. Step Wise • Step 2 Identify project infrastructure • Establish relationships between project and strategic planning • Identify installation standards and procedures • Identify project team organisation

  11. Step Wise • Step 3 Analyse project characteristics • Distinguish the project as either objective or product driven • Analyse other project characteristics • Identify high level project risk • Take into account user requirements concerning implementation • Select general life-cycle approach • Review overall resource estimates

  12. Step Wise • Step 4 Identify project products and activities • Identify and describe project products (or deliverables) • Document generic product flows • Recognise product instances • Produce ideal activity network • Modify ideal to take into account need for stages and checkpoints

  13. Step Wise • Step 5 Estimate effort for each activity • Carry out bottom-up estimates • Revise plans to create controllable activities

  14. Step Wise • Step 6 Identify activity risk • Identify and quantify activity-based risks • Plan risk reduction and contingency measures where appropriate • Adjust plans and estimates to take account of risk

  15. Step Wise • Step 7 Allocate resources • Identify and allocate all resources • Revise plans and estimates to account for resource constraints

  16. Step Wise • Step 8 Review/publicise plan • Review quality aspects of project plan • Document plans and obtain agreement

  17. Step Wise • Step 9 Execute plan • Step 10 Lower levels of planning • There are no sub-sections for steps 9 & 10

  18. PRINCE 2 • PRINCE is an acronym for: • Projects IN Controlled Environments • PRINCE was conceived and developed by the Central Computer and Telecommunication Agency (CCTA)

  19. PRINCE 2 • PRINCE 2 defines three key elements • Each element has several fundamental constituents

  20. PRINCE 2 • Processes • Starting Up A Project (SU); • Initiating A Project (IP); • Directing A Project (DP); • Managing Stage Boundaries (SB); • Controlling A Stage (CS); • Managing Product Delivery (MP); • Closing A Project (CP); • Planning (PL) (also a Component and Technique)

  21. PRINCE 2 • Components • Business Case • Organisation • Planning (also a Process and Technique) • Controls • Management of Risk • Quality In A Project Environment • Configuration Management • Change Control

  22. PRINCE 2 • Techniques • Product-Based Planning • Change Controls • Quality Reviews

  23. PRINCE 2 • Example of actions within a process • Controlling A Stage process actions … • Authorise work packages • Assess progress • Capture project issues • Examine project issues • Review stage status • Report highlights • Take corrective action • Escalate project issues • Receive completed work packages

  24. PRINCE 2 • Actions within the Planning process PL 1 Design a Plan PL 2 Define and analyse PL 3 Identify activities and their dependencies PL 4 Estimate effort for each activity PL 5 Schedule PL 6 Analyse risk PL 7 Complete plan

  25. PRINCE 2 • PRINCE2 can be a very powerful tool is used wisely • PRINCE2 can become very prescriptive • Overall PRINCE2 is a good framework to use

  26. Conclusion • Planning is important • Planning Frameworks • Project Frameworks

More Related