Part 3 of 3: What to Do in a High Level it Review

<h1>Part 3 of 3: What to Do in a High Level it Review</h1>Author: <a title="Peter Groom" href="http://www.articlesbase.com/authors/peter-groom/62012.htm">Peter Groom</a> This is final one of a three part article on how to carry out a high level IT review. The first part looked at how to break the problem down into more manageable chunks and then proceeded to review the Software aspects. The second looked at the Infrastructure considerations while this, the final part, reviews the Operations and Change aspects.  Operations The first operational question is around availability. For example, what is the current uptime percentage and how are downtime windows communicated and approved? How these questions are answered will tell you a lot about how robust and mature the operational processes are. The next area of questioning is about how the software is administered, by whom and under what circumstances. For example, if there is a CMS (Content Management System) then questions on what can be changed, by whom, when and how are all valid. This is important from not only a security view but also from an auditing/governance perspective. If financial transactions are being handled then the Fraud processes need to be robust. Therefore, asking questions about those processes is key. It is worth ensuring that it is clear what financial rules and regulations the operational processes are designed to work with. Finally. an understanding of how much Disaster Recovery is in place for the production systems is important.  Depending on the risk profile, it may not be seen as critical but it is worth asking the question. Operations Quick Check-list - What is the current uptime percentage and how are downtime windows controlled? - How does the administrator access the system to control it? - Describe the Fraud processes - Describe the current state of Disaster Recovery for all production systems Changes The final area to consider is that of changes to the system. This should cover bug fixes, small enhancements and upgrades. Understanding the process and who will carry out the work is essential, as is being clear on who approves the changes. There is a reason that change freezes occur around high value events – changes cause the majority of operational problems with a system. Therefore, understanding who tests what and when is of particular importance. An interesting question to ask is how much of each stage is specified. The answer to this question permits an understanding of what methodology is preferred. Also worth asking is whether an IT roadmap exists or not? If so, how aligned to the end customer(s) is it? Finally, is there a technology strategy for the software and its platform? Changes Quick Check-list - How often can or would the software be enhanced or upgraded? - Who tests what and when do they test it? - How much of each change is specified - Does an IT roadmap exist? - What is the technology strategy? This completes this three part article and as you can imagine, only scratches the surface of this wide ranging and challenging topic. Depending on the situation, some aspects will be more important than others. For example, if the software is not going to be hosted by the provider then the Infrastructure considerations are clearly not as important. I hope that you found the article interesting and please feel free to contact me on my web site at <a href="http://www.petergroom.com"><a target="_blank" href="http://www.petergroom.com">http://www.petergroom.com</a></a> Peter GroomAbout the Author: Peter Groom has been in IT & Technology for 16 years, the last 5 have been spent turning around problem IT departments. More information on him can be found at <a target="_blank" href="http://www.petergroom.com">http://www.petergroom.com</a> 
 
He is also the Managing Consultant at Network Knowledge - <a target="_blank" href="http://www.network-knowledge.co.uk">http://www.network-knowledge.co.uk</a>Article Source: <a href="http://www.articlesbase.com/">ArticlesBase.com</a> - <a href="http://www.articlesbase.com/management-articles/part-3-of-3-what-to-do-in-a-high-level-it-review-523319.html" title="Part 3 of 3: What to Do in a High Level it Review">Part 3 of 3: What to Do in a High Level it Review</a>

This is final one of a three part article on how to carry out a high level IT review. The first part looked at how to break the problem down into more manageable chunks and then proceeded to review the Software aspects. The second looked at the Infrastructure considerations while this, the final part, reviews the Operations and Change aspects.

Operations

The first operational question is around availability. For example, what is the current uptime percentage and how are downtime windows communicated and approved? How these questions are answered will tell you a lot about how robust and mature the operational processes are.

The next area of questioning is about how the software is administered, by whom and under what circumstances. For example, if there is a CMS (Content Management System) then questions on what can be changed, by whom, when and how are all valid. This is important from not only a security view but also from an auditing/governance perspective.

If financial transactions are being handled then the Fraud processes need to be robust. Therefore, asking questions about those processes is key. It is worth ensuring that it is clear what financial rules and regulations the operational processes are designed to work with.

Finally. an understanding of how much Disaster Recovery is in place for the production systems is important. Depending on the risk profile, it may not be seen as critical but it is worth asking the question.

Operations Quick Check-list

- What is the current uptime percentage and how are downtime windows controlled?

- How does the administrator access the system to control it?

- Describe the Fraud processes

- Describe the current state of Disaster Recovery for all production systems

Changes

The final area to consider is that of changes to the system. This should cover bug fixes, small enhancements and upgrades. Understanding the process and who will carry out the work is essential, as is being clear on who approves the changes. There is a reason that change freezes occur around high value events – changes cause the majority of operational problems with a system. Therefore, understanding who tests what and when is of particular importance.

