Foundational Project Planning Tools and Techniques
Core Planning Questions and Foundations
- Project planning relies on answering four foundational questions prior to initiating work:
- What has to be done?: Answered by the Work Breakdown Structure (WBS), which defines and breaks down the project scope into manageable tasks.
- When does each task happen?: Answered by Gantt charts, which sequence the work and plot tasks across a timeline.
- What will it cost?: Answered by the budget, which estimates and tracks financial spend across all tasks.
- What could stop us?: Answered by the risk management plan, which anticipates potential roadblocks and prepares mitigation responses.
- Primary goal and running example:
- Every planning tool applies to an 8-week company website launch project.
- Project Goal: Launch a redesigned company website in 8 weeks, on budget.
Planning Flow Process
- Project planning follows a sequential five-step flow:
- 1. Define Scope (WBS): Establish the complete scope of work required.
- 2. Sequence Work (Gantt Chart): Structure the identified tasks chronologically.
- 3. Estimate Cost (Budget): Calculate resource costs and contingency reserves for all tasks.
- 4. Plan for Risk (Risk Plan): Identify potential risks and define mitigation response strategies.
- 5. Assign People (Resources): Allocate specific personnel and working hours to execute the tasks.

- Definition: A Work Breakdown Structure (WBS) is a hierarchical breakdown of the total project scope into smaller, more manageable pieces of work.
- Core principles of a WBS:
- Top Down: Begins with the entire project at the top and subdivides it into major phases or deliverables.
- 100% Rule: Every level of the WBS must capture 100% of the work—no more and no less.
- Stops at Tasks: Decomposition continues until the elements are small enough to estimate, assign, and track accurately.
- Importance in project management:
- The WBS is typically the first planning tool constructed.
- All subsequent planning tools—including the Gantt chart, budget, risk management plan, and resource allocation—are organized around the tasks defined within the WBS.
- Hierarchy levels in the Website Launch example:
- Level 0 (The Project): 1.0 Website Launch
- Level 1 (Major Phases):
- 1.1 Design
- 1.2 Development
- 1.3 Content
- 1.4 Launch
- Level 2 (Individual Tasks):
- Under 1.1 Design: Wireframes, Visual mockups
- Under 1.2 Development: Build front-end, Build back-end
- Under 1.3 Content: Write copy, Source images
- Under 1.4 Launch: QA testing, Go live

