Major Project-I (EX-706) - Unit 2 Short Notes

2.0 Project Planning & Design: From Concept to Actionable Blueprint

Purpose: To transform the approved project proposal (from Unit 1) into a comprehensive, integrated, and actionable roadmap. It defines how the project will be executed, monitored, controlled, and closed. Key Deliverable: The Project Management Plan (PMP) – a formal, approved document that consolidates all subsidiary plans.

[!TIP] Exam Focus: Be prepared to differentiate between the Project Proposal (justification, high-level scope, feasibility) and the Project Management Plan (detailed how-to guide for execution).

2.1 Defining and Structuring Project Scope

Objective: To clearly define and document the specific work required to deliver the project's intended outcomes.

2.1.1 Requirements Gathering & Analysis

• Stakeholder Interviews & Workshops: Direct engagement to elicit needs and expectations.

• Document Analysis: Reviewing existing reports, standards, or legacy systems.

• Use Cases / User Stories: (For software/design projects) Describing functionality from an end-user perspective.

2.1.2 Scope Statement Development

A formal document including:

• Project Justification & Objectives: SMART (Specific, Measurable, Achievable, Relevant, Time-bound) goals.

• Deliverables: Tangible (e.g., prototype, report) and intangible (e.g., trained staff, improved process).

• Boundaries & Exclusions: Explicitly state what is OUT of scope to prevent scope creep.

• Constraints: Limitations (budget, deadline, resources).

• Assumptions: Factors considered true for planning (e.g., "key personnel will be available").

2.1.3 Work Breakdown Structure (WBS)

A hierarchical decomposition of the total scope of work into manageable work packages.

• Principle: 100% Rule – The WBS must include 100% of the project's scope.

• Structure: Typically 3-5 levels (e.g., Project → Major Deliverables → Sub-Deliverables → Work Packages).

• WBS Dictionary: Companion document detailing each work package (description, responsible party, schedule, cost, quality requirements).

• Control Account: A management control point where scope, budget, and schedule are integrated and measured.

[!TIP] Common Pitfall: Creating a WBS that is too high-level (not decomposable) or too detailed (micromanagement). The lowest level should be a work package that can be realistically estimated and assigned.

2.2 Project Scheduling & Time Management

Objective: To sequence activities, estimate durations, and develop a realistic project schedule.

2.2.1 Activity Definition & Sequencing

• Activities: Defined from WBS work packages.

• Sequencing: Using Precedence Diagramming Method (PDM) relationships:

  • FS (Finish-to-Start): Most common. B cannot start until A finishes.

  • SS (Start-to-Start), FF (Finish-to-Finish), SF (Start-to-Finish).

• Leads & Lags: Time adjustments to relationships (e.g., "Start A + 2 days" = lag).

2.2.2 Duration Estimating

• Analogous: Using historical data from similar projects (fast, less accurate).

• Parametric: Using a statistical relationship (e.g., cost per line of code).

• Three-Point (PERT):

$$ \text{Expected Duration (TE)} = \frac{O + 4M + P}{6} $$

where O=Optimistic, M=Most Likely, P=Pessimistic.

• Expert Judgment: Consulting subject matter experts.

2.2.3 Schedule Development (Critical Path Method - CPM)

Calculating Early Start (ES), Early Finish (EF), Late Start (LS), Late Finish (LF).

• Forward Pass: Calculates ES/EF (earliest possible times).

• Backward Pass: Calculates LS/LF (latest allowable times without delaying project).

• Float/Slack:

$$ \text{Total Float} = LS - ES \quad \text{or} \quad LF - EF $$

• Critical Path: Longest path through the network with ZERO total float. Any delay here delays the project.

2.2.4 Schedule Presentation & Control

• Project Network Diagram: Visual representation of activity sequence.

• Gantt Chart: Bar chart showing activities vs. time, often with dependencies.

• Milestone Chart: High-level view of major deliverables/events.

• Baseline Schedule: The approved version of the schedule against which performance is measured.

[!TIP] Exam Calculation: You may be asked to perform a forward/backward pass on a small network diagram. Always draw the network first. Remember: Critical Path = longest duration path with zero float.

2.3 Project Resource & Cost Planning

2.3.1 Resource Planning

• Identifying Requirements: Human (skills, roles) and physical (equipment, materials).

• Resource Breakdown Structure (RBS): Hierarchical list of resources by type.

• Resource Allocation & Leveling: Assigning resources to activities and resolving over-allocations (delaying non-critical tasks).

• Responsibility Assignment Matrix (RAM) / RACI Chart:

  | Task | Responsible | Accountable | Consulted | Informed | | :------------- | :-------------- | :-------------- | :------------ | :----------- | | Develop FRD | Analyst | PM | Stakeholders | Dev Team |

2.3.2 Cost Estimating

• Analogous & Parametric: (As in scheduling).

• Bottom-Up: Estimating costs of individual work packages and summing (most accurate, most time-consuming).

• Vendor Bid Analysis: Using quotes from potential sellers.

2.3.3 Budgeting & Cost Baseline

• Aggregating Costs: Summing activity costs to create the project budget.

• Time-Phased Budget (Cost Baseline): The approved, time-distributed budget (S-curve). It is the scope baseline + schedule baseline expressed in monetary terms.

