why_should_we_start_without_doing_a_complete_analysis
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
why_should_we_start_without_doing_a_complete_analysis [2016/06/22 08:25] – [Just Start] hpsamios | why_should_we_start_without_doing_a_complete_analysis [2016/07/03 13:38] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 26: | Line 26: | ||
But here is the rub. While you are doing all that analysis, you are not producing running code. Now if go back to the idea of [[how_does_the_agile_approach_allow_us_to_deliver_early|delivering high value items first]], there is another effect. | But here is the rub. While you are doing all that analysis, you are not producing running code. Now if go back to the idea of [[how_does_the_agile_approach_allow_us_to_deliver_early|delivering high value items first]], there is another effect. | ||
- | {{: | + | {{ : |
Take a look at the diagram. This is the same diagram in as before for a fictitious project. On it we see the the value delivered by an agile project doing highest value first. Compare this with a project where we do up front analysis before we start working any value delivery. How much time do you spend on detailed requirements? | Take a look at the diagram. This is the same diagram in as before for a fictitious project. On it we see the the value delivered by an agile project doing highest value first. Compare this with a project where we do up front analysis before we start working any value delivery. How much time do you spend on detailed requirements? |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/why_should_we_start_without_doing_a_complete_analysis.txt · Last modified: 2020/06/10 12:50 by hans