IT-Checklists.com - The eBook-Shop with Checklists and Templates for Professionals
Phase :: Achieving Operational Readiness
Your systems are up and running, business is growing but still small.
Don't lean back
- We don't talk about "optimization" now, but there are many more important issues left.
Using this templates you will achive more in less time!
- Are you sure that after a fast startup you know which application connects where ?
- And even worse - which testing environment created by copying the production system still connects to other production systems?
Start now to DOKUMENT your Interfaces - and the responsibilities on both side!
Utilize the lessons learned during the blamestorming after next incident - and fill in those documentation template!
<! -- ================================================ EAI Interface Checklist ========================= >
Data Exchange between applications is the MAJOR Challange for Application Support!
- Use this template to document and check your application interfaces
And what about Operation Manuals for all systems ?
You might have a few months left until the first big audit - Try to fill the following template for one system!
- You will realize that that needs some effort
- You will realize that some incidents would not have happend if...
- - and we are sure that you will immediately rank for new systems the operations manual as important mandatory deliverable of the project!
<! -- ================================= Template for an Operations Manual ========================>
Of course you do know that an Operations Manual is mandatory part of the delivery, but you might be surprised about
the required effort to create a really comprehensive Operations Manual!
Note: When purchasing a commercial packaged application, the vendor's manuals will not cover all aspects of operating the integrated application!
Ask the customer which chapters you do have to deliver and which you do not need to deliver!
Using this template the customer will understand you estimations of mandays and costs for this deliverable!
You detect the first operational shortcommings of your new applications?
- Avoid those for the next applications comming soon by asking for important requirements for manageability and reliability!
This simple Checklist for Production Release is a good starting point....
<! -- ================================= Checklist for Production Release ========================>
Reading this checklist at the very beginning of the project will reveal a lot of steps which otherwise might be forgotten in the time- and budget estimation!
This simple checklist with 101 items targets small and new companies with IT-department on a low maturity level and should bridge the time until change management and release management are fully implemented according best practice.
For new projects use as soon as possible following much more detailed....
<! -- ========================================== Non-Functional Requirements ========================== >
No matter if you are selecting a software package or if you planning custom development, the requirements must be defined in both cases.
Each requirement detected later costs much more than this template!
More than 150 requirement for availability, reliability, manageability, Backup and Recovery, resuming crashed jobs, configuration requirements, archiving / restore....
(And don't even think about the additional delay...)
<! -- ================================= Application Interfaces ========================>
Requirements-Checklist and Template for Application Interfaces. It's quite sure that the new application needs to be integrated with existing applications, and that might be a MAJOR part of the project!
Therefore you should ask those important (vendor- and tool independent) questions about the interfaces before selecting and implementing the application !
(Requirements checklist 65 Requirements / 36 pages, template for operational documentation 8 pages)
<! -- ================================= Database SLA / OLA ========================>
Introducing Service Level Management (SLM)
and the position of a Service Level Manager
is an important step in this phase of achiving operational readiness.
Use this template to establish the Service Catalogue for databases....
- you will need this when the Service Level Manager will establish the first Operating Level Agreement (OLA)
with the database team.
Service Level Management is one process of service delivery. In this phase the Service Level Manager will contact you and present you a huge Service Catalogue and Service Levels for the Services offered.
Read it before you estimate your budget!
This document is not for the DBA, it's primary for YOU, the project manager as YOU need to budget and order those services which are appropriate for your project.