3 ms·

For me, agile is about responding to change quickly: reducing the waste in the development cycle by not building stuff that isn't needed. That's an important st

For me, agile is about responding to change quickly: reducing the waste in the development cycle by not building stuff that isn't needed. That's an important step, but it has very little to say about the way in which you build the stuff that is valuable: it doesn't dictate architecture, approach, standards, or any thing else (except that onerous / long-winded processes conflict with the agile approach). Agile is great for developing things where you're not totally sure what the end result is. Specifically, for me, agile doesn't make the development _process_ faster, it just encourages you to adapt more quickly and may (should) speed up delivery. If you want to make the _process_ faster, you have to look to other solutions (which are pretty orthogonal to agile).

usrusr 9y ago
In a perfect world, agile is about responding to change, in reality it is about responding to change and to misunderstandings. I believe that the latter is even more important, but an emphasis on change might be helpful to sell the idea to people who don't think that it could happen while they are involved.
jasonmaydie 9y ago
It's funny because everyone seems to go with their own ideas on what Agile is. I know companies who do agile and to them it's moving fast, loose requirements, etc. That is what it means to be "agile". For others, it's that slow grinding process of sprint planning, task estimation, pointless scrums and using estimation as some kind of metric for performance. Then I took an agile course from the scrum alliance and the instructor only cared about Agile as a way of building "high performance teams". E.g get a group of people together, stay together, let them manage their time and they way they work to get the best usage out of them. I've done all 3, to me agile fails because nobody really knows what it is other than they are doing "Agile"
- zimpenfish 9y ago
  > nobody really knows what it is other than they are doing "Agile" And as soon as you say "Agile isn't working", you'll get a flurry of responses saying "You're clearly not doing it RIGHT".

usrusr 9y ago

In a perfect world, agile is about responding to change, in reality it is about responding to change and to misunderstandings. I believe that the latter is even more important, but an emphasis on change might be helpful to sell the idea to people who don't think that it could happen while they are involved.

jasonmaydie 9y ago

It's funny because everyone seems to go with their own ideas on what Agile is. I know companies who do agile and to them it's moving fast, loose requirements, etc. That is what it means to be "agile". For others, it's that slow grinding process of sprint planning, task estimation, pointless scrums and using estimation as some kind of metric for performance. Then I took an agile course from the scrum alliance and the instructor only cared about Agile as a way of building "high performance teams". E.g get a group of people together, stay together, let them manage their time and they way they work to get the best usage out of them. I've done all 3, to me agile fails because nobody really knows what it is other than they are doing "Agile"

zimpenfish 9y ago
> nobody really knows what it is other than they are doing "Agile" And as soon as you say "Agile isn't working", you'll get a flurry of responses saying "You're clearly not doing it RIGHT".