PART 1: Is Agile a bad idea? Or is it your inertia?
UK Wasting ￡37 Billion a Year on Failed Agile IT Projects is an eye opener!
Change i$ Co$tly! IT re-engineering and digitisations comes with a HUGE price tag regardless of development is done in house or not.
The business cases may promise that general housekeeping will be more efficient and IT implementations will facilitate productive work in an organization.
To be on the safe side & not side line from the topic, let’s take a Birds eye view, of primary causes of project failures in general as published in https://financesonline.com/35-essential-project-management-statistics-analysis-of-trends-data-and-market-share/
?
Considering ‘Change in organisation priorities’ and there by ‘change in project objectives’ both due to external factors.....however, 35% is caused by ‘Inaccurate requirements gathering’ and can we turn a blind eye is an internal factor?
Below is a graph showing $$Cost of Change$$ is increasing exponentially with each System Development Life Cycle (SDLC) phase progresses!
Considering what is at stake, how would you decide which project management methodology to adopt? Should your IT project or initiative select Agile or Waterfall?
Agile is accepted at large scale, so Adopt Agile? OR Abandon Agile and go against the tide?
Keen to know what you decide.