Level 4 Project Management Official Study Guide Flashcards

Core Concepts and Definitions of Project Management

• Definition of a Project: According to the Association of Project Managers, a project is defined as "A unique, transient endeavour undertaken to achieve planned objectives, which could be defined in terms of outputs, outcomes or benefits."

• Projects vs. Operations: The fundamental difference lies in their nature. Operations are ongoing and repetitive, while projects are temporary and unique. It is crucial to distinguish between them to avoid managing modest activities as complex projects or failing to give significant initiatives the control they require.

• Temporal Considerations: The label "temporary" does not necessarily mean short-term. Some projects, like the Aswan High Dam completed in $1970$, take many years (e.g., $12$ years) and involve thousands of workers, yet remain projects because they have a specific end goal within an agreed timescale.

• The Iron Triangle: Every project is influenced by three primary factors: Quality (Scope), Cost, and Time. There is a constant trade-off between these.

  • Time Constraint: Increasing the time available (e.g., building a shed in $2$ days instead of $1$) may allow for higher quality (paint, glass windows).

  • Cost Constraint: Money might not be available to pay for the extra labor or materials required for higher quality.

  • Prioritization: Project managers must identify which dimension is the most important influence for a specific context (e.g., a fixed-price contract makes Cost paramount; an Olympic stadium makes Time paramount).

The Project Life Cycle: The IPECC Model

• The IPECC Framework: Projects generally follow a sequence of stages to manage evolving challenges. The IPECC model consists of five stages:

  • Initiation: The idea emerges, often to generate revenue or reduce costs. Key activities include creating the Business Case, defining the initial scope, and identifying potential risks. This stage typically culminates in a Project Initiation Document (PID).

  • Planning: Detailed documents are created, including the project plan, budget, and functional specifications. These are "baselined"—frozen and approved by senior management so that progress can later be measured against them.

  • Execution: Work commences. The project manager focuses the team on the original plan and specifications while managing day-to-day tasks.

  • Control: Progress is tracked against the baseline. Differences between planned and actual progress are identified quickly. This involves monitoring risks and managing "Scope Creep" (the increase in deliverables or requirements).

  • Completion (Closing): The final stage involves delivering products to clients, evaluating the experience, and documenting "lessons learned"—both positive and negative—to improve future projects.

• Alternative Life Cycle Models:

  • Meredith and Mantel: A three-stage model focusing on risk and quality management.

  • Maylor: A four-stage model providing an overview of activity phases.

  • Frigenti and Cominos: A five-stage model used to define processes clearly.

The Project Business Case and Financial Metrics

• Purpose of a Business Case: To justify a project by demonstrating that future benefits will exceed costs. It typically includes strategic, economic, commercial, financial, and management issues.

• The Project Sponsor: A senior manager who oversees the project, holds responsibility for the business case, acts as an advocate, and has the authority to approve funding.

• Financial Appraisal Techniques:

  • Return on Capital: Calculated by dividing total positive cash flows by total negative outgoings: $\text{Return on Capital} = \frac{\text{Total Benefits}}{\text{Total Investment}}$. For example, a return of $2.68$ means a $268\%$ return on investment.

  • Payback Period: The time required to recover the initial investment. The formula for a precise point is $Payback \, Period = A + (B/C)$, where $A$ is the last period with a negative cumulative cash flow, $B$ is the absolute value of that cumulative flow, and $C$ is the total cash flow in the following period.

  • Discounted Cash Flow (DCF) and Net Present Value (NPV): These accounts for the "time value of money"—the concept that a dollar today is worth more than a dollar in the future.

    • Discount Factor: The rate at which future money is reduced. For a $10\%$ rate ($0.10$), the denominator is $1.1$.

    • NPV Calculation: Future cash flows are divided by the discount factor for every year in the future: $NPV = \frac{\text{Cash Flow}}{(1 + r)^t}$.

    • Decision Criterion: A positive NPV indicates the project will repay the investment plus the cost of borrowing/capital.

Work Breakdown Structure (WBS)

• Definition: A work-oriented grouping of project elements in a graphical hierarchy used to subdivide the total work scope.

• Benefits: Simplifies complex projects (e.g., an offshore platform) by breaking them into manageable components and "Work Packages."

