Database Project Recovery

1
Database Project Recovery

• Libby Hare
• Members 2009

2
Aim of the session

• More than 50 of database implementations go
  wrong
• What can you do to put them back on track?

3
How many database implementations succeed
?
?
?
?
?
?
?
?
4
Implementing a database

• Resources, roles and responsibilities
• Data cleansing
• Data analysis, mapping and transfer
• Configuration
• Test (and test again)
• Documentation
• Training
• Go live and bedding in

5
Why are IT projects so difficult?

• Because
• IT often involves a lot of technical detail
• IT people often have difficulty explaining
  projects in lay language
• Sometimes its tempting to just give up trying to
  understand

6
and because

• it usually turns out that the technology is only
  ever a relatively minor part of the problem.

7
Why database projects go wrong

• Deadlines arent met
• Users arent happy
• People cant agree poor decision-making
• Costs are unexpected and spiral
• Problems with data migration and data quality
• Different supplier and organisation expectations
• Over commitment stress of project and day job
• Change in organisational objectives

8
Getting it back on track
9
Key controls

• Business case
• Planning
• People
• Risk
• Costs
• Project management
• Documentation
• Review / closure

10
Getting it back on track

• Business case

11
Developing the business case

• Issues
• Outcomes
• Options
• Recommendation
• Investment appraisal
• Risks
• Plan

12
Getting it back on track
People
13
People

• Sponsorship
• Engagement
• Decision-making
• Project manager
• Supplier
• Project team
• Communications

14
Getting it back on track
Planning
15
Planning
16
More discussion
?
?
?
?
?
?
?
?
17
For more information
Contact us at www.sayervincent.co.uk Or
email libby_at_sayervincent.co.uk