Course contentsShow
← Software Engineering
Lesson 1663 of 1,93348. Project Management for EngineersFree lesson

Identifying Unknowns and Spikes

Recognize areas of uncertainty and create time-boxed investigation tasks to reduce risk before committing.

Identifying Unknowns and Spikes

What you'll learn: How to spot areas of uncertainty in your plan and create focused investigation tasks to reduce risk before full implementation.

What Are Unknowns?

Even after breaking down features into tasks using techniques like Work Breakdown Structures and vertical slicing, you'll encounter tasks where you don't know how to estimate accurately. These are your unknowns—technical questions without clear answers yet.

Common unknowns include:

  • "Can this third-party API handle our scale?"
  • "Will this approach work with our legacy database?"
  • "How difficult is migrating this data format?"

Pretending these unknowns don't exist leads to blown estimates and project delays.

What Is a Spike?

A spike is a time-boxed investigation task designed to answer a specific unknown. Think of it as a research mini-project with a strict deadline and clear exit criteria.

Unlike regular development tasks, spikes don't produce production code—they produce knowledge. You might build a prototype, run experiments, or research documentation. The goal is gathering enough information to confidently estimate the real work.

Creating Effective Spikes

When you identify an unknown:

  1. Define the question clearly: "Can we process 10,000 records/second with library X?"
  2. Time-box strictly: Usually 1-3 days maximum
  3. Set an outcome: A written finding, not perfect code
  4. Schedule before commitment: Run spikes before promising delivery dates

After the spike, you can size the actual implementation task with much better accuracy, reducing the Cone of Uncertainty.

Key Takeaway: Recognize what you don't know early, create time-boxed spikes to investigate unknowns, and convert uncertainty into actionable knowledge before making commitments—this protects both your estimates and your team's credibility.