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
Antidote #1: Discovery of Purpose
Use "Waterfall" Approach
Gather the business requirements
Design the software
Write the code to implement that design
Test it
Roll it out
Major problems
The approach assumes that a project can identify business users' latent needs at the outset.
The project team likely to give user what they asked for but not necessarily what they needed.
A lot can change during the window of isolation where the programmers and users have little interaction.
change during the window of isolation cause huge cost
Antidote #2: Curb Scope
The biggest threat to IT projects: Attempting too much, with too little or too fast
Using 80/20 rule
Non-IT managers can help identify the 20%
classifying each major requirement into one of MoSCoW classification.
Must have requirement
the 20% requirements that a project must prioritize to ensures line function do not make impossible demands
Should-have requirement
Could-have requirements, but not critical
Won't have this time, but maybe later
Antidote #3: Accountability without Micromanagement
2 ways to judge a project's success
Was it executed well in terms of its schedule, budget, and quality
Did it deliver the desired business results
Measures by an operational business
4 elements of MOV statement
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)