IT people is always right?

My professional career path gives me the chance to think about this question "IT people is always right?", IT people think most of time they have the power to put them in winner side and giving them the permission to be right always.
I worked for many years always I faced a conflict between the  IT and Business, my role as IT Manager gave me  the chance to be in the IT side but as a professional IT Manager I should keep the business satisfy and some time say for business "Yes, you are right", cause they know what is the business need more than IT,  when we think like this we will enhance our relationship as IT people with the Business people.

When you plan to build a success IT organization you should work to enable the needs of the business, remember you have to support business to deliver mission and to help the business to enable vision not fighting the business once you think like that you put your foot on the success way of your IT organization.

make sure the business is part of your success plan your support to the business one of the success keys  for your IT Organization.


My answer now is clear about the question "IT people  is always Right?" is of course "No".

IT Problem Management

Introduction

The IT Problem Management helps IT people to identify the root cause of an error, resolving a problem will fix the error which means stop these incidents from occurring in the future. Problem resolution and elimination of root cause often calls for applying a change to the configuration item in the existing IT environment.

IT Problem Management Definition

Wikipedia defines IT problem management as an IT service management discipline designed to “minimize the adverse imp

act of incidents and problems on business that are caused by errors within the IT infrastructure, and to prevent recurrence of incidents related to these errors”.

Which means effective IT Problem Management will reduce the cost, increase the availability and gives the IT people the time to focus on the business not on support and fixing errors.

IT Problem Management Objectives

The primary objectives of IT Problem Management are to prevent IT problems and resulting incidents from happening, to eliminate recurring incidents and to minimize the impact of incidents that cannot be prevented.

IT Problem Management Benefits

The main benefits from IT Project Management:

•  Improving IT service quality. Remember that high quality and reliable service is very good for business. 

•  Reducing number of incidents. Proactive problem management is instrumental in reducing the number of incidents that interrupt the business/organization every day.

• Build a known error database (Knowledge Base). Documenting the known errors and solutions will reduce the number and impact of problems.

•  Give the IT people the opportunity to start self-learning. One of the main concepts for IT problem management is learning from past experience. The process document all previous errors and problems to identify trends, and the means of preventing failures and of reducing the impact of failures, resulting in improved productivity.

•  Increase the rate of fixing errors by the Service Desk. Problem management enables the Service Desk to know how to deal with problems and incidents that have previously been resolved and documented.

IT Problem Management Processes
1. Identifying and Reporting Problems

A problem can be generated in a number of ways like:

• Problem form by IT staff member.

• Generate a problem from an incident by IT staff member.

• Service catalog allows user to log problems.

•  A problem can be generated from an email.

A problem can be associated with a configuration item using CMDB (I will talk about it in future) to help the problem management team see the affected item and its relationships to other configuration items and to measure the impact on the business.

Resolving problem can be done by a user or group. Which means the problem can be assigned to a user or group and this can be done manually or automatically.

The problem can be generated from an incident. This gives the problem management team the opportunity to quickly refer to knowledge base already generated and find the solution or start workaround to reduce the problem impact on the business. Once the problem is solved all related incidents will be solved.

2. Investigating and Updating Problems

Problem was identified and reported in the first step, the second step is to know what is the problem, what it is impact on business and do updates on the problem.

In this stage the user or group was assigned to solve this problem will start solving the problem and update the problem status and information.

Problem can be associated to Service Level Agreement (SLA) to monitor the progress of the problem according to the defined rules in the SLA. As time passes, the SLA will dial up the priority of the problem, and leave a marker as to its progress. SLAs can also be used as a performance indicator for the problem management team.

3. Resolving Problems

If a problem needs a change in order to be resolved, it is possible to request a change (Read My previous blog “IT Change Management”), which will be then resolved using the change management process.

Once you start saving the problem by using change management the problem will be closed when the change is close.


Workflow Sample

Here is a sample of Problem Management workflow (The workflow for IT Problem Management is configurable; it depends on the work environment).

Don't Do This Mistake #4

Introduction

Most of IT managers have a backup solution in case of disaster; and IT Managers was set the tools (softwares and/or hardwares) to implement backup solution to meet business needs.

Definition

Backup solution is a tools (software and/or hardware) to safe your data on storage media (Tape, HD, DVD, etc.).

Why backup solution?

Backup solution is the key weapon in case of disasters (i.e. lost data, hardware failure, natural disaster, etc.). Once you lost the information stored on your IT Assets the business will affect negatively. So you need the backup to recover the business.

Testing Backup Solution

Backup solution is the key part of your backup plan, and you have to integrate all backup plan parts to get the value from backup solution (what we are taking about in this post). The big mistake I want to mention it is not testing your backup solution.

Testing your backup solution is a very important part of your backup plan and it is the key to make sure your backup solution is working correctly. Don’t forget testing your backup solution you don’t know when you need to use one of your backup it is working normally and the backup was taken correctly.

Remember that

Backup solution is the key of your backup plan this key must be tested to make sure this key will work normally when you need it.

And also remember

Not testing your backup solution is a big mistake.

Don’t Do This Mistake #3

I have a problem, the system is down and I don’t know too much technical information about this system. I will try to solve it by myself; yes I will try many times to fix it. I am the manager and it is a weakness point if asked someone for help. Stop please you do a very costly mistake by trying to solve the problem without asking for help.

Some problems appears in the IT environment for the first time, don’t expect to know everything about everything in your IT environment, keep improving your skills by reading, asking and sharing knowledge to know more and being the manager doesn’t give you the power to solve all problems.

