Module - Design, Development and Creativity
Class or Article - Article
Lesson or Name - Beck, K. (1999) Embracing Change with
Extreme Programming. Computer, 8
Additional Info - 70-77
Precis
In this article ' Embracing change with Extreme programming' by Kent Beck he presents change from the lens of Extreme programming. Beck views Extreme programming through a conventional lens on system developments and change from a waterfall and iterative design perspective, displaying the merits of Extreme programming as a way of running a program. Beck presents the idea that XP flips what is seen as the conventional methodologies on their head and in turn completes these stages one piece at a time, continuously through a development. Through continuous development, delivery and testing the team are able to ensure that the final product works, equally when something does not work they are able to see can it work, can they make it work ugly and then can they rebuild it after. Additionally a benefit of XP is that code is written in pairs so that no knowledge is silos or reside with one person. The customer/user have a key role in XP and are as a result choose the key performance indicators that would satisfy them that the story or iteration is complete. Timing in XP is a complex calculation due to the contineously nature of design, develop, test and deploy however through every facilitation of the XP lifecycle timing are being refined to a greater art. Beck acknowledges XP is by no means the silver bullet to development but through refinement can challenge the challenges themselves in tough environments.
Reflection
XP for me seems very like an agile approach and this is a methodology for change and development I am very intrigued by. XP for me has a more holistic lens on the change/development than other conventional methodologies. Allowing the user define the KPIs that deem success for them is a new concept I have been exposed to but I think this could be fundamentally flawed as Beck states at the start most customers don't know what they want, so in turn how can they tell you what will satisfy them?. While in saying this I believe this issue can be circumvented through continuous communication with the customer/user and as their knowledge develops it will bring refinement also to the process. XP is working to eradicate the gaps in the conventional methodologies and further more strengthen delivery, create a community, drive communication and knowledge dissemination. These are some of the fundamental issues with conventional changes and projects.
I would love to speak to someone who has lived the XP process through and get a deeper understanding of this. Equally I think I would enjoy this type of project as I feel it suits alot of my own personal skills but equally addresses and supports my weaknesses if developed in the implemented in a way that addresses these issues
Quotes
Precis
In this article ' Embracing change with Extreme programming' by Kent Beck he presents change from the lens of Extreme programming. Beck views Extreme programming through a conventional lens on system developments and change from a waterfall and iterative design perspective, displaying the merits of Extreme programming as a way of running a program. Beck presents the idea that XP flips what is seen as the conventional methodologies on their head and in turn completes these stages one piece at a time, continuously through a development. Through continuous development, delivery and testing the team are able to ensure that the final product works, equally when something does not work they are able to see can it work, can they make it work ugly and then can they rebuild it after. Additionally a benefit of XP is that code is written in pairs so that no knowledge is silos or reside with one person. The customer/user have a key role in XP and are as a result choose the key performance indicators that would satisfy them that the story or iteration is complete. Timing in XP is a complex calculation due to the contineously nature of design, develop, test and deploy however through every facilitation of the XP lifecycle timing are being refined to a greater art. Beck acknowledges XP is by no means the silver bullet to development but through refinement can challenge the challenges themselves in tough environments.
Reflection
XP for me seems very like an agile approach and this is a methodology for change and development I am very intrigued by. XP for me has a more holistic lens on the change/development than other conventional methodologies. Allowing the user define the KPIs that deem success for them is a new concept I have been exposed to but I think this could be fundamentally flawed as Beck states at the start most customers don't know what they want, so in turn how can they tell you what will satisfy them?. While in saying this I believe this issue can be circumvented through continuous communication with the customer/user and as their knowledge develops it will bring refinement also to the process. XP is working to eradicate the gaps in the conventional methodologies and further more strengthen delivery, create a community, drive communication and knowledge dissemination. These are some of the fundamental issues with conventional changes and projects.
I would love to speak to someone who has lived the XP process through and get a deeper understanding of this. Equally I think I would enjoy this type of project as I feel it suits alot of my own personal skills but equally addresses and supports my weaknesses if developed in the implemented in a way that addresses these issues
Quotes
Comments
Post a Comment