Skip to main content
Workforce LibreTexts

5.2: Plan of Attack

  • Page ID
    52110
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \(\newcommand{\longvect}{\overrightarrow}\)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

      

    Plan of Attack: Schedule, Cost Estimation, and Budget

    This milestone takes your project from strategic vision to operational readiness. You will now develop a complete project schedule, estimate costs across all relevant dimensions, and build a scalable budget model for the rollout of C-Bay’s loan services franchise system.

    In this phase, professionalism, clarity, and feasibility matter more than ever. Your stakeholders need more than ideas—they need structure, confidence, and data. Your job is to give it to them.

    Step 1: Create a Detailed Project Schedule

    A project schedule is not just a list of tasks—it’s a structured timeline that guides execution, aligns teams, and enables stakeholders to monitor progress. In this step, your team will create a professional-grade project schedule for C-Bay’s franchise rollout, complete with tasks, milestones, dependencies, durations, and role assignments.

    This schedule should reflect the logic, structure, and realism of a true implementation plan.

    Objectives

    Your schedule should enable you to:

    • Identify key milestones that mark project phases
    • Break those milestones into detailed tasks using a Work Breakdown Structure (WBS)
    • Define and document each task in a WBS Dictionary
    • Identify dependencies using predecessor logic
    • Estimate the duration of each task (in business days or weeks)
    • Assign team roles or resources to each task
    • Apply scheduling techniques (e.g., Critical Path, float, lag/lead times)
    • Create a visual timeline (Gantt chart optional but encouraged)

    Step-by-Step Instructions

    1. Define Major Milestones
    Start by identifying 5–8 key milestones that structure your project. These are high-level events like:

    • “Franchise Playbook Complete”
    • “Training Materials Approved”
    • “Pilot Franchise Launched”

    Each milestone should have a clear outcome and delivery point.

    2. Break Down Each Milestone into Tasks (WBS)
    Create a Work Breakdown Structure (WBS) that shows how the work under each milestone is divided. Use levels like:

    • 1.0 Franchise Playbook

      • 1.1 Research best practices
      • 1.2 Draft core materials
      • 1.3 Peer review and revision
      • 1.4 Final formatting and delivery

    Structure the tasks hierarchically so it’s clear what’s part of what.

    3. Build a WBS Dictionary
    In a second worksheet or tab, define each task using the following fields:

    • Task Name
    • Description
    • Deliverable or Outcome
    • Success Criteria
    • Assigned Role
    • Dependencies
    • Notes/Risks

    This ensures clarity and prevents confusion later.

    4. Assign Dependencies (Predecessors)
    Specify which tasks must be completed before others can begin. This creates a logical flow for the project and supports later Critical Path analysis.

    5. Estimate Task Durations
    For each task, estimate the time required in business days or weeks. Use team input, expert judgment, or analogy to prior projects.

    6. Assign Resources or Roles
    Assign each task to a responsible role (not just a person). Examples:

    • Project Manager
    • Training Coordinator
    • Vendor Team Lead
    • Documentation Specialist

    Avoid unassigned tasks. Accountability is key.

    7. Apply Scheduling Logic
    Use standard scheduling tools and principles to validate your plan:

    • Identify the Critical Path (tasks that drive total project duration)
    • Calculate slack/float for flexible tasks
    • Add lag or lead time where tasks overlap or have gaps
    • Optionally, baseline your schedule for future comparison

    8. Format and Finalize Your Schedule
    Use a tool like Google Sheets, Excel, ProjectLibre, or MS Project. Your schedule should be formatted clearly, with:

    • WBS ID numbers
    • Task names
    • Start/End dates or durations
    • Predecessors
    • Roles
    • Milestone flags

    Include a Gantt chart if your tool supports it. Visuals help communicate progress and flow.

    Deliverable: Project Schedule

    Submit your completed schedule as:
    It should include:

    CBay_ProjectSchedule_TeamX.xlsx

    • WBS task list
    • Clearly marked milestones
    • Assigned roles
    • Task durations or start/end dates
    • Dependency logic
    • A separate WBS Dictionary tab
    • Optional Gantt chart or timeline visualization

    This is your operational roadmap. Build it with precision and professionalism.

    Step 2: Estimate Project Costs

    Once your schedule is complete, the next step is to estimate what it will cost to carry out your plan. Cost estimation translates your strategy into financial reality. A strong cost estimate gives stakeholders visibility into what it takes to build and scale C-Bay’s franchise system—and how investment decisions affect outcomes.

    Objectives

    Your cost estimation should:

    • Identify all major cost categories tied to the project scope
    • Distinguish between one-time, recurring, and per-unit costs
    • Break down costs by project phase or functional area
    • Use structured formulas and assumptions in a spreadsheet format
    • Provide multiple scaling models (e.g., for 10, 100, and 1,000 franchises)
    • Lay the groundwork for your final budget narrative

    Step-by-Step Instructions

    1. Open a New Spreadsheet
    Name your file: CBay_CostEstimates_TeamX.xlsx
    Set up your table with these columns:

    • Item Description
    • Cost Category (e.g., Personnel, Training, Legal, Tools)
    • Unit Type (e.g., hour, license, document)
    • Quantity
    • Unit Cost
    • Total Cost (use a formula)
    • Notes/Assumptions

    2. Identify Key Cost Areas
    Start with broad, high-impact categories such as:

    • Personnel (Project managers, trainers, developers, SMEs)
    • Training content development
    • IT tools/platform licenses
    • Vendor services (CRM consultants, onboarding partners)
    • Legal/compliance documentation and review
    • Support or customer service infrastructure

    3. Estimate Quantities and Rates
    For each line item, determine:

    • How many units/hours are needed
    • The standard rate or cost per unit
    • How long the resource will be used
      • Use research, analogies from real companies, or expert judgment.

    4. Build Cost Formulas
    Use formulas to compute totals:
    Total Cost = Quantity × Unit Cost
    Group items by category and subtotal each section. Include a grand total at the bottom.

    5. Tag One-Time vs. Recurring Costs
    Use a color code or add a column for cost type:

    • One-Time Setup (e.g., training development)
    • Recurring (e.g., support staff, licenses)
    • Per-Unit (e.g., cost per franchisee)

    6. Annotate Assumptions
    Use the “Notes” column to explain:

    • Where your data came from
    • Any uncertainties or ranges
    • Planning constraints (e.g., “assumes batch rollout of 100 franchises”)

    7. Run Roll-Up Totals for Different Scenarios
    Use separate subtotal rows to show:

    • Cost to launch 10 franchises
    • Cost to scale to 100 franchises
    • Cost to operate at 1,000 franchises
      • This demonstrates scalability and helps leadership compare rollout paths.

    8. Review with Your Team and Adjust
    Walk through the entire workbook with your teammates:

    • Are all critical costs represented?
    • Are there overlaps or missing items?
    • Are your assumptions consistent across sections?

    Make adjustments as needed for clarity, realism, and completeness.

    Deliverable: Cost Estimation Workbook

    Submit your spreadsheet as: CBay_CostEstimates_TeamX.xlsx

    Your final workbook should include:

    • Clear structure with labeled rows and columns
    • All major cost categories represented
    • Totals, formulas, and grouped cost summaries
    • Notes and assumptions for transparency
    • Scenarios for small-scale, mid-scale, and full-scale rollout
    • Professional formatting ready for stakeholder review

    Step 3: Build the Budget Narrative and Scaling Plan

    Once you’ve built your cost estimate, it’s time to move from spreadsheet to strategy. A budget isn’t just a table of numbers—it’s a story about how your plan turns investment into outcomes. This step challenges you to explain your financial model, justify your assumptions, and demonstrate how C-Bay can scale its franchise system responsibly.

    Objectives

    In this step, you will:

    • Translate your spreadsheet into a readable, professional budget narrative
    • Highlight the key cost drivers that shape your plan
    • Model different franchise rollout scenarios (e.g., pilot vs. full-scale)
    • Justify assumptions with logic and references
    • Prepare materials that are presentation-ready for stakeholders

    Step-by-Step Instructions

    1. Write a Budget Narrative
    Craft a 1–2 page write-up that explains your financial plan. Include:

    • Total projected budget and what it covers
    • Major cost categories (e.g., staffing, tools, training, support)
    • Timeline alignment: how the budget supports the delivery phases
    • Cost types: which are one-time, recurring, or per-unit
    • Risks, constraints, or uncertainties that may impact cost

    Think of this as an executive briefing: professional, concise, and confident.

    2. Justify Key Assumptions
    Clearly state 4–6 assumptions that shaped your cost model. Examples:

    • “Training costs are centralized and amortized across all franchisees.”
    • “Support will be outsourced for the first 100 franchises.”
    • “CRM subscription is flat-rated for the first 500 users.”

    For each, explain:

    • Where the assumption came from (e.g., market research, benchmark, estimate)
    • What happens if the assumption changes

    3. Model Rollout Scenarios
    Your cost spreadsheet should include comparative models for:

    • Pilot Launch (e.g., 10 franchises)
    • Mid-Scale Expansion (e.g., 100 franchises)
    • Full-Scale Rollout (e.g., 1,000+ franchises)

    Include columns for:

    • Total cost
    • Cost per franchise
    • Notes on scalability, risks, and savings opportunities

    This helps stakeholders understand the cost trajectory as C-Bay grows.

    4. Highlight Trade-Offs and Strategic Choices
    Show where your team made thoughtful decisions:

    • Did you invest heavily up front to reduce support long term?
    • Did you choose flexibility over cost when selecting vendors?
    • Are you staging your rollout to control early investment?

    This is where you demonstrate your maturity as project leads.

    5. Format for Executive Review
    Write your document using a clean, scannable layout:

    • Use section headers and bolded keywords
    • Keep paragraphs short and purposeful
    • Add white space and optional summary table at the end

    File name: CBay_BudgetNarrative_TeamX.docx

    Optional: Executive Presentation Slides

    If time allows, prepare 3–5 slides that visualize your:

    • Budget summary
    • Key cost drivers
    • Rollout scenario comparisons
    • Assumptions and trade-offs

    Use clear charts, bold visuals, and simple language.
    File name: CBay_BudgetPresentation_TeamX.pptx

    This is your chance to translate complexity into clarity. A great budget narrative doesn’t just explain costs—it builds trust. Show your audience that your plan is ready to lead C-Bay into scale.

    Final Deliverables for Chapter 3

    Final Delverables for Chapter 3
     File Description
    CBay_ProjectSchedule_TeamX.xlsx Full work breakdown and schedule view
    CBay_CostEstimates_TeamX.xlsx Detailed line-item and roll-up cost estimates
    CBay_BudgetNarrative_TeamX.docx Written justification and scaling model
    CBay_BudgetPresentation_TeamX.pptx (Optional) Executive summary of cost and budget plan

    You are no longer just project planners. You are now operating like project leads. Deliver work that reflects that standard. 


    5.2: Plan of Attack is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?