Database Reference
In-Depth Information
11.7.13.5 Backup/Recovery
Skimp on it and you will SEvErELy pay for this later if,
heaven forbid, a user runs a clear script by accident or a freak storm hits your data center.
Believe me on this subject even if you disregard the rest of this chapter. oracle produces
a backup guide—get it, read it, understand it, and backup those databases, BSo and
ASo. Supporting files and data sources would probably be a good idea as well. Backup
and recovery is covered in Chapter 1 (Building the Foundation: Essbase Infrastructure).
Check it out for some great information around this topic.
11.7.14 Who Is the PM?
It might be very tempting to cede project manager duties to your partner. Don't do it.
If you want them to be a note taker, then have at it. They can take notes. outside of
that, you or someone in your organization needs to handle the project manager duties
of monitoring the project deliverables, milestones, resources, timeframes, risks, issues,
budget, and dependencies, along with keeping the project on track. remember, no mat-
ter how conscientious your partner is, you are one of a long stream of clients; if this one
goes south, he or she will just go on to the next one. In contrast, this is your job, your
project, and your potential state of unemployment. Who is more committed? observe
the consultants, learn from them where possible, ask for their advice, but
you
be in
control as this project's success or failure will directly impact you.
11.7.15 Tips for a Successful Project (Besides Everything I Already Told You)
here are some practical tips for a winning project:
• keep your business users involved and engaged to garner enthusiasm and buy-in.
• Do not simply replace a report with a solution, look to add value.
• Allow for some change to business requirements (
(This Is Not The Same As A
Change In Scope
).
• have business users build reports. This engages them directly and a business
user not being able to build a report because data elements are missing from a
design is courting disaster.
11.7.16 Why Do Projects Fail?
And, now the top 11 reasons Essbase projects (or any project for that matter) fail. yes,
another flashing lights moment.
1. Lack of management commitment
2. Lack of business/user participation and buy-in
3. Imposed, unrealistic schedule
4. unrealistic scope for the schedule
5. unrealistic budget
6. unrealistic expectations
7. untrained or unavailable staff
8. Constantly changing business requirements
9. Ineffective project management
10. Scope creep
11. Bad source data
Are any of these a surprise? They should not be and the information in the preceding
pages in this chapter should have mitigated any of these from happening to you.
