DECA / FBLA Review: Project Management Basics

FBLA/DECA – Project Management Basics

What This Is

Project Management Basics cover the planning, execution, monitoring, and closing of a project using standardized tools (e.g., Gantt charts, CPM, Agile sprints). For the FBLA/DECA exam you must demonstrate how to keep a project on?time, on?budget, and aligned with stakeholder goals. Real?world example: A school’s Business?Tech Club launches a “Student?Run E?Commerce Site” – they must define scope, schedule tasks, allocate a $2,500 budget, and report progress to the principal and sponsors.

Key Terms & Formulas

• Project Scope – The detailed description of deliverables, boundaries, and acceptance criteria; a scope creep warning sign.
• Work Breakdown Structure (WBS) – Hierarchical decomposition of the total project into manageable work packages.
• Critical Path Method (CPM) – Scheduling technique that identifies the longest sequence of dependent activities; Critical Path = longest path duration.
• Float (Slack) – The amount of time a non?critical activity can slip without delaying the project; Float = Late Start – Early Start.
• Earned Value (EV) – Budgeted cost of work actually performed; EV = %?Complete × BAC.
• Planned Value (PV) – Budgeted cost of work scheduled to be done by a given date; PV = (Time Elapsed / Total Duration) × BAC.
• Actual Cost (AC) – Real money spent to date on the project.
• Cost Variance (CV) – CV = EV – AC; positive CV = under budget.
• Schedule Variance (SV) – SV = EV – PV; positive SV = ahead of schedule.
• Performance Indexes – CPI = EV / AC, SPI = EV / PV; values >1 indicate favorable performance.
• Agile Sprint – Time?boxed iteration (usually 2?4 weeks) delivering a usable product increment; includes daily stand?ups, sprint review, and retrospective.
• Stakeholder Register – Document listing all project stakeholders, their influence, interest, and communication needs.

Step?by?Step / Process Flow

1. Define Scope & Objectives – Write a clear project charter, list deliverables, and obtain sponsor approval.
2. Create WBS & Assign Resources – Break deliverables into tasks, assign team members, and estimate labor?hour costs.
3. Develop Schedule (CPM or Agile) – Plot tasks on a Gantt chart, calculate the critical path, and set sprint dates if using Agile.
4. Budget & Earned?Value Baseline – Compute the Budget at Completion (BAC), then set PV, EV, and AC baselines.
5. Monitor & Control – Each reporting period, calculate CV, SV, CPI, and SPI; adjust resources or scope as needed.
6. Close & Review – Conduct a final project audit, capture lessons learned, and deliver the final product to stakeholders.

Common Mistakes

• Mistake: Treating “float” as a buffer you can freely use on any task.
  Correction: Float only applies to non?critical activities; using it on a critical task creates schedule risk.

• Mistake: Confusing EV with PV (students often plug the budgeted total instead of %?complete).
  Correction: EV reflects work actually performed; calculate it by multiplying the percent complete by the BAC.

• Mistake: Ignoring stakeholder communication preferences and sending the same report to everyone.
  Correction: Use the stakeholder register to tailor frequency, format, and detail level for each audience.

• Mistake: Assuming the longest duration path is always the critical path without checking dependencies.
  Correction: Verify that each activity on the longest path has zero float; any positive float removes it from the critical path.

• Mistake: Adding “extra” tasks after the schedule is set and still calling the original timeline the baseline.
  Correction: Any scope change requires a formal change request and a revised baseline; otherwise the earned?value calculations become invalid.

Exam Insights

1. Formula Focus: FBLA/DECA loves the four core EV formulas (EV, PV, CV, SV) and the two performance indexes (CPI, SPI). Memorize them and know when to apply each.
2. Critical Path vs. Float: Expect a scenario where two paths have the same total duration—only the path with zero total float is the critical path.
3. Agile vs. Waterfall: The exam may ask you to choose the appropriate methodology; look for clues like “rapid market feedback” (Agile) versus “fixed?price, fixed?scope” (Waterfall).
4. Role?Play Tip: When acting as a project manager, always start with a concise “project charter” statement; judges award points for clear scope, measurable objectives, and stakeholder alignment.

Quick Check Questions

1. A project has a BAC of $50,000. After two weeks (40% of the schedule) the team has completed 30% of the work and spent $12,000. What is the Cost Variance (CV)?
   Answer: CV = EV – AC = (0.30?×?50,000) – 12,000 = $15,000 – 12,000 = $3,000 (under budget).

2. Which activity is on the critical path?

3. A) Task A (5 days, float 2)
4. B) Task B (8 days, float 0)

5. C) Task C (6 days, float 1)
   Answer: B) Task B – zero float indicates it lies on the critical path.

6. In an Agile sprint, the team delivers a usable product increment every 3 weeks. Which statement is true?
   Answer: The sprint length is a time?boxed iteration, and the team should hold a sprint review and retrospective at the end of each 3?week period.

Last?Minute Cram Sheet (10 one?liners)

1. Scope = What’s in, Scope Creep = What’s out.
2. Critical Path = longest duration with zero float.
3. Float = Late Start – Early Start (or Late Finish – Early Finish).
4. EV = %?Complete × BAC – not the total budget.
5. PV = (Time Elapsed / Total Duration) × BAC.
6. CV = EV – AC; positive = under budget.
7. SV = EV – PV; positive = ahead of schedule.
8. CPI = EV / AC; SPI = EV / PV; >1 = favorable.
9. Agile sprint = fixed?time box, daily stand?up, sprint review, retrospective.
10. Stakeholder Register = name, influence, interest, communication plan.