A free world wide network of agilitists!
Agility and project size are not competing entities
On the next "softwareudvikling på tværs" conference in Copenhagen, 2-3 June 2008, ( http://www.teknologisk.dk/18841) My contribution will be a discussion about agility and projects at scale.
I have these questions as a starting point:
> Can large and complex projects be agile?
> Is RUP an agile process?
> How agile can a process be?
> How do you measure agility?
My major points will be:
The agile manifesto is valid also if communication in a project is complex, and if not all project members are skilled. (I mean: small projects with skilled people are easily agile, anyway)
A clever use of method documentation is nessesary to maintain good processes (I assume: a process is how you work, a method is a prescription of how to work)
Agile practices can serve as a means of measuring agility, in stead of applicability to a certain agile method.
Agile practices are independant, both from each other and from methods.
All agile methods includes a set og "fundamental agile practices", like "iterative development", "whole team" and "integrated testing", but RUP includes more Agile practices than most, like "Risk-Value Lifecycle" and "Agile Architecture". This suggests that RUP is a more agile method !?!.
The mentioned agile practices are courtesy of Per Kroll, IBM Rationaol
I have these questions as a starting point:
> Can large and complex projects be agile?
> Is RUP an agile process?
> How agile can a process be?
> How do you measure agility?
My major points will be:
The agile manifesto is valid also if communication in a project is complex, and if not all project members are skilled. (I mean: small projects with skilled people are easily agile, anyway)
A clever use of method documentation is nessesary to maintain good processes (I assume: a process is how you work, a method is a prescription of how to work)
Agile practices can serve as a means of measuring agility, in stead of applicability to a certain agile method.
Agile practices are independant, both from each other and from methods.
All agile methods includes a set og "fundamental agile practices", like "iterative development", "whole team" and "integrated testing", but RUP includes more Agile practices than most, like "Risk-Value Lifecycle" and "Agile Architecture". This suggests that RUP is a more agile method !?!.
The mentioned agile practices are courtesy of Per Kroll, IBM Rationaol
Comment
© 2009 Created by Jørgen Larsen on Ning. Create a Ning Network!
You need to be a member of Agile Thinkers to add comments!
Join this Ning Network