Please enable JavaScript.
Coggle requires JavaScript to display documents.
Antidotes to Business Failure of IT Projects, Antidote 1, Antidote 2,…
Antidotes to Business Failure of IT Projects
Antidote can be said as vaccine or penawar/penyembuh
Discovering latent business needs (to search hidden requirement)
Gather Project Requirement - Design Software - Write Code to Implement the Design - Test - Roll Out
Curbing scope (limit the scope of requirement)
Always trying/ attempting too much, often too fast with little resources
Way to prevent such complexity is focusing on important project using 80/ 20 rule
MoSCoW rule applied to requirement by non- IT manager to identify the 20%
20% satisfaction of a project features can meet 80% of bussines needs
MoSCoW classification:
Must-have requirements
Should-have requirements
Could-have requirements, but not critical
Won’t have this time, but maybe later
Explicit accountability for business benefits (to highlight clearly what company can benefits from each IT features)
There are two ways to judge a project’s success:
Was it executed well in terms of it schedule, budget, and quality?
Did it deliver the desired business results— measured by an operational business metric?
A MOV statement for any IT project must have four elements:
Intended impact. What operational, strategic, or financial impact will the project have?
Promise. Will it help do something better, faster, or cheaper?
Change metric. What is the unit for measuring impact (e.g., dollars, percentages, or time)?
Time to impact. What is the time to impact after project completion, measured in years or months?
Antidote 1
Antidote 2
Antidote 3