Project Management Basics: Developing a Project Plan

Course Logistics and Schedules

MCI Lecture Schedule

  • Lesson 1: 11 May | 08:30−11:1008:30-11:10 | Location: H2.13

  • Lesson 2: 18 May | 11:20−14:0011:20-14:00 | Location: H1.12

  • Lesson 3: 19 May | 11:20−14:0011:20-14:00 | Location: H2.13

  • Lesson 4: 21 May | 08:30−11:1008:30-11:10 | Location: H2.13

  • Lesson 5: 1 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 6: 4 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 7: 8 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 8: 10 June | 08:30−11:1008:30-11:10 | Location: H2.13

IBA Lecture Schedule

  • Lesson 1: 12 May | 11:20−14:0011:20-14:00 | Location: H2.13

  • Lesson 2: 13 May | 08:30−11:1008:30-11:10 | Location: H2.13

  • Lesson 3: 18 May | 14:20−17:0014:20-17:00 | Location: H1.12

  • Lesson 4: 21 May | 11:20−14:0011:20-14:00 | Location: H2.13

  • Lesson 5: 2 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 6: 3 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 7: 9 June | 08:30−11:1008:30-11:10 | Location: H1.12

  • Lesson 8: 11 June | 08:30−11:1008:30-11:10 | Location: H1.12

Overview of the Planning Phase

Key Components of a Project Plan

  • Project Charter: The initiating document establishing the project.

  • Stakeholder Analysis: Identification and assessment of parties involved.

  • Structures: Deliverables Breakdown Structure (DBS) and Work Breakdown Structure (WBS).

  • Project Organisation: Definition of roles, responsibilities, and team structure.

  • Project Schedule: Timeline for milestones and tasks.

  • Risk Analysis: Identification of potential threats and mitigation strategies.

  • Budget: Financial planning for the project.

The PM² Planning Phase Workflow

  • Initiating Transition: The phase begins after the "Ready for Planning" (RfP) milestone.

  • Kick-Off Meeting: Includes a formal Agenda and Minutes of Meeting (MoM).

  • Process Tailoring: Adjusting the PM² process to fit specific project needs.

  • Role Assignment: Formalizing responsibilities within the team.

  • Outputs (Artefacts):

    • Project Handbook: Contains roles, responsibilities, management plans, and requirements management.

    • Project Stakeholder Matrix: Mapping of all stakeholders.

    • Project Work Plan: Detailed schedule and task breakdown.

    • Transition Plan and Business Implementation Plan: Strategies for post-project handover.

  • Execution Transition: Ends with the "Ready for Executing" (RfE) milestone, signaling that all plans are distributed to stakeholders.

Project Scope Management

Core Definitions

  • Scope (PMBOK Definition): The sum of the products, services, and results to be provided as a project.

  • Product Scope: The features and functions that characterize a product, service, or result.

  • Project Scope: The specific work performed to deliver a product, service, or result with specified features. It is often viewed as encompassing the product scope.

The Project Scope Statement

  • Nature: A short description (1−21-2 phases) of project accomplishments, including major objectives, deliverables, and justification.

  • Evolution: First defined in the Business Case, elaborated in the Project Charter, and reaches final form in the Project Work Plan.

  • Key Elements:

    • Product Scope Description: Progressive elaboration of characteristics defined in the charter.

    • Acceptance Criteria: Conditions required for deliverable approval.

    • Deliverables: Unique and verifiable products or results, including ancillary items like management reports.

    • Project Exclusion: Explicitly stating what is out of scope to manage stakeholder expectations.

    • Constraints: Limiting factors affecting execution.

    • Assumptions: Factors considered true/certain without proof; requires analysis of the impact if proven false.

Breakdown Structures and Techniques

Work Breakdown Structure (WBS)

  • Definition: A hierarchical decomposition of the total scope to be carried out by the team. It is used for assigning work and estimating effort and cost.

  • Goal: To organize and define the total scope of the project.

  • Techniques for Breakdown:

    • Phases or stages.

    • Deliverables or outputs.

    • Work packages.

    • Organisational departments or business units.

  • 100 Percent Rule: The total work at the lowest levels must roll up to the higher levels so that nothing is omitted and no extra work is performed.

Deliverables Breakdown Structure (DBS)

  • Definition: Part of Product-Based Planning used to identify deliverables (physical, functional, or conceptual) and their interdependencies.

  • DBS vs. WBS:

    • DBS defines what the project will produce (outputs).

    • WBS defines how (the work/tasks needed to produce those outputs).

    • Identified outputs in the DBS are used to create the WBS.

WBS Creation Tools

  • Decomposition: The activity of dividing project scope into smaller, more manageable parts.

    • Work Package: The lowest level of WBS where cost and duration can be estimated.

    • Decomposition Steps: Identify deliverables, structure/organize the WBS, decompose upper levels, assign identification codes, and verify the degree of decomposition.

  • Expert Judgement: Using individuals/groups with relevant training or predefined templates (industry or discipline-specific) to break down scope.

  • Rolling Wave Planning: Waiting to develop WBS details for future components until they are sufficiently defined.

Project Scheduling and Sequencing

Schedule Modeling

  • Components: Time-based plan of milestones, activities, tasks, and deliverables with start/end dates linked by dependencies.

  • Baselining: Once approved, the schedule is baselined; further changes require formal change management and governance.

Precedence Diagramming Method (PDM)

  • Activity-on-Node (AON): Activities are nodes linked by logical relationships.

  • Predecessor: An activity preceding a dependent one.

  • Successor: A dependent activity following another.

  • Relationship Types:

    • Finish-to-Start (FS): Successor cannot start until predecessor finishes (e.g., race must finish before awards ceremony starts).

    • Finish-to-Finish (FF): Successor cannot finish until predecessor finishes (e.g., writing must finish before editing finishes).

    • Start-to-Start (SS): Successor cannot start until predecessor starts (e.g., pouring foundation must start before leveling concrete starts).

    • Start-to-Finish (SF): Successor cannot finish until predecessor starts (e.g., 1st shift cannot finish until 2nd shift starts).

Milestones vs. Deliverables

  • Milestone: A zero-duration checkpoint marking significant progress or a decision point (e.g., "Consortium agreement signed").

  • Deliverable: A tangible product or result (e.g., "Project Management Plan", "XR training modules").

  • Case Study Examples (TourXperience Project):

    • D1.1: Project Management Plan (Due Month 22).

    • D1.2: Progress report for EACEA month 3838 (Due Month 3838).

    • Milestone 1: Signature of Grant Agreement (Due Month 11).

    • Milestone 2: Platform ready for use (Due Month 77).

Visualization and Calculation Tools

  • Gantt Chart: A bar chart showing activities on a vertical axis and dates on a horizontal axis. Uses percent-complete shading and a "today" line to track status.

  • Critical Path Method (CPM): An algorithm calculating the longest necessary path of activities. This represents the shortest possible project duration.

  • Critical Chain Method (CCM): Similar to CPM but accounts for resource levelling and human behavior (e.g., "padding" estimates).

    • Buffers: Uses project, feeding, and resource buffers to manage schedule uncertainty instead of padded individual task estimates.