Waterfall vs AgileScopeSchedule CostFix ConstraintsEstimateWaterfallScopeSchedule CostAgile
Waterfall works hard toprevent changes inscopeWaterfall vs Agile Agile expects andembraces scope changeand focuses ondelivering businessvalue quickly instead.Core project management best practices still veryrelevant and necessary even on an agile project
Do IT projects take too long to deliver? Is there a tendency to throw requirements and deliverablesover the fence to the next phase? Does the project fail to deliver on expected business value?Questions over Waterfall“Agile projects are successful 3 times more oftenthan non-agile projects…”
Fast time to valueCost-effective solutions which embracechangeIntuitive BI for everyoneWhy Agile BI Works?
No need for a complete Data Warehouse design beforestarting Instead an iterative and incrementaldevelopment Fast prototyping encourages user feedback=> fine tune requirementsAgile BI - Time to Value
BI requirements change on a monthly basis Deterministic Data Warehousing not aligned toever changing environment Agile is better suited to change Agile BI characterised by a low Total Cost ofChangeAgile BI - Embrace Change
Business users require access to answers today notnext week Cannot rely upon IT or report writers to deliver quickly The tools must support the businessuser to satisfy their own requirementsAgile BI - Intuitive BI
More frequent delivery to production Less documentation, more meetings and verbalcommunications Less pretence on long term strategy Immediate QA Multiple leaders, more teamworkImplications of moving to Agile BIfrom Waterfall BI
Use Waterfall … When the end state is well known, and requirementsare clearly defined and documented When the organisation process and business is stable Use Agile … When the end state is unknown or changing rapidly. Start-up or business in changeWhich approach to use?