This post is not about explaining what Agile is. If you want to know what it is, point your browser to the Agile Manifesto. What I want to share is what I believe to be some people's misconception of what Agile is and when to recognise when it isn't.
As a contractor, I had the opportunity to work in different client sites and I have seen how some organisations had more success with Scrum (one of the most commonly used Agile methods) compared to others, and that was a surprising discovery because the very mechanism of Agile projects is supposed to ensure higher probabliltiy of the software being delivered and of certain quality.
So, why do some Agile projects did not live up to the expectations of Agile methodology? In most cases that I've seen, it's because they lost sight of the key aspects of the Agile manifesto. So, I'll re-iterate some of these here:
- Early and continuous delivery of valuable software.
- Deliver working software frequently, from a couple of weeks to a couple of months
- Working software is the primary measure of progress.
So, let's define what is 'working software' and how Agile teams sometimes forget this little fact. A working software is one which is deploy-able into production to be used by real users.
In a truly Agile house, to be able to develop working software continuously is not an issue but in organisations where you are transitioning from the traditional methods of development into Agile then there is a risk that by simply following the mechanics of Scrum you could mistakenly believe that a potentially deliverable working software will come out the other end, just because you're following Scum.
Let's illustrate this with an example. In a traditional software project, a typical system being built can be usually broken down into 3 logical components; the user-facing front-end component (which could either be a desktop or web-based application, or an interface to an external system), the central processing engine component (holding the business logic and business processes) and the back-end component (mainly databases and/or interfaces to other external systems). There would be 3 different teams building each of the components and this would be followed by Integration Test phase, System Test phase and User Acceptance Test phase, prior to deployment. And, it is only when the project is in the System Testing phase that one gets the visibility as to how the system works as a whole and only after UAT that the software reaches the 'potentially deliverable working software' state.
The mistake that some people make is when changing from the traditional development to Agile methods, they simply change their ways of working to accommodate the Agile process, i.e. if we were to take the above example, they would still have 3 separate teams building the 3 components of the system, with each team working in an Agile manner, falsely believing that just because they are using the tools and processes of Scrum they are now doing Agile.
Once the components are built, they still need to go through the integration testing phase, system testing phase and UAT phase. What they have forgotten is the fact that the software that each Agile team is building forms just the component of a complete system, and therefore, there is no complete working software at anytime during the development, which is in a deploy-able state to production. If this happens then they have missed the most important value that Agile methodologies brings.
No comments:
Post a Comment