Originally posted by Vinayagam Kulandaivel: 1. Team size
It's true that Agile is easier to implement with smaller teams, up to perhaps a dozen people - simply because software development works better that way.
Jutta Eckstein, the author of "Agile in the Large" is known for saying that, on the other hand, being Agile is *especially* important for larger projects. (As far as I know, she has personal experience with projects of over a hundred people, and contact to other projects of 500 and more.)
2. Development/Maintenance/Enhancement projects
I don't see a significant difference between maintenance and enhancement. And as an Agile project works to deliver a minimal, working system after a few weeks, it basically is in enhancement mode afterwards, anyway. (You could say that Agilists strive to make every project become an enhancement/maintenance project as fast as possible.)
3. Mid size/Larger size/ERP/Product based projects
Not sure why you think this would make a difference.
4. Development in different geographical locations
As with 1., this certainly makes it harder to be Agile. Still, people trying to do it report that it still pays back to try to be as Agile as possible.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Nov 26, 2004
Thanks for your time. Agile is basically for the project to see the continuous progress like iterative model. This can be fit only for the project that have more number of business/functional requirements. So that we can split that into short iterations and start development. When there are only very few requirements say 5 to 10 (am not sure about the size or the complexity) means it cant be fit for agile model. Please correct me if i am wrong.
Originally posted by Vinayagam Kulandaivel: When there are only very few requirements say 5 to 10 (am not sure about the size or the complexity) means it cant be fit for agile model. Please correct me if i am wrong.
Any requirement, no matter how large, gets implemented by writing one line of code at a time. No matter how large, I think there's probably a way to split any requirement larger than an afternoon of work into smaller requirements for planning purposes. At least, I've never seen a requirement where we couldn't do that.
Splitting large requirements into smaller, parallelizable requirements is something of an art, and I can understand a customer's reluctance to do so, but I do believe it's possible.
Author of <a href="http://www.amazon.com/gp/product/0596527675?tag=jranch-20" target="_blank" rel="nofollow"><i>The Art of Agile Development</i></a>
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com