• Funding Requirements & Cash Flow: Projecting when funds will be needed.

2.4 Risk Management Planning

2.4.1 Risk Management Plan

Defines the methodology, roles (e.g., Risk Owner), budgeting, timing, and reporting formats for risk management.

2.4.2 Risk Identification

• Techniques: Brainstorming, Delphi technique, SWOT analysis, Checklists, Assumption Analysis.

• Output: Risk Register – a living document listing all identified risks, their characteristics, and potential responses.

2.4.3 Qualitative & Quantitative Risk Analysis

• Qualitative: Assessing Probability (P) and Impact (I) of risks (e.g., 1-5 scale). Plotting on a Probability/Impact Matrix to prioritize.

• Quantitative:

  • Expected Monetary Value (EMV):

$$ \text{EMV} = \text{Probability} \times \text{Impact (in monetary terms)} $$

*   **Sensitivity Analysis (Tornado Diagram):** Identifies risks with the greatest potential impact on project objectives.

2.4.4 Risk Response Planning

• For Threats (Negative Risks):

  • Avoid: Eliminate the threat.

  • Transfer: Shift ownership (e.g., insurance, warranty).

  • Mitigate: Reduce probability or impact.

  • Accept: Acknowledge and budget/plan for it (active or passive).

• For Opportunities (Positive Risks):

  • Exploit: Ensure opportunity occurs.

  • Share: Allocate ownership to a third party best able to capture it.

  • Enhance: Increase probability or impact.

  • Accept: No active pursuit.

[!TIP] Key Distinction: Avoid (change plan to eliminate risk) vs. Mitigate (reduce impact/probability within current plan). Exploit (guarantee gain) vs. Enhance (increase chance/gain).

2.5 Quality, Communication, and Stakeholder Engagement Plans

2.5.1 Quality Planning

• Identify applicable quality standards (ISO, industry-specific).

• Define quality metrics (e.g., defect density, test coverage, customer satisfaction score).

• Plan quality assurance (process-oriented) and quality control (product-oriented) activities.

2.5.2 Communications Planning

• Stakeholder Communication Requirements: Who needs what information?

• Communication Matrix:

  | Info | To Whom | By Whom | When/Frequency | How/Method | | :------------ | :------------ | :---------- | :----------------- | :--------------- | | Status Report | Sponsor, PMO | Project Mgr | Weekly | Email + Meeting |

• Format: Reports, meetings, presentations, dashboards.

2.5.3 Stakeholder Engagement Planning

• Stakeholder Register & Analysis: Assess power, interest, influence, impact.

• Engagement Strategies: Plan how to communicate, manage expectations, and involve key stakeholders throughout.

• Managing Challenging Stakeholders: Tailor strategies (e.g., high power/low interest → Keep satisfied).

2.6 Procurement & Vendor Management Planning (If Applicable)

2.6.1 Make-or-Buy Analysis

Decision on whether to perform work internally or procure from external sources.

2.6.2 Procurement Management Plan

Describes how procurement will be managed (process, roles, contract types).

2.6.3 Statement of Work (SOW) for External Vendors

Detailed description of the work to be procured, including deliverables, timeline, and performance criteria.

2.6.4 Source Selection Criteria

Metrics used to evaluate vendor proposals (price, technical capability, past performance, delivery schedule).

2.7 Integration & Finalization of the Project Management Plan

2.7.1 Consolidation

All subsidiary plans (scope, schedule, cost, quality, resources, communications, risks, procurement, stakeholder) are integrated into a cohesive Project Management Plan.

2.7.2 Baseline Establishment

• Scope Baseline: Approved WBS + WBS Dictionary.

• Schedule Baseline: Approved project schedule.

• Cost Baseline: Approved time-phased budget.

These baselines are the fixed reference points for measuring performance.

2.7.3 Plan Approval Process

• Formal sign-off from the project sponsor and key stakeholders.

• Configuration Management: Formal process for controlling changes to the baselines.

2.7.4 Plan Kick-off and Team Alignment

• Communicating the final, approved plan to the project team.

• Ensuring team members understand their roles, responsibilities, and the overall plan.

• Securing team commitment.

2.8 Documentation and Ethical Considerations

2.8.1 Structure of the Project Plan Document

Typical sections: Executive Summary, Project Scope, Schedule, Budget, Resource Plan, Risk Management, Quality, Communications, Procurement, Stakeholder Management, Approval Signatures.

2.8.2 Version Control & Document Management

System for tracking revisions (version number, date, author, change description). Ensures all stakeholders use the current version.

2.8.3 Ethical Planning Practices

• Realistic Estimating: Avoid padding (deliberate overestimation) or underestimation (to gain approval). Use objective techniques.

• Transparent Risk Disclosure: Fully communicate known risks to stakeholders.

• Fair Resource Allocation: Avoid bias in assigning personnel or equipment.

• Sustainability & Social Responsibility: Consider environmental and social impacts in planning decisions (e.g., material sourcing, community effects).

[!TIP] Ethical Red Flag: A plan with unrealistically aggressive deadlines or budgets to "sell" the project is unethical and leads to failure. Always plan based on realistic assumptions.