Project Management Handbook Section 1: Foundational Project Management & Organizational Context Definition & Project Life Cycles ● A project is a temporary, unique endeavor undertaken to produce a specific set of deliverables and achieve a defined outcome. ● Project management is the application of knowledge, skills, tools, and techniques to project activities to satisfy requirements. ● Traditional 4-Phase Life Cycle: Initiation (identifying goals, deliverables, resources, and budget), Planning (establishing workflows, timelines, and tools), Executing (carrying out the work), and Closing (evaluating performance and archiving documentation). ● Comprehensive 5-Phase Life Cycle: Initiation, Planning, Execution, Monitoring & Controlling (tracking baselines and adjusting variances in real time), and Closure. Organizational Structures, Governance & Culture ● Classic (Functional) Hierarchy: Traditional top-down operational structure where functional managers lead departmental reporting lines. ● Matrix Structure: Grid reporting model where project team members report simultaneously to a functional manager and a project/program manager. ● Project Management Office (PMO): An organizational department that standardizes and oversees project governance, policies, and practices. ● Corporate Governance: The internal systems, rules, and decision structures used to direct operations and achieve corporate goals. ● Organizational Culture: Shared behavioral norms, company values, and institutional personality that determine how change is adopted. ● Leadership Roles: ○ Project Manager (PM): Central leader responsible for guiding tasks, managing dependencies, and steering communication from kickoff to closure. ○ Program Manager: Oversees interrelated, coordinated projects across programs or business portfolios. ○ Change Agent: A leader who facilitates organizational transitions and optimizes internal effectiveness. ○ Influencing Without Authority: The ability to direct, motivate, and guide cross-functional contributors through trust, clear communication, and emotional connection rather than hierarchical management. ○ Conger’s Four Steps of Persuasion: A leadership framework based on establishing credibility, framing for common ground, providing compelling evidence, and connecting emotionally.

Section 2: Waterfall vs. Agile Delivery Frameworks Comprehensive Comparative Analysis Dimension Traditional Waterfall Agile Frameworks Philosophical Approach Linear, sequential, and predictable; each phase must conclude completely before the subsequent phase can begin. Adaptive, empirical, and iterative; overlapping cycles built to respond swiftly to changing circumstances. Operational Environment Stable projects with clear, non- negotiable scopes and predictable deliverables. Environments characterized by VUCA: Volatility, Uncertainty, Complexity, and Ambiguity. Project Manager Role Active operational leader who plans work, assigns tasks, enforces milestones, and tracks accountability. Servant-leader/Scrum Master acting as a facilitator and coach, removing roadblocks while the team self- organizes. Scope Management Fixed and heavily documented during initiation and planning; changes require formal approval through a Change Control Board. Adaptable and emergent; prioritized continuously in the backlog and modified iteratively through customer feedback. Work Schedule Sequential progression across project phases; managed via Critical Path schedules and Gantt charts. Timeboxed into fixed iterations or Sprints (typically 1 to 4 weeks) with dedicated sprint deliverables. Cost & Budget Locked upfront through bottom-up estimates; changes are controlled to prevent baseline budget variance. Flexible across iterations based on capacity, velocity, and evolving scope needs. Quality Management Standards, metrics, and acceptance criteria are fixed upfront; formal testing is executed after build phases conclude. Built-in quality through continuous testing, reviews, and ongoing user input throughout every iteration. Communication Cadence Formal periodic status reports, documentation handoffs, and executive milestone reviews. Transparent, continuous, and daily interaction; face-to-face communication is preferred.