Once the problem appears do the right thing and seek help. The success key for the IT Manager is not know the correct answers; it’s being able to find them and implement a solution as quickly and cost effectively as possible. Don’t hesitate to ask the experts if it necessary.

Not asking for help is one of the biggest mistakes in the IT Managers life. It is not a weakness point of you if you asking someone for help. Asking for help gives you the opportunity to solve your problem faster and reduce the cost and time.

Why you should ask for help?

Many reasons to ask for help:

· Solving problems faster.

· Reduce the cost and time needed to solve the problem.

· Reduce the risk of trying solving the problem without prior knowledge about the solution.

· Improve the quality of IT services.



How to ask for help?

1- Persuading yourself that you need help by telling yourself you need help and what you need exactly from help.

2- Seek for one can help you and be positive with your helper, remember that it is not a reason to feel weak or stupid it is a sign of strength.

3- Understand your helper’s advice.

4- Say thanks for your helper’s.

5- Don’t afraid to ask for help again if needed.

IT Change Management

Introduction

Change is inevitable in every IT work environment it is includes but not limited to (hardware, software, processes, etc.). Many types of changes in work environments, as example:

1- Strategic changes.

2- Governance changes.

3- Technological changes.

4- Operational changes.

Some of the changes should be applied, for example, changes that come from the government.

Definition

The change management is an IT service management (ITSM) discipline. The process responsible for controlling the life cycle of all changes. The change management is a set of procedures, processes, and processes to manage all changes in the work environment with minimum negative effect on the IT service and/or business.

Change management objectives

The primary objective of Change Management is to apply beneficial changes, with minimum disruption to IT services.

Another objective of Change Management is to ensure that you applying the standardized methods and procedures for efficient and prompt handling of all changes to control IT infrastructure, in order to minimize the impact of any related incidents.

Change Management Processes

1. Raising and record changes

Many of ways can generate a new change record:

• Request a change from an incident.
• Request a change from a problem.
• Request a change from a business need.
• Request a change through a service catalog.
• Request a change from an email

2. Assessing and evaluating changes

Once a change request is in place, the change management team must populate the change request with as much information as possible in order to fully assess the requested change.

Information that can be collected :

• Priority
• Category
• Impact
• Urgency
• Schedule - Includes a requested by date, a planned start and end date, and work start and end dates. This can be integrated with Outlook so that the change schedule will appear in Outlook's calendar. Note that changes made to the schedule in Outlook will not change the change record.
• Change/Roll Out Plan/Backout Plan/Test Plans
• Approvers - All CAB members.
• Related Problems - All related problem to the change will be associate to the change form. 
• Related Incidents - All related incident to the change will be associate to the change form.
• Affected CIs - a list of configuration items (from the CMDB) that will be affected by the change.
• Impacted Services - a list of business services (from the CMDB) that will be affected by the change.

3. Planning Changes

Changes can be planned directly in the change record, but for complex, multi-step changes, Project Management allows specificity of planning. 

4. Authorizing Changes

Any change should be reviewed and approved by the Change Advisory Board (CAB)  before put it into production environment. Usually, the CAB consist of a group of people with different perspectives, backgrounds and areas of expertise. Their function is to review the change from a process and governance standpoint to assure that all foreseeable risks have been identified and mitigated, and that compensatory techniques are in place for any elements of exposure (things that could go wrong). The development team and the change sponsor will present the change to the CAB. Evaluation of risk will be the focus. Implementation strategies, communication to affected stakeholders, backout plans and post-implementation monitoring are elements on which the CAB is required to focus. The CAB is not responsible for determining if the change is appropriate – that decision has already been made. The CAB is also not responsible for determining if the change is cost effective. Again, that is strictly a business decision.

5. Closing Changes

Once the change has come to an end, and the change has been tested and confirmed, the change can be closed by changing the state. If the change was generated from an incident or problem, you have to close all related incidents and/or problems.

Workflow Sample

Here is a sample of change management workflow (The workflow for change management is configurable, it depends on the work environment).

IT Change Management Workflow Sample

Don't Do This Mistake #2

I love my work too much so I will work more and more!  My team not have the capability to do the business as I do! My business will not live if I take a vacation! So I will not take a vacation, be careful about what you trying to do. This is a formula for disaster.

Do you plan to do everything by yourself, what about vacations?  No plans done for rest? If you don't plan for your vacations please do it right now.

Why you need a vacation?

There are many vacation benefits; I will list a few of them below:

1-      Improve your mental skills.

2-      Reduce stress.

3-      Improve your physical health.

4-      Check your employee skills.

5-      Test what your leave effect on the business.

Do a favor for yourself, family, and business and take some time off. Really you need this do not try to burn yourself.

Simplified IT Management & Operations

I engaged to a new job 1 month ago and the first thing I did is thinking about my mission, I read my job description a lot and I reviewed the company mission, vision and values to create a sentence collect all these information, my sentence is “Simplified IT Management & Operations”.

When I looked to this sentence many times I found it very hard to implement and we have to start inside the company before we go outside, I spent a lot of time to set the market plan to help the company to achieve this mission, but really I found it very interesting mission and we can implement it easily.

Many of IT people thinking the processes and procedures are developed to make the work more complex, in my point of view is procedures and processes help us to simplify the work and help us to automate the work specially those repeated tasks.

What is the simplification mean?

In my point view I see the simplification is set of procedures, policies and procedures set to control and organize the work and IT infrastructure and applications aligned with those polices procedures and processes. Awareness is needed also to do the simplification better.

Simplifying IT Management & Operation gives the IT people the opportunity to focus on the business, you need very good communication skills to contact with business, just keep in your mind the business people is your customer and you have to keep them satisfied.