In today’s blog, I will outline some myths about the Agile and XP framework….
According to Visual studio Magazine, Agile methods (which include XP Programming) can sometimes be misinterpreted despite its popularity. Herein, I shall discuss and critique some of these…
As per my previous two blogs where I discussed the growing concepts in relation to Extreme Programming and indeed Agile as a whole. http://www.gartner.com/technology/home.jsp has even declared that ‘Agile is now the mainstream!’.
Misconception 1; Agile does not ‘Commit’.
Some people still think that Agile do not commit and that the process is conducted by a number of developers working on the programme until completion. In reality, the teams within Agile are honest, realistic and timely in their delivery of software development and they do commit…
Misconception 2; Predictability is not part of the Agile agenda.
Similar to the last misconception, however the coding used is subdivided into two distinct parts;
1 Coding which is tested and rolled out within two weeks; daily communicating occurs and system requirements are being updated consistently.
2 When codes are not tested for a period of 6 months to one year, teams do not report any status until the finish of a said construction stage.
The fact is, that well working Agile teams ensure that predictability is ensured due to constant communication, adapting and updating of documents, so that everything is current.
Misconception No 3; Agile is a quick fix to your software problems.
Some Agile ‘preachers’ will claim that the utilisation of Agile will fix all of your problems and quickly! Whilst the processes are indeed carried out in an efficient and speedy manner, the guarantee of speed cannot be taken for granted in the delivering of every software solution. The Agile values foundations are collaboration, quality, regular and quick feedback.
Misconception 4; Using Agile can assist me with anything.
Sometimes Agile is not the ideal solution. For example; the development of space programme’s e.g. NASA call for a much higher design structure and may in fact be more suited to the Waterfall model.
Misconception 5; Agile is conducted in one way only.
As per the original Agile Manifesto, it included four values and also 12 principles, it doesn’t take the implementation details into consideration. Scrum, Extreme Programming, Feature-Driven Development and Kanban can be interpreted in different ways.
Misconception 6; No requirement for up front designs in Agile.
The design, in fact has to be completed at the last responsible moment. Parts of the design of the development of the Agile software are done well before any coding is written up, whereas others completed when and as they are needed.
Misconception 7; Agile is Pain Free.
When a system is changed from say a Waterfall system to a fully operational Agile system, this can be declared a success. To optimize the new software will require practice and time in order to become familiar with the new Agile software. It’s about familiarising yourself with your new Agile system…
In my next blog, I am exploring a case study in relation to XP programming, as used by the US Army…