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
"Waterfall” Approach
1) Gathering project requirement
2) Design : Design the software
3) Code: Write the code to implement that design
4) Test it
5) Roll it out
Lean Discovery of Business Needs
Assumes:
Business users can’t articulate an IT project’s requirements
Success only in their eyes
Three foundational principles of all lean methods
Short iterations
Less code
Active business participation
Curbing scope creep
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
Tame scope using 80/20 rule
Accountability without micromanagement
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
Promise: Will it help do something better, faster, or cheaper?
Change metric: dollars, percentages, or time?
Intended impact: Operational, strategic, or financial
Time to impact after project completion (years/ months)