Please enable JavaScript.
Coggle requires JavaScript to display documents.
Antidotes to Business Failure of IT Projects - Coggle Diagram
Antidotes to Business Failure of IT Projects
Discover a project’s true business purpose
use "waterfall" approach
window of isolation : gather requirements - design software - write code - roll it out
problem :warning:
the waterfall approach erroneously assumes that a project team can identify business users’ latent needs at the outset (i.e., at 1 before the shaded steps in begin). The project team is likely to give the users what they asked for but not necessarily what they needed.
Second, a lot can change during the window of isolation where the programmers and users have little interaction. If a new requirement is discovered during the window of isolation then the waterfall approach requires redoing which may cause
huge cost.
The waterfall approach lacks the flexibility to hit a moving target and the mechanisms to incorporate feedback. The completed project then meets the business needs that the firm once possibly had in the past, not the ones it now has. This inflexibility can lead to a project’s obsolescence before completion.
•Business needs change
•Competitors actions
•Tech evolves
•Regulations change
Curbing scope creep
#1 threat: Attempting too much, with too little or too fast
Tame scope using 80/20 rule
MoSCoW rule applied to requirements by non-IT managers: – Must-have – Should-have – Could-have, but not critical – Wont-have this time, but maybe later
Must-do versus may-do in real options lingo
Accountability without micromanagement
Non-IT managers must hold team accountable for delivering business benefits
a project’s measurable organizational value (MOV) must come the business side
– Must balance what’s ideal and realistic
– Collaborative, involving all project stakeholders
– Ensures IT folks are evaluated first as business people
how does this project further our operational strategy?
Four elements:
Intended impact: Operational, strategic, or financial
Promise: Will it help do something better, faster, or cheaper?
Change metric: dollars, percentages, or time?
Time to impact after project completion (years/ months)