Agile vs Fragile: Technical Discipline Matters
Posted on Mar, 2013 by Admin
Part 10 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Principle nine is all about good design and technical excellence. One of the biggest challenges facing teams that are attempting to do Agile development is the natural urge to just jump in and start coding based on a lose set of requirements, without any real design. This is natural, but almost always results in negative impacts to the project timelines, because the team has to go back and do rework when it is discovered that there are flaws in their assumptions. In true Agile, design is a key component to the success of the project. Time isn’t wasted; it is saved by design, as it eliminates false starts and rework. In a Fragile environment, all processes, including design are shunned as time wasters. The team is unable to make the connection between their missteps and the lack of proper planning and design. In the Fragile world, processes are eliminated and documentation is shunned.This problem with anti-methodology is so prevalent in Fragile teams that the Agile Alliance came out with a statement supporting value added processes. They wanted to be clear that they weren’t against methodology, but were against methodology that didn’t help the team deliver the value the customer was looking for. This is the key challenge for teams. It is hard to identify the level of process and documentation that helps the entire team (not just developers) deliver the right solution for the customer. It is sometimes hard for testers to let go of the old documents that they are used to getting, and look for more efficient ways to get the information needed to deliver quality. I like the concept of healthy criticism. Everyone should have to prove that the process or document they are requesting is necessary. If they can’t defend how having the document or process helps them be successful; and more importantly how that without the it they will fail, then the process or document should be eliminated. Yes this from a quality leader! Process for the sake of process is waste! Process that drives efficiency and effectiveness is essential.
In the next installment of the blog we will talk about the 10th Agile principle. In the meantime…Keep on testing!