• Man-Hours: A measure of the work effort required, not the duration. For example, a project might require $379,000$ man-hours. By assigning an average cost per man-hour (e.g., $\$75$ for conceptual design, $\$40$ for construction), a high-level budget estimate can be generated (e.g., $\$16.7\,m$).

Project Risk Management

• The Five-Stage Process:

  1. Identify: Use experience and checklists to create a Risk Register (Risk Log).

  2. Assess Impact: Determine the potential effect on the project.

  3. Assess Likelihood: Determine the probability of occurrence.

  4. Response: Devise and implement strategies.

  5. Review: Revisit the process regularly.

• The Risk Log: A dynamic document including: Unique number, Type, Author, Date, Description, Likelihood, Severity, Countermeasures, Owner, and Status.

• Ranking Risk ($5 \times 5$ Matrix): Risks are prioritized by multiplying Likelihood ($1$ to $5$) by Impact ($1$ to $5$). High-likelihood/high-impact items (red zone) require immediate attention.

• Risk Responses:

  • Acceptance: Do nothing but continue monitoring.

  • Prevention: Take measures to stop the risk from occurring.

  • Reduction: Minimize the likelihood or the impact.

  • Transference: Shift the risk to a third party (e.g., insurance or contractors).

  • Contingency Planning: Prepare documented plans for if the risk occurs.

Project Planning and Network Diagrams

• The Five Steps of Planning:

  1. Identify separate tasks.

  2. Estimate time durations for each task.

  3. Identify the logical sequence (Predecessors).

  4. Construct the network diagram.

  5. Calculate project duration and critical paths.

• Network Diagrams: Use precedence notation (boxes for tasks, arrows for logic). They flow from left to right.

• Milestones: Significant events with a duration of $0$ days (e.g., "Contract Signed," "Site Operational").

• Critical Path Analysis (CPA): The longest path of tasks through a network.

  • Critical Tasks: Tasks on this path; any delay in these directly delays the project end date.

  • Float (Slack): The permissible delay for non-critical tasks that does not affect the total project duration.

• Advanced Scheduling:

  • Lag Time: A required delay between tasks (e.g., $5$ days for plaster to dry before painting).

  • Lead Time: An overlap where a succeeding task starts before the predecessor finishes.

Resource-Based Project Budgets

• Resource Categories:

  • Human Resources: Project team, delivery team, and contractors. Can be internal (seconded) or external (agency-hired).

  • Materials: Consumables like steel or cement, often managed by quantity surveyors.

  • Equipment and Premises: Tools, computers, or office space.

  • Financing for Subcontracts: Specialized work packages externalized to experts.

• Budgeting Types:

  • Bottom-Up: Calculating the cost for every individual task and totaling them. Provides high detail and control.

  • Top-Down: A budget cap is imposed from the start (e.g., $\$3.5\,m$ limit). The manager must still use bottom-up details to verify if the cap is realistic.

• Resource Costs:

  • Time-based: Proportional to duration (e.g., $\$130/day$ for a consultant).

  • Fixed-cost: Lump sums for materials or equipment regardless of time.

Tracking and Controlling Live Projects

• Progress Tracking Process:

  1. Create baseline plan/budget.

  2. Update plan weekly with progress and actual costs.

  3. Perform formal quality reviews.

  4. Compare baseline to updated plan (Variance analysis).

  5. Implement strategies to address variances.

• Measuring Progress:

  • Status Values: Not started ($0\%$), In progress, Complete ($100\%$).

  • Percent Complete: Assessing the actual work done (e.g., an engineer reporting $90\%$ completion).

• Cost Variance Analysis: Measuring the difference between "Expected Spend" (Budget $\times$ Actual $\%$) and "Actual Spend." If Expected Spend is $\$25.1\,m$ but Actual Spend is $\$42.7\,m$, the variance is -\17.6\,m (overspent).

• Recovering Lost Progress:

  • Crashing: Adding extra resources to critical tasks. Note: Subject to diminishing returns and increased costs.

  • Redeployment: Moving the most talented staff to the most difficult tasks.

  • Scope Change: Renegotiating project deliverables with the sponsor.

  • Outsourcing: Engaging subcontractors for specific work packages.

• Software Systems (e.g., Microsoft Project): Assist in planning (CPA, start/finish dates), resource optimization, "what-if" analysis, and generating high-quality graphical reports (Gantt charts).