re: What does "agile" mean these days? VIEW POST


My own experience with agile is we look at the principles and then take what we need. Things like iterative development and client feedback are pretty useful to avoid wasting time. Continuous integration to make sure anything we write basically works is also useful. If you push a simple block of code and it doesn't even work, what's the point in expanding your code at all?

I don't know about traditional manufacturing processes like building a house or whatever, but the only thing that matters is whether the end result satisfies the goals, which means we should always be checking to make sure we're on-track. Don't spend time writing 10000 lines of code only to find out it's not what the client wanted.

What if the client doesn't like to be bothered so much with progress updates? Well that would be kind of their fault ain't it.

code of conduct - report abuse