Shades of grey
The question I keep pondering, "when do you use agile?". "can you use agile for Fixed price projects?" is another question that is being discussed frequently and recently in Agile Alliance. Well, read on my thoughts ... You should use agile when you cannot define requirements to the last line, when you are not clear exactly what you want and these wants potentially change depending on what you see. It is ironical that more often than not, this is the case. Hence you should use Agile more often than not. When the requirements are in various levels of grey, agile works very well - like a dream. The key there is that details are expected to come later but commitments are expected without the details. If you try to get the details in such a case, you are force fitting a wrong peg. It is in such situations, teams should accept the shades of grey and work towards achieving business results. Will they end up achieving exactly what they want - yes. The reason is simple - no...