From Plotting to Iterating: Unveiling the Parallels Between Traditional and Agile Approaches in Project Management and Writing

?

The decision of which approach best fits a project is a crucial step when starting off. Analyzing the entire project is essential to determine whether a traditional waterfall approach, an agile approach, or a hybrid of both is the right way to proceed. While this article won't delve into selecting the ideal approach, it aims to highlight the differences between them using an uncommon example within this network: writing a book.

To begin, let's consider the phases or lifecycle of a general project: initiation, planning, execution, control, and close. Although variations exist depending on the case, this provides a sufficient framework for our discussion of different approaches and how they utilize these phases.

Let's start with the traditional waterfall approach. In this method, each project phase follows the completion of the previous one, and the final product is delivered at the end of the entire process. The planning phase consumes a significant amount of time, and implementing changes during execution can be challenging and costly. Now, let's examine how this approach applies to writing a book. In the realm of writers, there is a term attributed to those who meticulously plan out the entire book, (whether it's a novel or a collection of stories) they are often referred to as "map writers." These authors invest hours sketching the story, characters, and settings, sometimes with meticulous detail before they sit down to write the first sentence. They do not publish until the entire book is finished.

On the other hand, we have the agile approach, which is more contemporary. Agile projects progress through short iterations, allowing the product to deliver value from the early stages. While this method is primarily used in software development projects, it can be applied in various fields. Let's revisit our literature example. It is common for authors to commence their careers by writing short stories or tales. This enables them to release and showcase their "voice" within shorter time frames. These texts may be published in blogs, journals, magazines, or social media platforms. Once they have gained recognition from a broader audience, they may then publish a longer book, such as an anthology containing some of those stories, or even a completely new work. This illustrates how the agile approach adds value to the product, the client, and the customers with each iteration. Within the authors' jargon, the opposite of "map writers" is often referred to as "compass writers." These individuals have an idea for a new story and tend to sit in front of the computer, typing away as fast as they can, sometimes only knowing the main character's name. Planning is minimized or nonexistent, and it is not uncommon for them to be uncertain about the type of work they are creating—a tale, a novel, or even a script. This is analogous to projects where the client's requirements are unclear, prompting the adoption of an agile approach during execution.

In summary, the traditional approach (waterfall) involves delivering the product at the project's conclusion, like a "map writer" publishing their novel. In contrast, the modern approach (agile) embraces iterative development, allowing the product to evolve with each iteration. This resembles a writer who shares their texts through various platforms without waiting to compile an entire book of stories. Personally, I have employed both approaches in my own works. I have published short stories across different media while concurrently working on a well-planned novel.

Feel free to connect with me on LinkedIn for further discussions or collaborations in project management and writing!