Timeline for How to provide traditional upper management early analyses in an agile project?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 13, 2018 at 19:46 | comment | added | RibaldEddie | I think you’re getting it. Don’t justify the cost of the entire project before starting. Instead, justify enough cost to run the initial stages for a few weeks and then see what is delivered. If it has value, keep going. If not, change direction and deliver something else. Keep iterating, and you’ll hit on something valuable a lot sooner and for less money than if you tried to hit a target a year away. | |
| May 11, 2018 at 19:47 | comment | added | Barnaby Golden | It's a classic dilemma. If you want give the CEO gap and cost analysis on day 1 then you will need to nail down requirements and almost eliminate technical/project risks. That is the opposite of agile, which says nailing things down is pointless, much better to accept that change will happen and plan accordingly. | |
| May 11, 2018 at 16:32 | comment | added | Sarov | I'm aware there are ways to provide the metrics, but the question posed to me was how to provide, at the beginning of the project, gap/cost analyses in order for the CIO to justify the project to the CEO. Am I correct in interpreting your Answer as "Don't; just fail fast and you won't need to justify at the beginning."? | |
| May 11, 2018 at 15:42 | history | answered | Barnaby Golden | CC BY-SA 4.0 |