@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.
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.
Really nice presentation, thanks.
heera542608 6 months ago
Good one !
Ranjit1742 1 year ago
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?
269d 1 year ago
@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.
DanyAlejandro 1 year ago
@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.
DanyAlejandro 1 year ago
Nice clear presentation on the power of iterative development and continuous deployment.
bobgower 1 year ago
Nice presentation.
kanbivideo 2 years ago
Great movie, going to use it on a presention on how to work Agile. It will be perfekt.
Thanks guys!
/patrik
MrMalmquist 3 years ago
This comment has received too many negative votes show
What a joke!
profetas 3 years ago
<3 i love u LOVE MEEEEE Y
mladinov2 3 years ago
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.
lancerkind 3 years ago 7
Good JOB!
god18 3 years ago
Good work!!!
MaxDaDeath 4 years ago
excellent video
Tgillin 4 years ago
Nice Movie Guys - atomicfeedback.com
bubbles2911813 4 years ago
Excellent
kashwin24 4 years ago
Great presentation. It's exactly what I've been looking for to show our sales guys and especially our customers. Thanks!
AgileNick 4 years ago 3
This comment has received too many negative votes show
What a joke!
profetas 4 years ago
Correct, good presentation. Very useful information..
Diabolus1987 4 years ago