Stakeholder Dynamics Managed by the PM to protect baseline scope and deliver final commitments according to original expectations. Direct, ongoing business collaboration; stakeholders demo working deliverables each sprint to shape subsequent work. Section 3: Project Initiation, Chartering & Stakeholder Alignment The Project Charter A foundational document authored during project initiation that formally authorizes the project, establishes operational guardrails, and provides an ongoing alignment reference for stakeholders. ● Project Summary: A concise, executive-level summary articulating why the project exists and what it intends to accomplish. ● S.M.A.R.T Goals: Target outcomes that are Specific, Measurable, Attainable, Relevant, and Time- bound. ● Deliverables: The tangible products, services, or technical components completed and handed over upon finish. ● Scope & Boundaries: Explicitly defining what is in-scope (agreed work) and what is out-of-scope (tasks excluded to prevent scope creep). ● Benefits & Business Case: Quantified cost-benefit analysis and strategic justifications (both tangible financial returns and intangible gains like customer satisfaction). ● Budget & Constraints: The financial allocations required to deliver the defined outputs within approved boundaries. Stakeholder Governance & Scope Negotiation ● Stakeholder Categorization: Primary/key stakeholders (directly invested decision-makers, including the project sponsor) vs. secondary stakeholders (indirectly impacted teams). ● Power-Interest Grid: ○ High Power / High Interest (Key Players): Manage closely, engage regularly, and secure active buy-in. ○ High Power / Low Interest (Context Setters): Keep satisfied and consult on major strategic shifts. ○ Low Power / High Interest (Informed Champions): Keep adequately informed and leverage their enthusiasm. ○ Low Power / Low Interest (Monitored Group): Monitor with minimal effort through routine status channels. ● RACI Matrix: Identifies who is Responsible for completing the task, Accountable for the final decision/outcome, Consulted for expert input, and Informed on progress. ● Scope Negotiation Principles: ○ Uncover core motivations (distinguishing budget restrictions, schedule compression, or personal visibility). ○ Say “no” without explicitly saying “no” by reframing constraints as clear trade-offs.

○ Separate people from the problem, anchoring discussions around objective criteria and historical project metrics. ○ Deliver win-win solutions by sharing constraints transparently and presenting multiple viable alternatives. Section 4: Planning, Estimation & Scheduling Mechanics Strategies for Getting Accurate Estimates To avoid common pitfalls like optimism bias and the planning fallacy, project teams rely on structured estimation tactics: ● Consult Subject Matter Experts (SMEs): Review task steps, technical requirements, and sub-steps directly with specialists to validate the scope of work. ● Research and Historical Benchmarks: Review case studies, news articles, and past project data to ground estimates in demonstrated timelines. ● Challenge Assumptions: Critically evaluate assumptions by assessing potential failure points and their schedule impacts. ● Three-Point Estimating Technique: Assess every task across three scenarios—Optimistic ($O$), Most Likely ($M$), and Pessimistic ($P$). ○ Beta / PERT Distribution: $$\text{Expected Duration} = \frac{O + 4M + P}{6} \quad \text{[cite: 2]}$$ ○ Triangular Distribution: $$\text{Expected Duration} = \frac{O + M + P}{3} \quad \text{[cite: 2]}$$ ● Relative Estimation & Sizing: Sizing complexity using comparative units (Story Points, T-shirt sizing: XS, S, M, L, XL) rather than guessing absolute hours. Scheduling & Network Diagrams ● Work Breakdown Structure (WBS): Hierarchical decomposition organizing the complete project scope into manageable deliverables, summary tasks, and subtasks. ● Task Dependencies: ○ Finish-to-Start (FS): Successor cannot start until the predecessor finishes. ○ Finish-to-Finish (FF): Successor cannot finish until the predecessor finishes. ○ Start-to-Start (SS): Successor cannot start until the predecessor starts. ○ Start-to-Finish (SF): Successor cannot finish until the predecessor starts. ● Critical Path Method (CPM): The longest operational sequence of dependent tasks that dictates the shortest possible project completion timeline. ○ Float (Slack): The duration non-critical tasks can slip without delaying project completion. ○ Forward & Backward Pass: Network analysis techniques calculating earliest possible start/finish dates and latest allowable start/finish dates. ○ Buffers: Strategic safety time inserted on specific tasks (task buffer) or at project completion (project buffer) to absorb variance.

