Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 7 : MANAGING PROJECTS, Antidotes to Business Failure of IT…
CHAPTER 7 : MANAGING PROJECTS
Antidotes can be as vaccine
Discovering latent business needs
:- to search hidden requirement
Curbing scope
:- limit the scope of the requirement
Explicit accountability for business benefits
:- to highlight clearly what company can benefit from each IT features
Assume that business users can't articulate an IT project's requirements and assume that success only in their eyes
Business involvement
:- get decision maker in the user requirement capture process
C
ollaborative
R
epresentative of biz users
A
uthorized to decide
C
ommitted to business value
K
nowledgeable
Rapid iteration
:- to repeat the process fast until solution found and then move to the next process
Each iteration hands users a crude but functioning system with small subset of functionality
Clears misunderstandings earlier - cheaper to fix
Less code
:- avoid lengthy line of code, make it short and simple
Every line of code explicitly justified with business objectives
Bakes in quality and curbs costs in two ways :
Plan of to handover and install the IT system to be used by users
Abruptly replace
:- by quickly replacing the old system
Run in parallel
:- by running concurrently with the old system before you uninstall it
Chunk rollout
:- install and run the system portion by portion
Antidotes to Business Failure of IT Projects
Lean Principles
Rollout Strategy
CRACK Business Team Members
Software with more code is buggier
Lesser code lowers upfront development costs
How completed project is rollout out to users :