An interesting question to ask is how much of each stage is specified. The answer to this question permits an understanding of what methodology is preferred. Also worth asking is whether an IT roadmap exists or not? If so, how aligned to the end customer(s) is it?

Finally, is there a technology strategy for the software and its platform?

Changes Quick Check-list

- How often can or would the software be enhanced or upgraded?

- Who tests what and when do they test it?

- How much of each change is specified

- Does an IT roadmap exist?

- What is the technology strategy?

This completes this three part article and as you can imagine, only scratches the surface of this wide ranging and challenging topic. Depending on the situation, some aspects will be more important than others. For example, if the software is not going to be hosted by the provider then the Infrastructure considerations are clearly not as important.

I hope that you found the article interesting and please feel free to contact me on my web site at http://www.petergroom.com

Peter Groom

Peter Groom has been in IT & Technology for 16 years, the last 5 have been spent turning around problem IT departments. More information on him can be found at http://www.petergroom.com

He is also the Managing Consultant at Network Knowledge - http://www.network-knowledge.co.uk

Rate this Article:

5 / 5 stars - 1 vote(s)

Re-Publish

Article Source: http://www.articlesbase.com/management-articles/part-3-of-3-what-to-do-in-a-high-level-it-review-523319.html

Article Tags: Vendor Selection, It Review, High Level Review, It Turnaround, Specialist It

Related Articles
Related Q&A

Latest Management Articles
More from Peter Groom

PPRA Tenders Pakistan – The Anomalies

By: Dr.Irfan Ahmad | 28/12/2009
PPRA (The Public Procurement Regulatory Authority) is an autonomous body responsible for defining regulations and procedures for public procurements by Federal Government owned public sector in Pakistan .It also monitors procurement process by public sector agencies/organizations in order to improve governance, management, transparency, accountability and quality of public procurement of goods, works and services.

Learn How to Manage an Office Cleaning Business

By: Jeremy Gray | 28/12/2009
Setting out to start your own office cleaning business is really something to look forward to. Being the boss of your own company provides a lot of perks and opportunities. But aside from the good things, there is also that challenge to succeed. If you are planning to open your own office business, below are valuable tips to keep you revved up and going:

Picking Apparel Displays That Stand Out

By: Tom Tran | 27/12/2009
Clothing displays are important factors when you think about how to promote quality apparel in your shop. You can get a custom fashion fixture stand so you make the most of the appearance of your apparel according to the collection. Once you are able to create a nice display of your clothes, it will lure more buyers to check out your products and direct them to purchasing your clothes.

PPRA and the challenges in combating corruption

By: Dr.Irfan Ahmad | 27/12/2009
Corruption in procurement is a serious issue in Pakistan. The formation of PPRA (Public Procurement Regulatory Authority) is the first sincere effort to take some control of the situation. The rules designed by PPRA provide a broad regulatory framework for transparent public sector procurements and are applicable to all public sector departments of central government. A strict compliance of these Rules can lead to a transparent and accountable process of procurements in public sector.

NNew Product Development Requires Fresh Perspective on ‘Creative’ and ‘Structure’

By: Robert F. Brands | 26/12/2009
New product development can be a misunderstood concept. Is the “product” actually a product? Or can it be a process? Is it a mandate from the C Suite? Or can it be a suggestion from the factory floor, the retail showroom, the Idea Box or a customer tip?

How Good Clothing Racks Give a Better Shopping Experience

By: Tom Tran | 26/12/2009
Clothes are one of the merchandise that people tend to buy most often. That is why it is wise for every store owner to think of innovative ways to display their apparel products to their customers. Using clothing displays to market your clothes has also come a long way in...

What is Automatic Data Capture?

By: Ray Feoli | 26/12/2009
It's been called the "Supply Chain of the Future" and is being implemented by more companies to streamline business proficiencies every day. So although you may have heard of automatic data capture, you may be asking, "What exactly is it?" In this article, you will learn some of the main...

Reasons Your Records Should Be in Digital Format Rather Than on Paper

By: Ray Feoli | 26/12/2009
During a time when digitally maintained records are an affordable and easy to implement solution to your document management needs, the real question should be, "Why WOULDN'T your records be in digital?" Let's go through some of the many reasons why your business would benefit by going digital with its...

Part 2 of 3: What to Do in a High Level it Review

By: Peter Groom | 15/08/2008 | Management
What would you do if you were asked to look at a new platform and you only had a day? As is often the case, let's assume that the software will be hosted by the supplier as well. This article is part of a 3 part series that answers this question.

Part 1 of 3: What to Do in a High Level it Review

A High Level Plan to Fix a ‘broken’ it Department?

By: Peter Groom | 02/06/2008 | Management
Having an under-performing or a down right 'basket case' of an IT department can be a significant problem for a business. This articles describes some of the techniques that can be used to turnaround those problem IT departments.