1 Project Management – PMBOK® Project Management Plan Dr Marc Conrad Office: D104 – Park Square Marc.Conrad@beds.ac.uk 23.03.2016 Marc Conrad University of Bedfordshire 1 2 Project Management Processes Project Management Plan Initiation Project Charter Scope WBS (definition) Cost Time Human Resources (estimates, …) (activity diagrams, …) (RACI matrix, …) • Also to consider: Quality, Risk, Communication, Procurement, Integration (PMBOK® knowledge areas) 3 The Project Management Plan • The Project Management Plan integrates subsidiary plans relating to the knowledge areas into one document. • The Project Management Plan is a reference for managing the project. It should be “owned” by the project manager and the team. • The Project Management Plan is updated and revised throughout the project. PROJECT PLAN Project Name: Prepared by: Version History (insert rows as needed): Version Date Comments (MM/DD/YYYY) 1.0 Create links to referenced documents (e.g., Link_To_… ) by using Insert Hyperlink on your toolbar. 1. Executive Summary A summary description of the project is included in the Project Scope Statement. Please refer to that document for the following: 23.03.2016 Marc Conrad University of Bedfordshire Project Purpose and Justification: The business need/problem that needs to be solved. Project Overview: A brief description of what the project is intended to do. Project Objectives: A brief, concise list of measurable outcomes expected from this project. Project Approach: The strategy to deliver the project. Project Assumptions and Constraints: Link_To_Project_Scope Statement See Project Charter for Budget Overview: Link_To_Project_Charter 3 4 Contents of the Project Management Plan • The Project Management Plan documents: The processes selected by the project management team. The tools and techniques to be used. The selected project life cycle and project phases. How work will be executed and changes will be monitored/controlled Communication techniques used (team + stakeholders) • Exercise: Discuss the differences of tools & techniques, life cycle, execution and communication between a software project based on the UML and an Marc Conrad agile23.03.2016 software project (next two slides). 4 University of Bedfordshire 5 Case Study – UML & Agile The UML - Process (according to Larman) 1. 2. 3. 4. 5. 6. 7. Use Cases Conceptual Model System Sequence Diagram System Contracts Collaboration Diagram Class Diagram Code http://www.objectsbydesign.com/books/larman_process.html 23.03.2016 Marc Conrad University of Bedfordshire 5 6 Case Study – UML & Agile The Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan http://agilemanifesto.org 23.03.2016 Marc Conrad University of Bedfordshire 6 7 Subsidiary Plans of the Project Management Plan • The Project Management Plan may be composed of one or more subsidiary plans, Scope management plan Schedule management plan Cost management plan Quality management plan Staffing management plan Communication management plan Risk management plan Procurement management plan • See also PRINCE2 templates as examples! 23.03.2016 Marc Conrad University of Bedfordshire 7 8 Inputs of the “Develop Project Management Plan” PMBOK® Process Project Charter Outputs from planning processes Enterprise environmental factors Organizational process assets 23.03.2016 Marc Conrad University of Bedfordshire 8