OutSystems explains the reason why Agile Software Development projects make economical sense.
Other Related Blogs
19 Responses to “Why does Agile Software Development pay?”
Leave a Reply
Get Immediate Access to My Profitable Home Business Opportunity
Simply Complete
the form below and I will take you inside my business and
show you how you too can get the lifestyle
you deserve.
Correct, good presentation. Very useful information..
What a joke!
Great presentation. It’s exactly what I’ve been looking for to show our sales guys and especially our customers. Thanks!
Excellent
Nice Movie Guys – atomicfeedback.com
excellent video
Good work!!!
Good JOB!
I like the presentation. I like how he explains the value in a clear and visual manner.
From a gut level, it makes sense. I’m in the choir here. I’d like to see how what the graphs show are supported by evidence, otherwise it feels like theory–why does waterfall always declines into an end of life situation (or support via case histories)?
The unsaid assertion is that waterfall can’t produce software in a short period. Make this assertion explicit and support with evidence.
<3 i love u LOVE MEEEEE Y
What a joke!
Great movie, going to use it on a presention on how to work Agile. It will be perfekt.
Thanks guys!
/patrik
Nice presentation.
Nice clear presentation on the power of iterative development and continuous deployment.
i don’t understand, none of the statements were backed up with an evidence.
why are agile versions increasing? why are waterfall decreasing? why is agile version getting higher than waterfall?
Good one !
@269d Because 70% (I leave the researching for u) of software projects fail to deploy on estimated time and budget (and it was worse in the past). Industrial engineers taught us waterfall but you tell me if it has worked outside universities… Building software is not like building a bridge.
@269d sorry if I didn’t understand your question…
In the graph you can see the time gap between versions in agile is shorter, the theory says it should be 2 weeks maximum to get a functional, operable product that only has an extra feature per version. Then you get feedback from the user, refine requirements and repeat.
The feedback rises the value in both cases in equal way, just like time lowers it in an equal way. The critical difference is the time it takes to refine requirements.
Really nice presentation, thanks.