Please enable JavaScript.
Coggle requires JavaScript to display documents.
MANAGING PROJECTS - Coggle Diagram
MANAGING PROJECTS
Rollout strategies
Parallel rollout
safety net for glitches
prolong rollout period
Phased rollout
business pressure
Direct cutover
avoid for mission-critical IT
widespread impact of glitches
Antidotes to business failure
Curb scope
use 80/20 rule
80% business needs
20% project features
MOSCOW rule applied
Should-have
Could-have
Must-have
Wont-have
Accountability without micromanagement
non-IT managers play significant role in delivering benefits
elements to conduct operational strategy
Promise
Change metric
Intended impact
Impact time
Discovery of purpose
gather requirements
design
code
test
roll out
business and regulation need changes
flawed requirements
latent needs
Lean principles
Short iterations
clears earlier misunderstanding which is cheap to fix
uncover latent needs
Series of iterative sprints which 2-6 weeks apart
Less code
lesser codes means low cost in developing
others lean enabling ideas
constant automated testing
continous integration
Complicated software have more bugs
Active business principle
Business users contributes domain knowledge
IT unit technical knowledge
Then it converge towards prioritized requirements needed