Cost Engineering & Budget Baselines ● Direct vs. Indirect Costs: Direct costs tie directly to a specific deliverable (labor, specialized equipment); indirect costs represent shared overhead (office rent, utilities). ● CAPEX vs. OPEX: Capital expenditures for long-term physical/organizational assets vs. operating expenses for daily business continuity. ● Reserves: Contingency reserves manage identified and quantified risks in the risk register; management reserves absorb unexpected issues. ● Budget Baselines: Locking the approved expenditure baseline into the Project Management Baseline (PMB) to evaluate performance over time. Section 5: Risk Management & Quality Governance Risk Analysis & Mitigation ● Risk vs. Issue: A risk is an uncertain future event that could impact project outcomes; an issue is an active, realized problem requiring immediate attention. ● Probability and Impact Matrix: Prioritizes risks based on likelihood and severity to categorize exposure as low, medium, or high. ● Root Cause Analysis Tools: Cause-and-Effect (Fishbone) Diagrams and Decision Trees trace problems back to underlying drivers. ● The ROAM Technique: Strategy for addressing identified risks: Resolved, Owned, Accepted, or Mitigated. Quality Assurance (QA) vs. Quality Control (QC) ● Quality Planning: Establishing project quality benchmarks and defining how requirements will be satisfied. ● Quality Assurance (QA): Process-oriented reviews and systemic audits ensuring that operational workflows produce quality results. ● Quality Control (QC): Product-oriented technical inspections and testing designed to identify and fix defects in deliverables. Project Performance Evaluation ● Earned Value Management (EVM): ○ Cost Variance (CV): $$\text{CV} = \text{Earned Value (EV)} - \text{Actual Cost (AC)} \quad \text{[cite: 2]}$$ ○ Schedule Variance (SV): $$\text{SV} = \text{Earned Value (EV)} - \text{Planned Value (PV)} \quad \text{[cite: 2]}$$ ○ Cost Performance Index (CPI): $$\text{CPI} = \frac{\text{EV}}{\text{AC}} \quad \text{[cite: 2]}$$ ○ Schedule Performance Index (SPI): $$\text{SPI} = \frac{\text{EV}}{\text{PV}} \quad \text{[cite: 2]}$$ ● Project Closeout: Producing the Project Closeout Report, archiving historical records, evaluating

performance against baselines, and holding retrospectives. Section 6: Agile, Scrum & Complementary Frameworks Agile Manifesto Values & Themes ● The 4 Agile Values: 1. Individuals and interactions over processes and tools. 2. Working software over comprehensive documentation. 3. Customer collaboration over contract negotiation. 4. Responding to change over following a plan. ● The 4 Core Themes: 1. Value Delivery: Delivering working solutions early and often to create a steady value stream and gather fast feedback. 2. Business Collaboration: Partnering daily with business teams to remove operational silos. 3. Team Culture: Building supportive, psychologically safe, self-organizing environments at a sustainable pace. 4. Retrospectives: Regularly tuning and adjusting team behaviors to foster continuous improvement. The Scrum Framework ● Three Pillars: Transparency, Inspection, and Adaptation. ● Five Core Values: Commitment, Courage, Focus, Openness, and Respect. ● Three Core Roles: ○ Product Owner (PO): Defines product vision, prioritizes the Product Backlog, and maximizes the business value delivered. ○ Scrum Master: Facilitates ceremonies, coaches the team in Scrum practices, and removes blockers. ○ Development Team: Cross-functional team responsible for building the releasable product increment. ● Scrum Ceremonies: ○ Sprint Planning: Determines the Sprint Goal and builds the Sprint Backlog based on available team capacity. ○ Daily Scrum (Stand-up): 15-minute daily sync addressing three questions: What was completed yesterday? What will be done today? What impediments exist? ○ Sprint Review: End-of-sprint demo (up to 4 hours) inspecting completed product increments with stakeholders. ○ Sprint Retrospective: Team-focused meeting (up to 3 hours) evaluating people, processes, and tools to identify concrete improvements. ● Agile Artifacts & Measurement: ○ Product Backlog: An ordered list of features, tasks, and fixes maintained by the Product Owner. ○ Burndown Chart: Tracks completed tasks against time to show remaining effort in an iteration.

