Please enable JavaScript.
Coggle requires JavaScript to display documents.
Antidotes to business failure of IT projects, Rollout strategies, Lean…
Antidotes to business failure of IT projects
Discover a project's true business purpose
Waterfall approach
lack the flexibility to hit a moving target and the mechanism to incorporate feedback
Lead to project obsolescence before completion
Process
Gather requirement
Design
Code
Test
Roll-out
solution to waterfall approach
Business users cant articulate an IT project's requirements
Success only in their eyes
Lean discovery of business need
Active business participation
prioritize what actually need
business user integrally participate throughout the IT unit
C-R-A-C-K business team members
Collaborative
Representive of business users
Authorized to decide
Committed to business value
1 more item...
Build the right system
Short iterations
to do a project in series of iterative sprints of 2-6 weeks apart
iteration increase an IT project likelihood of delivering business into two-ways
clear misunderstanding earlier
Uncover latent need
Build the right system
Cheaper and faster
Less code
every LOC explicitly justified with business objectives
Software with more code is buggier
Lesser code lowers upfront development cost
Cheaper and faster
Bake quality
Curbing scope creep
Biggest threat to IT project almost always is trying to do too much too fast with too few resources
Solution
focus on one or two really important business that you hope project to achieve
Non IT manager helps in identifying the 20%
MoSCoW rule applied
Accountability without micromanagement
Non IT manager must hold team accountable for delivering business benefits
MOV must come to business side
Intended impact
Promise
Change metric
Time to impact after completion
Rollout strategies
Phased rollout
Parallel one step further
introduce new system is less overwhelming
business pressure to get new system quickly up and running make it less feasible
Direct cutover
new system turn on after rollout date
widespread impact of glitches
avoid for mission-critical IT
Parallel rollout
Old and new system available simultaneously
Safety net for glitches
Prolongs rollout period
how you roll out completed project to its business user
usually IT unit pay insufficient attorney to roll out in rush to get system out and running
bad choice hurts receptivity jeopardizing payoffs
Lean principles
Appropriate for custom built business app and for software embedded in product
success triples if made smaller
Larger project always more challenged