01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

348<br />

CHAPTER 15 THE BIG PICTURE AND THE TEN DELIVERABLES<br />

Scheduling: This section specifies what advance notice is required, what information<br />

needs <strong>to</strong> be supplied by the reques<strong>to</strong>r, what forms completed, and scheduling<br />

constraints if any.<br />

Prerequisites: Clearly documenting the prerequisites improves the chances that<br />

they will actually be met. You might want <strong>to</strong> include a “nice <strong>to</strong> have” section.<br />

Testing<br />

This section describes what testing should be completed in a labora<strong>to</strong>ry setting before the<br />

“real work” can begin. Here are the reasons for testing:<br />

<br />

a labora<strong>to</strong>ry setting that duplicates the targeted production setting may uncover<br />

deficiencies in the procedure.<br />

<br />

last executed the procedure. Also, the Standard Operating Procedure may have<br />

omitted some of the details, and practice in a labora<strong>to</strong>ry setting will allow a less<br />

experienced performer <strong>to</strong> supply them for herself or himself.<br />

<br />

not be considered necessary, because the work is truly routine; for example, adding<br />

a user. In other cases testing may not even be practical because of the huge<br />

effort required <strong>to</strong> duplicate the target environment in a labora<strong>to</strong>ry setting. If testing<br />

is unnecessary or impractical, then the author of the SOP should indicate as<br />

much and explain why.<br />

Approvals<br />

This section describes whose approval is required and the pro<strong>to</strong>cols <strong>to</strong> be observed—for<br />

example, verbal approval, written approval, formal meetings, advance notice, and so on.<br />

I have observed that most IT organizations fall in<strong>to</strong> one of two categories:<br />

. The performers are given free<br />

rein <strong>to</strong> take suitable action. Performer morale is high but the situation is certainly<br />

not desirable from a management viewpoint.<br />

<br />

permitted <strong>to</strong> do the slightest work without the approval of “change czars.” Performers<br />

chafe under the scrutiny and complain of delays and the effort expended<br />

in submitting paperwork before artificial deadlines, attending change management<br />

meetings, and answering questions from “change czars” who do not have<br />

expertise in the subject matter.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!