○ Velocity: The average amount of work (story points) a team completes within a single Sprint. ○ I.N.V.E.S.T.: Evaluates user stories to ensure they are Independent, Negotiable, Valuable, Estimable, Small, and Testable. ○ Product Increment vs. Minimum Viable Product (MVP): An increment is a tested, potentially releasable slice built each sprint; an MVP is a functional version built with minimal effort specifically to validate market learning, and may span multiple sprints. ○ Definition of Done (DoD): Mutually agreed checklist verifying that quality, technical, and testing standards are met before an increment can ship. Complementary Methodologies ● Kanban: Visual workflow method using columns (e.g., To Do, Doing, Done) and Work-in-Progress (WIP) limits to prevent bottlenecks and balance flow. ● Extreme Programming (XP): Engineering-focused agile method emphasizing Pair Programming, Continuous Integration/Refactoring, avoiding big design upfront, and writing tests before writing code. ● Lean Delivery: Eliminates operational waste across 5 principles: Define Value, Map Value Stream, Create Flow, Establish Pull, and Pursue Perfection. ● Lean Six Sigma: Combines Lean waste reduction with Six Sigma defect reduction using the DMAIC framework: Define, Measure, Analyze, Improve, and Control. ● DevOps: Cultural and operational movement combining software development and IT operations to accelerate delivery velocity and increase service reliability. Section 7: Scaling Agile & Enterprise Frameworks When initiatives grow beyond single cross-functional teams, organizations adopt scaling frameworks: ● Scaled Agile Framework (SAFe): Enterprise framework organizing teams into Agile Release Trains aligned directly to business value streams. ● Scrum of Scrums: Cross-team coordination forum where delegates from multiple Scrum teams meet to align dependencies, facilitated by a Scrum of Scrums Master. ● Large-Scale Scrum (LeSS): Extends standard single-team Scrum across multi-team products without added management layers (Basic LeSS up to ~50 people; LeSS Huge for larger groups). ● Disciplined Agile Delivery (DAD): A goal-driven hybrid framework combining Scrum, Kanban, XP, and Lean across four operational layers. ● The Spotify Model: Autonomy-focused structural model organizing individuals into Squads, Tribes, Chapters, and Guilds. ● Scaling Rules of Thumb: Focus on agile fundamentals before scaling, treat frameworks as adaptable guides, and avoid premature scaling to minimize administrative overhead. Section 8: Artificial Intelligence in Modern Project Management Core Concepts & Applications

● AI vs. Generative AI (Gen AI): AI handles predictive tasks like scheduling and data synthesis; Generative AI produces original text, code, risk logs, and summary artifacts. ● Life Cycle Use Cases: ○ Initiation: Drafting project charter components, summary statements, and initial S.M.A.R.T goals. ○ Planning: Brainstorming Work Breakdown Structures, generating task checklists, and identifying initial dependencies. ○ Execution & Closure: Auto-summarizing meetings, formatting retrospective action items, and drafting stakeholder status updates. ○ Risk Discovery: Brainstorming non-obvious operational, technological, and resource vulnerabilities. The T-C-R-E-I Prompting Framework A structured methodology for creating prompts that yield high-quality generative AI deliverables: ● T – Thoughtfully: Define the exact task, persona, and desired output format. ● C – Create: Provide operational context, constraints, and background details. ● R – Really: Supply reference materials, templates, and style examples. ● E – Evaluate: Critically review AI output for accuracy, gaps, and tone. ● I – Iterate: Refine inputs and prompt iteratively to polish the final output. Responsible AI Governance & Ethics ● Human-in-the-Loop: AI tools assist and accelerate work, but final accountability rests with human practitioners. ● Verification & Data Privacy: Inspect all generated claims and mathematical formulas for accuracy and bias; never input proprietary corporate data or Personally Identifiable Information (PII) into unauthorized public models. ● Transparency: Maintain open disclosure regarding where and how generative AI models are utilized in deliverables.