Skip to content
GanttPal
Log in Get started

Why Every Project Still Needs a Plan

A 47-minute Time Limit conversation with J. Scott, founder of 120VC and author of The Irreverent Guide to Project Management, makes a simple case: the label on your method does not decide whether you need a plan. Agile, enterprise and blended approaches all need one.

The method label does not remove the need to plan

Stakeholders often ask to skip formal planning and simply start delivering. That can occasionally work, but it usually leaves the team without a shared sequence, a way to spot blockers, or a basis for defending dates. Scott's answer is direct: create a plan always, regardless of the method name you use.

Planning is not the opposite of agility. Even agile delivery needs a vision, a roadmap and a backlog. Treating agile as permission to improvise misses the discipline that makes iterative work steerable.

A playbook you can defend

Scott describes a practical sequence from his firm's playbook. Start with a charter: its objectives and scope items sketch the outline of the work plan. Then break that outline into tasks small enough to estimate credibly, with each task capped at twelve hours and no more than three days. Finally, work with subject-matter experts until their commitments are clear enough to defend.

That last step matters when an executive asks why a date cannot move sooner. A small, explained task can be walked through piece by piece; a vague block of work cannot.

Use the playbook, do not be used by it

A standard playbook helps with training and quality assurance, but it is not a script to follow blindly. Pick the tools a particular project actually needs, and break the process when it gets in the way of delivering value.

If a client pushes to begin before a plan exists, Scott's approach is pragmatic: allow the start, plan in parallel, and take ownership only once the plan is in place. Without a plan, there is no blocker to escalate.

Strong commitments have five qualities: they are public, active, voluntary, explicit and mission-based. Two often-overlooked time savers support them — clear agendas and blocking time on the calendar.

Checklist: is your plan defensible?

Use this checklist before you accept a schedule:

  • Can you state the vision, roadmap and backlog for agile work, or the equivalent direction for other methods?
  • Does a charter's objectives and scope items outline the work plan?
  • Is every task sized at twelve hours or less, and within three days?
  • Have subject-matter experts made public, explicit commitments you can defend?
  • Are agendas and calendar blocks protecting the time the plan depends on?
  • If work started without a plan, is planning continuing in parallel until ownership can be taken?

The episode also covers blending processes, collaboration on planning, common planning mistakes, and ways to improve estimating. It runs 47 minutes and 48 seconds.

Frequently asked questions

Does agile mean a project can skip planning?

No. In this discussion, agile work still needs a clear vision, a roadmap and a backlog. Choosing an agile label does not remove the need to decide direction and sequence.

How small should planned tasks be?

Keep tasks small enough to explain: no more than three days and twelve hours each. That granularity makes an estimate easier to justify when leadership asks for a faster date.

What if a client wants to start before a plan exists?

Let work begin if the client insists, but continue planning alongside it and take ownership only once a plan exists. Without a plan, there is no agreed blocker to point to.

Should every project follow the same playbook exactly?

Use a standard playbook for training and quality assurance, select only the tools the project needs, and set the process aside when it blocks value.