- Definition: A horizontal bar chart that illustrates when each WBS task begins, its duration, and how tasks overlap over time.
- Structural components:
- Bars: Each horizontal bar represents a single task; the physical length of the bar corresponds directly to task duration.
- Timeline: The horizontal axis marks time progression in days, weeks, or months.
- Overlap: Bars displayed in parallel represent tasks occurring simultaneously.
- Dependencies: Indicated by arrows or sequential ordering, showing tasks that must complete before subsequent tasks can begin.
- Timeline structure for the 8-week Website Launch:
- Project Planning: Spans Week 0 to Week 1.
- Design Phase: Spans Week 1 to Week 3.
- Development Phase: Spans Week 2 to Week 6.
- Content Creation: Spans Week 2 to Week 5.
- Testing (QA): Spans Week 5 to Week 6.
- Launch: Spans Week 6 to Week 7$.\n\n\n\n# Tool 3: Budgeting\n\n- **Definition**: An estimate of the financial resources required to execute every task in the WBS, incorporating a buffer for unexpected expenditures.\n- Core budget categories:\n - **Labor**: Compensation for team members performing project work; typically represents the largest single line item.\n - **Materials & Tools**: Software licenses, hardware, equipment, or physical supplies necessary to complete deliverables.\n - **Overhead**: Indirect operational expenses such as web hosting, utility costs, or administrative support.\n - **Contingency Reserve**: A financial safety buffer—typically set at 5\%to15\% of total project cost—allocated specifically for known or anticipated risks.\n- Mathematical Budgeting Formulas:\n - Formula for individual task cost:\n \text{Task Cost} = \text{Estimated Hours} \times \text{Rate}\n - Formula for total project budget:\n \text{Total Budget} = \sum(\text{All Task Costs}) + \text{Contingency}\n- Process for budget calculation:\n - Estimates derive directly from the WBS by pricing each individual task, then aggregating (rolling up) totals by phase.\n- Budget allocation for the 8\text{-week} Website Launch:\n - **Total Project Budget**: \$20\,000\n - Breakdown by phase and line item:\n - **Design**: \$4\,000(20\% of total budget)\n - **Development**: \$9\,000(45\% of total budget; the largest line item, typical for build-heavy technical projects)\n - **Content**: \$2\,500(12.5\% of total budget)\n - **Testing**: \$1\,500(7.5\% of total budget)\n - **Launch / Marketing**: \$2\,000(10\% of total budget)\n - **Contingency**: \$1\,000(5\% of total budget; set aside in case a risk from the risk plan materializes)\n\n\n\n# Tool 4: Risk Management Plans\n\n- **Definition**: A dynamic living document that identifies potential project issues, evaluates their severity, and outlines actionable response plans.\n- Four-step risk management workflow:\n - **1. Identify**: Enumerate potential risks across technical, schedule, budget, or personnel categories.\n - **2. Assess**: Rate each identified risk based on its probability of occurrence and prospective impact.\n - **3. Plan a Response**: Formulate specific actions to **avoid**, **reduce**, **transfer**, or **accept** each risk.\n - **4. Monitor**: Continuously re-evaluate and update the risk management plan as project execution proceeds.\n- The Risk Matrix tool:\n - Plotted on a grid evaluating **Probability** (Low, Medium, High) against **Impact** (Low Impact, Medium Impact, High Impact).\n - Priority zones:\n - **Low Priority**: Minimal probability and low impact.\n - **Watch Closely**: Moderate probability or impact requiring ongoing monitoring.\n - **Act Now**: High probability and high impact requiring immediate mitigation action.\n- Assessed risks for the Website Launch:\n - **Missed launch deadline**: High Probability, High Impact (Action zone: **Act Now**).\n - **Scope creep**: Medium Probability, High Impact (Action zone: **Act Now** / Watch Closely).\n - **Budget overrun**: Medium Probability, Medium Impact (Action zone: **Watch Closely**).\n - **Server downtime at launch**: Low Probability, High Impact (Action zone: **Watch Closely**).\n - **Team member turnover**: Low Probability, Low Impact (Action zone: **Low Priority**).\n\n\n\n# Tool 5: Resource Allocation\n\n- **Definition**: The alignment of WBS tasks with designated team members, assigning exact working hours across specific time periods without causing workload over-allocation.\n- Resource allocation matrix for the 8\text{-week} Website Launch:\n - **Project Manager**:\n - Weeks 1–2:10\,\text{h}\n - Weeks 3–4:10\,\text{h}\n - Weeks 5–6:10\,\text{h}\n - Weeks 7–8:10\,\text{h}\n - **UI/UX Designer**:\n - Weeks 1–2:20\,\text{h}\n - Weeks 3–4:15\,\text{h}\n - Weeks 5–6:5\,\text{h}\n - Weeks 7–8:0\,\text{h}\n - **Developer**:\n - Weeks 1–2:5\,\text{h}\n - Weeks 3–4:25\,\text{h}(workloadincreasessharplyfrom5\,\text{h}to25\,\text{h} as development ramps up according to the Gantt chart timeline)\n - Weeks 5–6:25\,\text{h}\n - Weeks 7–8:10\,\text{h}\n - **Content Writer**:\n - Weeks 1–2:0\,\text{h}\n - Weeks 3–4:15\,\text{h}\n - Weeks 5–6:10\,\text{h}\n - Weeks 7–8:5\,\text{h}\n - **QA Tester**:\n - Weeks 1–2:0\,\text{h}\n - Weeks 3–4:0\,\text{h}\n - Weeks 5–6:10\,\text{h}\n - Weeks 7–8:15\,\text{h}$$

Synthesis of Project Planning Process
- Interconnected roles of the five planning tools:
- WBS: Defines what work needs to be accomplished.
- Gantt Chart: Sequences when tasks take place on a timeline.
- Budget: Calculates what every individual task will cost.
- Risk Plan: Prepares solutions for what could go wrong.
- Resource Allocation: Specifies who will execute the work and how many hours are required.
- Strategic value:
- Combined, these five tools transform an initial project concept into an executable plan for the team.
- They establish a clear baseline and benchmark against which actual progress can be evaluated throughout the project lifecycle.
Questions & Discussion
- Application phase:
- Practical execution involves applying all five foundational tools (WBS, Gantt Chart, Budget, Risk Plan, Resource Allocation) to individual project scenarios during hands-on workshop sessions.