Module - Design, Development and Creativity
Class or Article - Article
Lesson or Name - Kruchten, P. (2007) Voyage in the Agile
Memeplex. ACM Queue, 5, 38-44.
Additional Info - 38-44
Precis
In 'Voyage in the Agile Memeplex' by Philippe Kruchten he claims that Agile or Agility is not a technology, science or product but a culture and in turn as a result has a wider impact than the project one works on. Kruchten goes on to argue that where people draw conclusions such as 'this is very waterfall' have never actually experienced waterfall or seen a waterfall project and in turn only the bad is being spoken about that in turn evangelises Agile. Observing the theoretical side of projects Beck presents Jonathan Whittys' perspective that there is no such thing as a project and rather that it is an illusion we are witnessing. Agile is not just one self replicating act but rather a set of acts together and in turn teams who deliver agile have proven to be an effective outfit at delivering replication, self - development and producing agility. It is the power of a methodology or framework to keep its context through multiple replications. Kruchten advocates that context is key and is akin to to Location, Location, Location on the property market. Context holds the key to developing iterations of an agile memeplex or framework and in such is a core consideration when selecting the style of development one will undertake. Kruchten does raise a cause for concern within the Agile community and that on the one of bigotry and dogmatism or plain ignorance.
Reflection
This is a read I really appreciate. The more and more advocates of agile and agility within the technology and development communities the more bashing of other frameworks and methodologies I hear. Waterfall has almost become the punchbag for Agile in a very blinkered fashion. Agile presents waterfall as this old and flawed methodology that seems to not deliver. I find this very cult like behaviour and narrow minded as it will and can be the case that Agile will have its poor and substandard performances. Context, Culture and Application are 3 key components for ensuring the right method and approach are taken. I spoke in a previous article that methodologies need to be less evangelical of themselves and be more open to interpretability with one another. As no one organisation is the same or a department within each, being able to apply different methodologies and approaches harmoniously is a key feature I feel all methodologies are lacking. Simply building upon the old and advocating the new doesn't work in an industry where open-source and co-creation are now at the forefront and furthermore in an ever connected and developing world it is not feasible for one methodology to rule supreme but rather work and deliver together. We are the sum of our parts, and our parts come in all different shapes and sizes not to mention ages and we need to be open and aware to this. Perhaps this is something we can build in to culture as Kruchten suggested as it is an integral decision point.
Quotes
Precis
In 'Voyage in the Agile Memeplex' by Philippe Kruchten he claims that Agile or Agility is not a technology, science or product but a culture and in turn as a result has a wider impact than the project one works on. Kruchten goes on to argue that where people draw conclusions such as 'this is very waterfall' have never actually experienced waterfall or seen a waterfall project and in turn only the bad is being spoken about that in turn evangelises Agile. Observing the theoretical side of projects Beck presents Jonathan Whittys' perspective that there is no such thing as a project and rather that it is an illusion we are witnessing. Agile is not just one self replicating act but rather a set of acts together and in turn teams who deliver agile have proven to be an effective outfit at delivering replication, self - development and producing agility. It is the power of a methodology or framework to keep its context through multiple replications. Kruchten advocates that context is key and is akin to to Location, Location, Location on the property market. Context holds the key to developing iterations of an agile memeplex or framework and in such is a core consideration when selecting the style of development one will undertake. Kruchten does raise a cause for concern within the Agile community and that on the one of bigotry and dogmatism or plain ignorance.
Reflection
This is a read I really appreciate. The more and more advocates of agile and agility within the technology and development communities the more bashing of other frameworks and methodologies I hear. Waterfall has almost become the punchbag for Agile in a very blinkered fashion. Agile presents waterfall as this old and flawed methodology that seems to not deliver. I find this very cult like behaviour and narrow minded as it will and can be the case that Agile will have its poor and substandard performances. Context, Culture and Application are 3 key components for ensuring the right method and approach are taken. I spoke in a previous article that methodologies need to be less evangelical of themselves and be more open to interpretability with one another. As no one organisation is the same or a department within each, being able to apply different methodologies and approaches harmoniously is a key feature I feel all methodologies are lacking. Simply building upon the old and advocating the new doesn't work in an industry where open-source and co-creation are now at the forefront and furthermore in an ever connected and developing world it is not feasible for one methodology to rule supreme but rather work and deliver together. We are the sum of our parts, and our parts come in all different shapes and sizes not to mention ages and we need to be open and aware to this. Perhaps this is something we can build in to culture as Kruchten suggested as it is an integral decision point.
Quotes
Comments
Post a Comment