If you’ve ever outlined a novel in meticulous detail—only to abandon the plan halfway through—you’ve experienced the tension between Waterfall and Agile thinking.
As a writer with a project-management background, I’ve often noticed how closely drafting a novel mirrors managing a complex initiative. Whether you're building software or building a fictional world, you’re juggling scope, timeline, stakeholder expectations (hello, readers), and creative risk.
So which works better for drafting a novel: Waterfall or Agile?
Let’s explore.
In project management, Waterfall is a linear process:
Plan → Design → Build → Test → Deliver
Applied to fiction, Waterfall drafting looks like this:
Create a detailed outline (acts, chapters, beats)
Define character arcs from beginning to end
Lock in world-building rules
Draft straight through from Chapter 1 to “The End”
Revise only after the full manuscript is complete
This approach works beautifully for writers who:
Love structure
Need clarity before they begin
Write plot-heavy stories (mystery, political intrigue, multi-POV epics)
Want tight foreshadowing and payoff
For example, if you're writing a layered Regency mystery where clues must align across 24 chapters, Waterfall planning can prevent massive rewrites later.
Clear roadmap
Strong plot cohesion
Easier continuity tracking
Efficient if the outline is solid
Can feel rigid
Hard to pivot if a character surprises you
Risk of overplanning and never drafting
Agile, by contrast, works in short cycles. In software, it’s built around sprints, iteration, and feedback.
Applied to fiction, Agile drafting might look like:
Writing in 1–2 chapter “sprints”
Revising as you go
Adjusting plot based on character evolution
Testing scenes with beta readers early
Allowing the story to evolve organically
Instead of a fixed blueprint, you work from a flexible story vision.
This is especially helpful in:
Character-driven romance
Emotional slow burns
Stories where chemistry develops unexpectedly
Series where later books may influence earlier threads
In my own Regency romance projects, I’ve found that emotional arcs often deepen mid-draft. Agile allows room for that evolution.
Creative flexibility
Stronger character authenticity
Easier adaptation when inspiration strikes
Continuous improvement
Risk of scope creep
Continuity errors
Endless tinkering
Harder to estimate completion timeline
(Apologies for the DOS-style table, but Google Sites doesn't seem to have a table function)
| Element | Waterfall | Agile |
| ----------------------- ---------- | --------------------------------- | ---------------------- |
| Outline | Fully detailed upfront | High-level vision |
| Drafting | Linear | Iterative |
| Revisions | After full draft | Ongoing |
| Flexibility | Low | High |
| Timeline predictability | High | Moderate |
Here’s the truth: most successful novelists use a hybrid model.
You might:
Outline your three-act structure (Waterfall)
Draft in two-chapter sprints (Agile)
Conduct midpoint reassessments
Lock plot beats, but allow emotional beats to evolve
For example, you could fully map your mystery subplot while letting the romantic tension breathe and shift as you write.
That hybrid model protects structure while honoring creativity.
If you’d like a starting framework, try this:
1. Vision Phase (Waterfall)
Define theme
Identify protagonist arc
Map major turning points
Sketch ending
2. Sprint Drafting (Agile)
Write 2–3 chapters
Pause and reassess character alignment
Adjust outline if needed
Repeat
3. Structural Audit (Waterfall)
Ensure setups/payoffs align
Tighten pacing
Validate timeline logic
4. Iterative Polishing (Agile)
Scene-level improvements
Beta feedback cycles
Emotional depth layering
Waterfall gives you control.
Agile gives you discovery.
Novel drafting is both architecture and exploration. It’s a blueprint and a brushstroke.
If you’re a structure-loving planner who occasionally rebels mid-draft, you’re not inconsistent; you’re simply blending methodologies.
And in fiction, as in project management, adaptability often produces the most powerful results.