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 : DISCOVER of PURPOSE
Begin to gather the projects requirements.
Design software
Create coding for the design
Test the coding
Roll it out
Problem of "Waterfall" approach
Assumes project team can identify the business users' latent needs at the outset
Many changes happened when window of isolation also the lack of communication between programmers and users
Waterfall approach lack of flexibility
Antidote #2 : CURB SCOPE
Always trying to do too much
Often too fast or with too few resources
MoSCoW rules are applied
Must-have requirements
Should-have requirements
Could-have requirement, but not critical
Won't have this time, by maybe later
20% requirements of the project must prioritize
Antidotes# 3: ACCOUNTABILITY without MICROMANAGEMENT
To delivered business benefits, team accountable must be hold by Non-IT managers
Project's Measurable Organizational Value (MOV)