To understand issue of XP (Extreme Programming) as a methodology is important to mention some of it? s background. XP came to the picture in 1999 in Kent Beck? s book named Extreme Programming Explained. The book was originally aimed to programmers but the Extreme methodology reached others areas as well. XP as a methodology in the early 2000 gained a lot of followers as a new outlook of doing programming and systems design. But this new methodology also arose questions about its effectiveness and originality when compare to the other traditional models.
The article Is extreme Programming Just Old Wine in New Bottles: A Comparison of Two Cases (2005) summarizes that the principles of XP at first glance may seem like a new methodology, a methodology that promotes communication, simplicity, feedback and courage something different from the limitations of the other existing methodologies. However, the author’s opinion is to beware of the swan song of the XP to take a deeper look and see that the root of the methodology can be traced back to Dahl and Niggards’ (1966) ideas, that this so call new idea is just old wine in a new bottle.
The authors conclude that the contribution of the XP in the field maybe not so new after all and depends more of motive individuals that will do well regardless the methodology they use, to support their opinion the authors offer the results of their qualitative case-study of two different companies that applied an XP-style development approach in their information systems development life cycle.
The Term Paper on Extreme Programming Xp Development Code 2002
Kent Beck introduced extreme programming to the programming community. He developed and documented an approach to computer software creation that uses elements of traditional methods and redefines the priority, sequence, and emphasis of these elements to increase the number of options available to developers as they fashion new software he calls Beck's Extreme programming (Beck, 1999). To put it ...
The authors urge the reader to consider that while there are many claims for the successful use of XP and Agile Modeling (AM) and many advocates that support its use, these claims are lacking of studies to support them. To emphasis their position the authors explore the concept of XP as a new approach to IS development, Hilkka M. R. and et. al. (2005).
They argue that instead of being a new development model, XP can be described as a way of working and actually does not bring anything completely new into the ISD discussion, Hilkka M.
R. and et. al. (2005).
In their study to prove their assertion the authors explore first the roots of XP, then describe the methodology used in their investigation which consisted of an adapted quality research and case study in contrast with a positivist approach, discussed the results of the investigation and presented their findings. They found that, all agile methods, including XP ave their strengths and weakness, that practitioners should focus more on the drivers, constrains, and enablers that affect the selection of the method instead what method is better than the other one. The authors conclude that they find found support of their claim through the results of their studies that, XP is a new name for an old way of developing a tailored system in the house, Hilkka M. R. and et. al. (2005).
The authors add that XP relays heavily on people, works best in small projects and seem to be at times an excuse for not using more refined approaches.
This conclusion seems at first to be similar to the opinion of Martin Fowler, author, speaker, and consultant on the design of enterprise software, in his opinion many of XP’s practices are old, tried and tested techniques, yet often forgotten by many, including most planned processes. As well as resurrecting these techniques, XP weaves them into a synergistic whole where each one is reinforced by the others and given purpose by the values, Fowler M. (2004).
The Research paper on Siemens Electric Motor Works – Process Oriented Costing
1. Introduction The German manufacturing giant Siemens currently markets the largest range of electric motors in the world under its SIMOTICS brand.1This success was ensured by a transformation of Siemens Electric Motor Works (SEMW) in the early 1980s when management decided to move to a specialised customised electric motor manufacturer. This strategic reorientation transformed the manufacturing ...
Fowler article describes that, for many that come briefly into contact with XP it seems that XP calls for the death of software design. XP rejuvenated the notion of evolutionary design, but does it in a different way than established software process (Fowler, 2004, Introduction, para 1) However Fowler looks at the functional side of the XP methodology instead of focusing on the limitations he exploits the benefits y considered that the negative critics of the methodology come from the misunderstanding of the concept.
The authors conclusions raise one of the most important issues with XP, namely that it not so a novel process and that is best suited for small projects, however is undeniable the impact that this methodology had in the process of programming and design since its beginning in 2000. The team work and emphasis in feedback makes of this model one very useful in the current work environment where team work is required in most positions.
