KU Leuven Project Management - Part 1 PDF

Project Management Dries Vandevyvere (Proj3ctS BV) KU Leuven © Proj3ctS - Dries Vandevyvere - 2024 Introduction - Dries Vandevyvere Engineer / IT / Project & program Management / Business Mentor Consulting - Product - Project - Program - IT management Accenture...

Project Management Dries Vandevyvere (Proj3ctS BV) KU Leuven © Proj3ctS - Dries Vandevyvere - 2024 Introduction - Dries Vandevyvere Engineer / IT / Project & program Management / Business Mentor Consulting - Product - Project - Program - IT management Accenture - Itineris - Ablynx - Ambits - Proj3ctS - Galapagos - ECS Chemicals / Utilities / Natural resources / Bio-Pharma / Supply Chain Passionate about travelling & outdoor activities with my wife & 2 girls © Proj3ctS - Dries Vandevyvere - 2024 Introduction - Course Content Main objectives Help you understand what a project is & why it matters for an engineer Give you the basic understanding of how project management is done Introduce the new trends and future of project management: Agile & Hybrid Provide you with tools, techniques, frameworks and guidance to get started on a project or work in a project team Give hints & tips based on experience and provide you with practical advise Analyse and solve problems in a project-based approach Collaboration & teamwork in a project context Course material These slides Background materials: articles, blog posts and/or references Exercises & quiz questions Lexicon © Proj3ctS - Dries Vandevyvere - 2024 Introduction - Course Content Part 1: Intro, stakeholders, change & scope management What is a project? How does project management work? Why does it matter? Stakeholder management + change + communication + team motivation How to define and manage the scope of the project Part 2: Estimating, scheduling & resources Reliable project estimates Project Scheduling done right Optimize resource scheduling Part 3: Risks, progress & Agile Project Risk Management Tracking progress and keeping your project on track + Earned value management Project management in an Agile world Hybrid project management: the best of both worlds © Proj3ctS - Dries Vandevyvere - 2024 Introduction - Exam Closed book 2 types of questions Open questions Multiple choice Focus on Understanding of the core concepts Application in real-life situations Connection between the topics across the PM knowledge areas © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 What is a project ? Temporary Unique Product, service or result Complex and X-functional Goals and objectives Beneficial change or added value Plan © Proj3ctS - Dries Vandevyvere - 2024 Is this a project? This is a Project © Proj3ctS - Dries Vandevyvere - 2024 Is this a project? Not a Project © Proj3ctS - Dries Vandevyvere - 2024  What is a project ? “ A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or staffing) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value… that we agreed to deliver based on a plan. ” © Proj3ctS - Dries Vandevyvere - 2024 This is a Not a Project Project © Proj3ctS - Dries Vandevyvere - 2024 History of Project Management Pyramids First signs of project management -2020 -208 Great Chinese Wall Clear objective Resource Management Phasing Never finished No documentation Many sponsors No stakeholder engagement © Proj3ctS - Dries Vandevyvere - 2024  History of Project Management Cold Control VUCA Maximise control on the PM process -> first PM Scrum & PmBok standards arise: Waterfall ‘30 ‘60 ‘69 ‘86 ‘87 Now VUCA Crazy Creativity Volatility – Uncertainty – Complexity - Ambiguous Project Management more as an art to overcome engineering problems -> CPM, PERT, Gantt © Proj3ctS - Dries Vandevyvere - 2024 Project Management Methods Kanban PMBoK XP Classic Prince2 Hybrid SCRUM Agile Waterfall – Plan Based Iterative – Value Based Waterscrumfall Prism SCRUMBAN CCPM LEAN © Proj3ctS - Dries Vandevyvere - 2024  PM Methods overview Classic Plan (waterfall) Analyze Build Test Launch Agile (Scrum) Sprint 1 Sprint 2 Launch Sprint 3 Sprint N Launch © Proj3ctS - Dries Vandevyvere - 2024  Classic Project Management Classic Plan (waterfall) Analyze Build Test Launch Agile Project Management Agile (Scrum) Sprint 1 Sprint 2 Sprint 3 Sprint N Launch © Proj3ctS - Dries Vandevyvere - 2024 The triple constraint / Iron triangle © Proj3ctS - Dries Vandevyvere - 2024  What is Project Management ? Project “Project management is the Management application of processes, methods, tools, skills, knowledge and experience to achieve specific project objectives.“ © Proj3ctS - Dries Vandevyvere - 2024 What does a project manager do? s Organize chaos Set Goals Conduct Lessons learned Control Integrate & Manage collaborate Stakeholders Quality Manage Cost / Communicate Use Tools Plan Manage Risk Resources © Proj3ctS - Dries Vandevyvere - 2024 Who is the project manager? SUCCESS © Proj3ctS - Dries Vandevyvere - 2024  The Project Management Process Project Project Project Preparation Execution Closure Business Idea -> Business requirements Documented in a Project Charter Project Charter = approval to start the project (preparation) © Proj3ctS - Dries Vandevyvere - 2024  The Project Management Process Project Project Project Preparation Execution Closure The final deliverable of the Project Preparation Phase = Project Plan Project Plan contains: goal, scope statement, deliverables, stakeholder analysis, budget, timeline, resources, risks, … © Proj3ctS - Dries Vandevyvere - 2024 The Project Management Process Project Project Project Preparation Execution Closure During the project, deliverables are delivered according to a milestone planning © Proj3ctS - Dries Vandevyvere - 2024 The Project Management Process Project Project Project Preparation Execution Closure Knowledge transfer, lessons learned and project acceptance are delivered during Project Closure © Proj3ctS - Dries Vandevyvere - 2024  Budget management during the project Project Project Project Preparation Execution Closure Project Charter: Project Plan: Detailed Cost & Time Control: actuals Lessons Learned: cost & High level cost estimate estimations on work versus planned time performance package level -> aggregated + Change Mgt: new estimates for change requests © Proj3ctS - Dries Vandevyvere - 2024 Stanish group - CHAOS Report © Proj3ctS - Dries Vandevyvere - 2024 Top factors found in failed projects: 1. Incomplete Requirements 2. Lack of user involvement 3. Lack of resources 4. Unrealistic expectations 5. Lack of executive support 6. Changing Requirements & Specifications 7. Lack of planning 8. Didn’t need it any longer 9. Lack of IT management 10. Technical illiteracy © Proj3ctS - Dries Vandevyvere - 2024 The top five factors in successful projects are: 1. User involvement 2. Executive management support 3. Clear Statement of Requirements 4. Proper planning 5. Realistic expectations © Proj3ctS - Dries Vandevyvere - 2024  Top vs Flop Top factors found in failed projects: The top five factors in successful projects: 1. Incomplete Requirements 1.User involvement 2. Lack of user involvement 2.Executive management support 3. Lack of resources 3.Clear Statement of Requirements 4. Unrealistic expectations 4.Proper planning 5. Lack of executive support 5.Realistic expectations 6. Changing Requirements & Specifications 7. Lack of planning 8. Didn’t need it any longer 9. Lack of IT management 10.Technical illiteracy © Proj3ctS - Dries Vandevyvere - 2024 Project Life Cycle © Proj3ctS - Dries Vandevyvere - 2024 Classic Project Management - Planning Work Breakdown Structure (WBS) Task ID Tasks Dependencies Duration Work Material 1.1 Order Concrete N/A 5 1 0 1.2 Prep Surface N/A 5 10 2000 1.3 Place molding 1.2 3 6 1000 Task List 1.4 Place concrete nets 1.3 1 2 1000 1.5 Pour Concrete 1.4 1 2 5000 1.6 Dry Concrete 1.5 14 0 0 1.7 Remove molding 1.6 2 2 0 © Proj3ctS - Dries Vandevyvere - 2024  Classic Project Management - Planning Task ID Tasks Dependencies Duration Work Material 1.1 Order Concrete N/A 5 1 0 Task List 1.2 Prep Surface N/A 5 10 2000 1.3 Place molding 1.2 3 6 1000 1.4 Place concrete nets 1.3 1 2 1000 1.5 Pour Concrete 1.4 1 2 5000 1.6 Dry Concrete 1.5 14 0 0 1.7 Remove molding 1.6 2 2 0 Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Critical Path Method Order Concrete Prep Surface (CPM) Molding + Nets +pour Dry Concrete Remove © Proj3ctS - Dries Vandevyvere - 2024  Classic Project Management - Planning Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Critical Path Method (CPM) Order Concrete Prep Surface Molding + Nets +pour Dry Concrete Remove Resource allocation © Proj3ctS - Dries Vandevyvere - 2024 Classic Project Management - Control Scope Quality People Manage = Control Risk Time Cost © Proj3ctS - Dries Vandevyvere - 2024 Project management processes (PMBOK) Initiating Process Group: Processes required to launch a new project or a new project phase. Planning Process Group: Processes related to defining and planning the extent of the project, as well as planning how it will be executed. Executing Process Group: Processes related to the actual completion of project activities and tasks. Monitoring & Controlling Process Group: Processes covering everything related to tracking, monitoring, reporting on, and controlling project performance and progress. Closing Process Group: Processes required to finalize and complete a project or project phase. © Proj3ctS - Dries Vandevyvere - 2024 Project management processes (PMBOK) © Proj3ctS - Dries Vandevyvere - 2024 Knowledge areas & performance domains (PMBOK) PMBOK 6 PMBOK 7 1. Project Integration Management 1. Team 2. Project Scope Management 3. Project Schedule Management 2. Stakeholders 4. Project Cost Management 3. Lifecycle 5. Project Quality Management 4. Planning 6. Project Resource Management 5. Navigating uncertainty & ambiguity 7. Project Communications Management 6. Delivery 8. Project Risk Management 9. Project Procurement Management 7. Performance 10. Project Stakeholder Management 8. Project work © Proj3ctS - Dries Vandevyvere - 2024  PM process groups and knowledge areas (PMBOK 6) © Proj3ctS - Dries Vandevyvere - 2024 12 Project Management Principles (PMBOK 7) 1. Stewardship: Be a diligent, respectful, and caring steward. 2. Team: Create a collaborative project team environment. 3. Stakeholders: Effectively engage with stakeholders. 4. Value: Focus on value. 5. Systems Thinking: Recognize, evaluate, and respond to system interactions. 6. Leadership: Demonstrate leadership behaviors. 7. Tailoring: Tailor based on context. 8. Quality: Build quality into processes and deliverables 9. Complexity: Navigate complexity. 10. Risk: Optimize risk responses. 11. Adaptability & Resilience: Embrace adaptability and resiliency. 12. Change: Enable change to achieve the envisioned future state. © Proj3ctS - Dries Vandevyvere - 2024 The history of Agile: Roots in software development © Proj3ctS - Dries Vandevyvere - 2024 Agile: 4 values & 12 principles © Proj3ctS - Dries Vandevyvere - 2024  The PM triangle: Classic vs Agile Constraints Requirements Cost Schedule Value driven Plan driven Estimates Cost Schedule Features Approach Requirements Activities Delivery Goal Performed once for the Classic (waterfall) Fixed Single Delivery Deliver at cost, on time and at quality entire project Frequent small Customer value via frequent deliveries & Agile (Scrum) Dynamic Repeat until correct deliveries feedback © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 Stakeholder management What are stakeholders ? Why do we need them ? How do we analyze them ? How to we work with them ? Challenges with stakeholders ? © Proj3ctS - Dries Vandevyvere - 2024 Stakeholders Stakeholders are individuals or groups who have an interest or some aspect of rights or ownership in the project, and can contribute to, or be impacted by, the outcomes of the project. © Proj3ctS - Dries Vandevyvere - 2024 Stakeholder management Start to find Analyze Document Classify Plan 2. Plan 1. Identify stakeholder stakeholders management 4. Control 3. Manage stakeholder stakeholder engagement engagement Monitor Implement Update © Proj3ctS - Dries Vandevyvere - 2024 Identify stakeholders EVERYONE CAN BE A STAKEHOLDER … not everyone should be considered as one ! © Proj3ctS - Dries Vandevyvere - 2024 Identify stakeholders How to start? Start to find: Look at the project goal: who is impacted/ Who can impact the project ? Look at the organization you are working for: who is involved? Who should be involved ? Look at the environment around the project: communities? Government? Regulators ? How: conduct interviews and/or set up brainstorm with the project team © Proj3ctS - Dries Vandevyvere - 2024 Plan - Power/Interest matrix What is their interest in the project ? What is their Power ? How? Power/Interest Matrix ! © Proj3ctS - Dries Vandevyvere - 2024 Plan - Stakeholder circle Size pie= influence Depth = impact Distance from the core = proximity Color= type of stakeholder Pattern: group or person © Proj3ctS - Dries Vandevyvere - 2024 Plan - Stakeholder salience Power of the stakeholder Refers to the perceived validity or appropriateness of the stakeholder’s claim to a stake Urgency of the demand made by the stakeholder Refers to the degree to which the stakeholder’s claim demands immediate attention Legitimacy of the stakeholder demand Refers to the ability or capacity of a stakeholder to produce an effect © Proj3ctS - Dries Vandevyvere - 2024 Stakeholder management plan Stakeholder register Additions: Current & desired engagement levels Impact of change to stakeholders Interrelationships and overlap between stakeholders Communication requirements Information to be distributed (incl. language, format, content, level of detail, …) Reason for communictation and expected impact Time and frequency of distribution of information Method for updating/refining the plan Stakeholder Power Interest Engagement level Action(s) Details Status Stakeholder A H H Neutral -> Supportive Weekly status meetings Status + issues + risks Ongoing Stakeholder B H L Unaware -> neutral Monthly newsletter In English To start … © Proj3ctS - Dries Vandevyvere - 2024 Stakeholders: management -> engagement © Proj3ctS - Dries Vandevyvere - 2024 Stakeholder engagement Acknowledge Avoid conflicts Listen Engagement Cooperate Communicate Adapt © Proj3ctS - Dries Vandevyvere - 2024 Stakeholder engagement Unaware: unaware of project and potential impacts Resistant: Aware of project and potential impacts; resistant to change Neutral: Aware of project yet neither supportive nor resistant C = current / D = desired Supportive: Aware of project and potential impacts; supportive to change Leading: Aware of project and potential impact; actively engaged in ensuring the project is a success © Proj3ctS - Dries Vandevyvere - 2024 Challenges with stakeholders Distracted Too many projects and initiatives at the same time Global workforce Difficult to communicate and engage Cultural differences Resistance to change VUCA world Change is the only constant What happened to my project? My stakeholder? Me? © Proj3ctS - Dries Vandevyvere - 2024 “Projects would be so much easier if it didn’t involve… people” - Anonymous Project Manager © Proj3ctS - Dries Vandevyvere - 2024 Hints & tips: How to start Consult early What & how you say it Be positive & convinced Open for feedback Adapt approach Fit to the stakeholder’s need & style Review the list, the plan & the engagement Consult often Informal & formal meetings Actively listen Be open for feedback © Proj3ctS - Dries Vandevyvere - 2024 Hints & tips: during the project Show the benefit What’s in it for them ? No Machiavelli Influcene with authenticity, integrity & sincerity Just do it! Actively engage with stakeholders Plan -> execute -> evaluate -> repeat © Proj3ctS - Dries Vandevyvere - 2024 Hints & tips: Stakeholders Relationships Actively work with your stakeholders Listen & Learn Actively listen: what are their real expectations Seek confirmation! Don’t assume, ask confirmation if their expectations are still met Their only human Expectations can change Can be irrational Perception can change Everything is people business Can conflict Different stakeholders = different /conflicting interests © Proj3ctS - Dries Vandevyvere - 2024  Stakeholder engagement is about turning stakeholders into opportunities to be successful as a project manager - Another unknown PM © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 © Proj3ctS - Dries Vandevyvere - 2024 The cycle of change © Proj3ctS - Dries Vandevyvere - 2024 Change and communication (Kübler Ross) © Proj3ctS - Dries Vandevyvere - 2024 Hints & tips for communication & change Communicate clearly, early, and often Communicate through & to the right people Communicate through multiple channels Answer the questions, “what’s in it for me?” “what does it mean to me?” Prepare for resistance Listen to feedback Don’t be afraid to repeat yourself © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 Team motivation “I’m not the smartest fellow in the world, but I sure can pick smart colleagues.” — Franklin D. Roosevelt “A team is not a group of people who work together but a team is a group of people who trust each other.” — Simon Sinek © Proj3ctS - Dries Vandevyvere - 2024 Phases of team development (Tuckman) © Proj3ctS - Dries Vandevyvere - 2024 Dysfunctions of a team (Lencioni) © Proj3ctS - Dries Vandevyvere - 2024 Hoe reageren als project manager? © Proj3ctS - Dries Vandevyvere - 2024 © Proj3ctS - Dries Vandevyvere - 2024 Most difficult = trust => the trust equation © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 Scope - definitions Project scope Management The process required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is in and what is not included in the project. Product scope: The features and functions that characterize a product, service or result. Project scope: The work performed to deliver a product, service, or result with the specific features and functions. The sum of the products, services, and results to be provided as a project © Proj3ctS - Dries Vandevyvere - 2024 Before scope management can start Collect all relevant information & documentation Project Execution Plan (PEP) contains Project charter: Document issued by the initiator/sponsor that authorizes the existence of a project and provides the PM with the authority to apply resources to project activities. Enterprise environmental factors Organizational chart (can very in different phases) with functions and names. Description of roles and responsibilities; RACI; Limit of responsibility Organization assets Company procedures & Scope change procedures Working processes to prepare and handle schedule, budget, incidents, … Communication strategy Other inputs Risk assessments Filling, naming and revision of documents Approval Cycle Without this you will never have the correct people in front of you and chaos will be your share © Proj3ctS - Dries Vandevyvere - 2024 Project scope management Business This is where your project goes wrong ! need Actual start of your project Collect data Define Will be treated together in this part of the course, as different scope stages in scope definition, require different information & data. Validate scope Important stage gate Control scope This is where your project goes wrong ! © Proj3ctS - Dries Vandevyvere - 2024 Business need What? It is actual necessity or need to start a project. It answers the question “Why are we doing this project” Who is involved? Normally higher management: Shareholders, board of directors, operational management… Other relevant stakeholders Strategic plan of a company (e.g. Input Output growth, diversification) Market demands (e.g. new products) Clear answer to your question ”Why are HR Department (e.g. training programs, we doing this project?” diversification, reorganization) Start of Project charter (remains your IT department (e.g. New software) basic reference for the project) Health and safety department Bottom-up initiatives © Proj3ctS - Dries Vandevyvere - 2024 Bussiness need - importance Business need is very rarely a clear description If it is not clarified by you, your target to start the project will be too vague. e.g. Improve safety in the company Find out, what is the bases for this specific business need. A business need is not a “technical” solution. e.g. A new production line is not business need. It does not answer the question “Why?” Business need: obsolescence and so not reliable, not flexible, Turnover growth, new products If the “why?” is not clear, the solution will be wrong/or too limited and re- work or delay will be the result. It is essential to get alignment between the requester(s) and the project team © Proj3ctS - Dries Vandevyvere - 2024 Bussiness need - Techniques & outcomes Expert judgment Requirements documentation Data gathering Requirements traceability matrix Brainstorming Interviews Focus groups Questionnaires and surveys Benchmarking Data analysis Document analysis Decision making Voting Multicriteria decision analysis Data representation Affinity diagrams Mind mapping Interpersonal and team skills Nominal group technique Observation/conversation Facilitation Context diagram Prototypes © Proj3ctS - Dries Vandevyvere - 2024 Requirements traceability matrix A grid that links requirements from their origin to the deliverables that satisfy them. Helps ensure a requirement adds business value by linking it to the objectives Provide a means to track requirements throughout the project life cycle Ensure that requirements approved in the requirements documentation are delivered at the end of the project Finally, it provides a structure for managing changes to the product scope Tracing requirements includes: Business needs, opportunities, goals, and objectives; Project objectives; Project scope and WBS deliverables; Product design; Product development; Test strategy and test scenarios © Proj3ctS - Dries Vandevyvere - 2024 Project scope management Business need Collect data Collect data & Define Define scope scope Validate scope Control scope © Proj3ctS - Dries Vandevyvere - 2024 Collecting data and define scope Collecting data and Define the scope = Project Scope Description What? Project Scope Description is a document or collection of documents that describe the target (business need) the criteria input requested output of the project It will be the backbone of your project scope throughout the entire project life cycle. It will be together with your schedule, budget and project plan, the “bible” of the project Consists out of 2 main parts: 1. A functional description 2. The work breakdown structure (WBS) © Proj3ctS - Dries Vandevyvere - 2024 Collecting data and define scope Functional description Other names: Pharmaceutical industry: User Requirement Brief; PMBOK: Project Scope Statement; Others: program of demands, Project Description Sheet, Statement of Scope What? It describes all the functionalities of your project of the starting conditions and of the requested project output It contains typical: The target or Business need; The request product description (the output of the project), including all of its characteristics and acceptance criteria; The project acceptance criteria (under which the project can be stopped or continued, e.g.: ROI, schedule, resources, budget, quality…); The project main deliverables; The constrains; © Proj3ctS - Dries Vandevyvere - 2024 Functional description: Actual => New situation Concrete project outcome Business “Technical“ Input need Output solution Solution characteristics Assumptions; Legal requirements; INCLUDES Risks; (Standards); (Company procedures); Project boundaries; Exclusions; Impact on other departments/services or projects PM and project team; INVOLVES Requester; Actual user; Experts (internal/experts); Others: Quality, maintenance, HR, IT, legal advisor… © Proj3ctS - Dries Vandevyvere - 2024 Hints & Tips: Collecting data and define scope Do not only discuss with department managers Contact who will be involved with the outcome of your project on daily bases e.g. operators, workers, maintenance people, IT-ers, safety controllers … Take time for discussions, reviews, brainstorms, and reflection Going too fast will stop the reflection: Better ideas will come when you are in the next phase leading to re-work Taking extra time here will save you lots in the next phase Explain “live” the functional description Make it official by signing it off by the required stakeholders If necessary, make a confidential part (critical product/company data) © Proj3ctS - Dries Vandevyvere - 2024 Scope decomposition Scope = the sum of the products, services, and results to be provided as a project. Scope decomposition: Scope can be elaborated using Scope statement to identify the major deliverables associated with the project Acceptance criteria for each deliverable Scope can be elaborated by decomposing it into lower levels of detail using a work breakdown structure. A WBS is a hierarchical decomposition of the total scope of work to be carried out to accomplish the project objectives and create the required deliverables Each level down in the hierarchy represents a greater level of detail of the deliverable © Proj3ctS - Dries Vandevyvere - 2024 Work breakdown structure A WBS of a project: a subdivision of all project deliverables and project work into smaller, clearer and manageable components, called work package It provides a list of everything that must be delivered It is a hierarchical and logical decomposition of the total scope Important: a WBS contains deliverables & work packages. NOT activities. © Proj3ctS - Dries Vandevyvere - 2024 Work breakdown structure Use decomposition: break the deliverables in smaller, more manageable pieces Work package Lowest level of the WBS Cost & duration can be/will be estimated and managed on this level Basis for your Work Schedule © Proj3ctS - Dries Vandevyvere - 2024 WBS dictionary Document that provides detailed deliverable & scheduling information about each WBS component. Information in the WBS dictionary may include but is not limited to: Identifier: unique Hierarchical number Description of work (the work package) Responsible person or organization, Assumptions and constraints, Schedule milestones, Associated schedule activities, Resources required, Cost estimates, Quality requirements, Acceptance criteria, Technical references, Agreement information Optional elements Discipline (civil, software, electricity, PM….); Sub-discipline (walls, windows, foundations, steel structure…) Option Y/N? Remarks Procurement package © Proj3ctS - Dries Vandevyvere - 2024 WBS: example from software development Phases of the project life cycle as the 2nd level of decomposition Product and project deliverables inserted at the third level © Proj3ctS - Dries Vandevyvere - 2024 WBS: example from engineering Major deliverables as the 2nd level of decomposition Incorporating subcomponents that may be developed by organizations outside the project team, such as contracted work The vendor then develops the supporting contract WBS as part of the contracted work © Proj3ctS - Dries Vandevyvere - 2024 WBS: Hints & tips Use Excel. Easy to install filters and make calculations Always prepare a network Start the high-level division Divide level by level Add enough detail and information Select as much columns as you deem to be necessary. You can always hide them Correct level of detailing: the work packages depend entirely on you and your team Use the WBS structure As a price list during procurement; In your work Schedule and project Schedule (later) Use the WBS as communication tool: Explain the WBS to your customer If it is clear, it is good ! © Proj3ctS - Dries Vandevyvere - 2024 Scope - Quick summary Business need: WHY ? Project Execution Plan: HOW ? project charter: mandate for the project context Project scope description: WHAT ? Functional description: outcome + solution Requirements Assumptions, Risks, Boundaries, Exclusions, Contraints, … Main deliverables Acceptance criteria WBS: breakdown => deliverables & activities © Proj3ctS - Dries Vandevyvere - 2024 Exercise: create WBS + identify activities 1. Build a Work Breakdown Structure showing the main deliverables. 2. List the activities needed to create the deliverables. © Proj3ctS - Dries Vandevyvere - 2024 Project scope management Business need Collect data Define scope Validate scope Validate scope Control scope © Proj3ctS - Dries Vandevyvere - 2024 Validate the Scope What? The process of formalizing acceptance of the complete scope Ensuring that the defined scope enables to guarantee a consistent answer to the business need. How? Group sessions in which the scope is explained and discussed; Project Risk analysis: What, if… ? Group decision techniques Output A fixed project scope that will serve as the scope baseline for the rest of the project. A bases for project schedule, estimating, budgeting, procurement and realization. © Proj3ctS - Dries Vandevyvere - 2024 Validate the Scope: Hints & tips Try to have intermediate scope validation sessions as soon as a considerable part of the project is considered as ready by the project team. Define a stage/gate model Acceptance criteria of the deliverables for every phase (stage) in your scope definition are defined. Start of the next phase depends on the results of the control of these criteria at the end of the previous phase (gate). It is not an opportunity to include additional scope, people are often tempted to do so. Communication regarding scope validation is essential Often changes or issues are found during the validation process. This is preferable and much less costly to being surprised by problems at the end of the project. Scope issues can be corrected quickly before their effects are propagated to the end result. © Proj3ctS - Dries Vandevyvere - 2024 Project scope management Business need Collect data Define scope Validate scope Control Control scope scope © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope: scope change management 1. Identify the need 6. Adapt 2. Evaluate project scope impact 5. Track overall 3. Prepare changes scope change 4. Approve scope change © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope What? Any change requested by the customer/user; Missing (forgotten) deliverables or tasks Development of business need, design, … When? After scope validation, because before it is taken into the initial study Can occur in each stage of the project: Engineering – e.g., something forgotten in engineering Procurement – e.g., good idea from a quoting party (contractor) Execution – e.g., site situation that was misjudged or changed, requesting an adapted technical solution Commissioning – e.g., extra support requested for commissioning © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope Formal (RfC = request for change) or informal (scope creep or goldplating) Consider the impacts Schedule Budget Quality Safety Organization and resources The exact procedure is described in a scope change procedure, What is considered as a scope change Who can introduce a scope change? The procedure to follow from request till approval The authority level for approval & conditions under which each authority level can approve a scope change At this point we know if we would approve or decline this change => COMMUNICATE! Understand change request & its impacts Explain to customer/steerco why change should be accepted & why the impacts are what they are © Proj3ctS - Dries Vandevyvere - 2024 Control the scope: Gold-plating & scope creep Gold plating Occurs when a project manager or team member (so: internal) believes that a project could be enhanced by an additional feature and includes it without approval. Moves the project beyond the originally scope and has potential negative effects Potential negative effects include: Extending the time or budget that to complete the project Wasting money and time when the team has to remove or correct additions Dissolving trust among stakeholders who no longer feel confident that specific instructions will be followed Scope creep and gold-plating both mean going outside the scope baseline Gold-plating is the result of choices made by the project manager or team, while scope creep refers to additions initiated by the client (external of the project team) In scope creep, a client or user may intentionally or unintentionally increase the workload ▪ While it’s common for users or clients to make additional requests during a project, scope creep occurs when there is no adjustment to the project plan that is being completed. ▪ Thus, the project team is doing extra work without receiving any additional budget or time © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope: Hints & Tips Keep track of ALL (incl. rejected) scope change requests It is important to RECOGNIZE scope changes, to avoid SCOPE CREEP Unofficial scope changes Stakeholders are not aware Impact not estimated but impact on final project result ‘Bad surprise’ at the end of the project: Budget overrun, Schedule slippage, More effort required Update all key project documents = new scope baseline Project Description Schedule – new baseline Budget © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope: Hints & Tips Do not accept scope change that sneaked into the project, without formal approval Kill it immediately! It is a plague that cannot be stopped. You will lose control over your project. Dirty trick: answer any scope change request with “denied”. It will make them think twice before entering the next request ☺ Never approve a scope change request without the impact on scope, budget, schedule, quality and safety Another trick: Make the change requester fill in the scope change template Start your project with complete requirements © Proj3ctS - Dries Vandevyvere - 2024 Control the scope: completion of deliverables Depending on the approach used, there are different ways to describe component or project completion: Acceptance or completion criteria: The criteria to be met before the customer accepts the deliverable or before the project is considered complete are documented in a scope statement. Technical performance measures: The technical specifications for a product may be documented in a specifications document, or as an extension to the WBS. This extension, known as a WBS dictionary, elaborates the information for each deliverable in the WBS. Definition of done. The definition of done is used in agile. It is a checklist of all criteria required so that a deliverable can be considered ready for customer use. Scope verification should happen at least at the end of each phase of the project. © Proj3ctS - Dries Vandevyvere - 2024 Control the Scope: Acceptance criteria Project Acceptance Criteria Include performance requirements and essential conditions, which must be met before project deliverables are accepted Set out the specific circumstances under which the user will accept the final output of the project Can measure, achieve, and prove that work is complete Acceptance criteria are documented in the requirements document and the Project scope statement. Acceptance criteria are an important part of contractual agreements on external projects Importance: Set the right expectations with stakeholders Avoid miscommunication & create clarity Determines success (getting paid or not) on a project © Proj3ctS - Dries Vandevyvere - 2024 Agenda - Covered in these slides Introduction What is a project? How does project management work? Why does it matter? Stakeholder management Change management + communication Team motivation Scope management How to define scope How to manage Wrap-up + Q&A © Proj3ctS - Dries Vandevyvere - 2024 Wrap-up What have you learned today © Proj3ctS - Dries Vandevyvere - 2024 Q&A © Proj3ctS - Dries Vandevyvere - 2024 APPENDIX © Proj3ctS - Dries Vandevyvere - 2024 Reference material Project Management Body of Knowledge (PMBOK) - PMI [not included] Lexicon Additional material 1. What is Project Management? - PMI 2. Process group and knowledge area mapping - https://www.deepfriedbrainproject.com 3. Project Performance Domains - PMI 4. Project relationships and the Stakeholder Circle - PMI 5. Integrated change management - PMI 6. Motivation: how to increase project team performance - PMI 7. Project Success Quick Reference Card - CHAOS 2020: Beyond Infinity Overview 8. Project Scope Management according to the PMBOK - https://www.projectengineer.net/ 9. Scope: mastering the Fuzzy Constraint - PMI 10. Scope change control - PMI 11. Top Five Causes of Scope Creep - PMI © Proj3ctS - Dries Vandevyvere - 2024