Creativity and process

The Agile Manifesto recognises that software development is a creative endeavour. One of its core values is a preference for “individuals and interactions over processes and tools”, which supports the idea that writing code isn’t a production line, and individuals are not interchangeable units of resource.

A good developer has an intricate knowledge of technology. They have the capability to understand what needs to be achieved (the problem, need or requirement), the creative insight to couple the two, and develop the best possible solution. Agile methodologies allow this to happen, by accepting that software development is creative, and the process is actually one of learning and discovery.

But because Agile doesn’t promote formalised process, it’s still not an excuse to just do whatever you want and hope for the best. Agile methodologies are very structured and consist of a framework of processes. These are designed to encourage inclusiveness in the development team, to foster understanding and unlock creative potential. A key difference between Agile and other software development methods is they do not allow for traditional and authoritative ‘command and control’ type of management process popularised 50 years ago, instead they feature processes that involve the whole team at every level and every stage during development.

You’re only ‘doing’ Agile if you’re ‘doing’ Agile’s processes.