It Ain't What You Do It's The Way That You Do It

Why do we all make a huge noise about Agile? There are countless discussions for and against Agile, as well as debates on how we must operate when implementing Agile. Some even shout "Agile is dead" and ask what's next. Well, it's time to set the record straight: Agile is not a revolutionary new concept. The principles of iterative work, feedback loops, and continuous improvement have been around for centuries, not just since 2001.

The Origins: Beyond Software Development

Agile formally emerged in 2001 with the Agile Manifesto, aiming to improve software development. However, the core principles—iteration, adaptability, and feedback—have been integral to creative and intellectual processes for centuries. The term Agile may be new, but the concept is timeless. Artists, writers, and musicians have long utilised iterative approaches to refine their work, driven by feedback, self-assessment, and the pursuit of excellence. The work I did previously, recording and creating music, exemplifies everything about Agile, years before the Agile Manifesto was published. The song by Fun Buy Three referenced in the title of this article is a reworking of a song first recorded in 1939.

Shakespeare: The Agile Playwright (16th/17th Century)

William Shakespeare, one of the greatest writers in history, exemplified Agile practices through his writing process. His plays were not written in isolation and then performed exactly as scripted. Instead, they were living documents, continuously refined through rehearsal, feedback from actors, and audience responses.

• Iterative Rewriting: Shakespeare frequently revised his works, adjusting scenes, dialogues, and character dynamics based on what worked and what didn't. His ability to adapt and improve his scripts during rehearsals mirrors the Agile approach of revising and refining a product through sprints and feedback loops.

• Collaboration with Stakeholders: Much like modern Agile teams involve product owners and users in the development process, Shakespeare worked closely with actors and theatre owners to shape his plays. Their input played a crucial role in the evolution of his works, highlighting the collaborative nature of his creative process.

• Responding to Change: Shakespeare was not bound by rigid plans. He was open to changes in his scripts, adjusting his work based on external factors such as audience reception or the availability of certain actors. This adaptability is a hallmark of Agile, where teams respond to changing requirements rather than sticking strictly to an initial plan.

Beethoven: The Agile Composer (18th/19th Century)

Ludwig van Beethoven, one of the most celebrated composers, was a relentless reviser of his music. His process was deeply iterative, often reworking his compositions multiple times before reaching a final version, embodying the Agile principle of continuous improvement.

• Prototyping Through Drafts: Beethoven’s sketches and drafts show a composer deeply engaged in a process of musical prototyping. He would write, revise, and rewrite sections repeatedly, exploring different possibilities to refine his work. This is akin to software developers creating prototypes, testing, and iterating.

• Feedback and Self-Critique: Beethoven would often seek feedback from other musicians or critique his own work, constantly striving for improvement. This parallels the Agile practice of retrospectives, where teams review what went well and what could be improved after each sprint.

• Adaptability in the Face of Constraints: Despite his hearing loss, Beethoven adapted his process, leveraging his deep knowledge of music theory and his inner ear to continue composing. This resilience and adaptability reflect Agile’s core value of responding to change over following a rigid plan.

Other Historical Agilists

Many other historical figures and professions have embodied Agile principles. Here are a few:

Leonardo da Vinci (15th/16th Century): Known for his iterative approach to art and invention, da Vinci constantly sketched, revised, and tested his ideas before reaching a final product. His notebooks are filled with adjustments and experiments, illustrating a process of continuous refinement.

Thomas Edison (19th/20th Century): Edison's approach to invention was famously iterative, involving thousands of experiments and adjustments before achieving a successful outcome, much like the Agile practice of trying multiple approaches to find the best solution.

Architects and Builders: Medieval and Renaissance architects often adapted their designs during construction, responding to structural challenges, material availability, and feedback from patrons—practices that align closely with Agile methodologies.

Agile Resonates Across Time

Agile resonates because it reflects how humans naturally work: through trial and error, collaboration, feedback, and adaptation. These practices are not bound to any one industry or era but are fundamental aspects of creativity and problem-solving. The historical examples of Shakespeare, Beethoven, and others show the Agile mindset has always been about embracing uncertainty, valuing collaboration, and continuously improving. This approach to work transcends technology and is as relevant today as it was centuries ago. Agile for technology development is not dead; it’s just evolving.

Embrace the Timeless Nature

Agile is more than a project management framework; it's a way of thinking and working that has been part of human creativity and innovation for centuries. By understanding the deep roots of Agile principles, we can appreciate that we are part of a long tradition of iterative and collaborative work. So, next time you reach for the Scrum Guide to understand what you need to do next, think about what your favourite artist, writer, musician, or architect would do and learn from them. Remember: you’re not just using Agile—you’re continuing a legacy dating back to some of the greatest minds in history.