MOD 6: Project Management

Project

: A temporary endeavor undertaken to create a unique product, service, or result, characterized by having a defined beginning, a defined end, and specific scope constraints.

Project Management

: The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.

Project Life Cycle

: The series of phases that a project passes through from its initiation to its closure (typically: Initiation → Planning → Execution → Monitoring & Controlling → Closing).

Triple Constraint (Project Management Triangle)

: The foundational structural model stating that the quality of a project is constrained by three interdependent factors: Scope, Time, and Cost. Changing one automatically impacts the others.

Project Charter

: A formal, high-level document issued by the project initiator or sponsor that officially authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

WBS (Work Breakdown Structure)

: A deliverable-oriented, hierarchical decomposition of the total scope of work to be executed by the project team. It breaks the project down into manageable, bite-sized components.

Work Package

: The lowest, most granular level of a Work Breakdown Structure (WBS) where cost and activity duration can be reliably estimated and managed.

Scope Creep

: The uncontrolled, unauthorized expansion of product or project scope without adjustments to time, cost, and resources.

Network Diagram (Activity-on-Node / PDM)

: A visual schematic showing the sequential relationships, dependencies, and chronological flow of a project's tasks from start to finish.

Critical Path Method (CPM)

: A step-by-step project management technique that identifies the longest sequence of dependent tasks in a network diagram. This sequence determines the shortest possible duration to complete the project. Any delay on the critical path delays the entire project.

Float (Slack Time)

: The total amount of time that a specific project activity can be delayed without causing a delay to the subsequent tasks or the overall project completion date. Tasks on the Critical Path have a float of exactly zero.

Earned Value Management (EVM)

: A project management methodology that integrates schedule, costs, and scope measurements to assess project performance and progress.

PV (Planned Value)

: The authorized budget assigned to scheduled work.

EV (Earned Value)

: The measure of work actually performed expressed in terms of the budget authorized for that work.

AC (Actual Cost)

: The total cost actually incurred while performing work.

Cost Variance (CV) & Schedule Variance (SV)

: Performance indicators calculated as CV=EV−AC and SV=EV−PV. Negative values indicate the project is over budget or behind schedule.

CPI (Cost Performance Index)

: Efficiency ratio calculated as ACEV​.

SPI (Schedule Performance Index)

: Efficiency ratio calculated as PVEV​. (Value less than 1.0 means underperforming).

RAM / RACI Matrix

: A structural chart used to clarify team roles and responsibilities across deliverables, mapping who is Responsible (does the work), Accountable (approves the work), Consulted (provides input), and Informed (updated on progress).

Risk Management Plan

: The structured process of identifying, analyzing, and preparing proactive responses to potential project risks to minimize negative impacts.

Risk Response Strategies

: The standard treatments for handling threats:

Avoid

: Eliminate the threat entirely by changing the project plan.

Mitigate

: Reduce the probability or impact of the risk.

Transfer

: Shift the consequence of the risk to a third party (e.g., insurance, outsourcing).

Accept

: Acknowledge the risk but take no action unless it occurs.

RFP (Request for Proposal)

: A formal business document issued by an organization requesting bids from external vendors to procure software, hardware, or development services.

SOW (Statement of Work)

: A narrative description of the specific products, services, or results to be delivered by an external vendor under a procurement contract.

Stakeholder

: Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.

Technical Communication

: The practice of transmitting technical, complex data, processes, or instructions into clear, accessible information tailored to specific audiences (developers, stakeholders, or end-users).

Pyramid Principle

: A structured communication framework where the main conclusion, core recommendation, or answer is presented first, followed directly by a summary of supporting arguments and detailed data grouped logically below it.

MECE (Mutually Exclusive, Collectively Exhaustive)

: A structural grouping principle used to organize information. Data points or sub-problems must not overlap with one another (mutually exclusive), and together they must cover the entire scope of the problem without leaving any gaps (collectively exhaustive).

Executive Summary

: A short, high-level overview document summarizing the key findings, budgets, timelines, and conclusions of a massive technical report, explicitly designed for busy management stakeholders who do not have time to read the full brief.

KISS Principle (Keep It Simple, Stupid)

: A design and communication rule stating that systems and messages work best if they are kept simple rather than made complicated; avoiding unnecessary technical jargon when communicating with non-technical business partners.

SRS (Software Requirements Specification)

: A comprehensive, formal document that describes exactly what a software system is intended to do, its functional capabilities, and its operational performance constraints. This serves as the blueprint agreement between the client and the developers.

SDD (Software Design Description)

: A highly technical document that translates the requirements found in the SRS into a concrete technical architecture specification, detailing module structures, database schemas, interfaces, and exact low-level class structural designs.

UML (Unified Modeling Language)

: A standardized, visual modeling language used to specify, visualize, construct, and document the structural blueprints of software systems (e.g., Use Case diagrams, Class diagrams, Sequence diagrams).

Release Notes

: A concise document distributed alongside a new software build or update that details new features, bug fixes, operational patches, and known limitations for the end-user or deployment team.

API Documentation

: An instructional technical guide explaining exactly how to integrate with and consume a specific software API, detailing valid endpoints, expected request arguments, data formats (JSON/XML), and sample response outputs.