Does writing a book resemble the Waterfall method or Scrum? Yes.
I first started blogging and writing books in 2008. Since that time, I like to think that I've become a more effective writer. If I hadn't, I would have thrown in the towel years ago. Cue Rocky IV reference.
When I think about writing a book today, I often bounce back and forth between two antithetical ways to develop software development: Agile methods such as Scrum and the Waterfall method. My longstanding antipathy to jargon prevents me from fusing the two into some horrible portmanteau.
At the same time, though, when I built RacketHub, I thought long and hard about adding a Gantt chart before ultimately deciding against it. Doing so would imply that writing a book represents either a sequential or serial process. Here's a quick figure demonstrating their differences:
It'll only take a moment.
