LO1,2,3 in One Edit
LO1,2,3 in One Edit
Ethiopian TVET-System
INFORMATION TECHNOLOGY
SERVICE MANAGEMENT
Level V
LEARNING GUIDE # 1
Unit of Competence: Establish and Maintain Client User Liaison
Module Title : Establishing and Maintaining Client User Liaison
LG Code : ICT ITM5 01 0710
TTLM Code : ICT ITM5 01 1010
Introduction
Once the critical business functions have been identified and analyzed in a business and an appropriate
new system has been implemented you will need to establish and maintain a liaison with the client. This
will enable you to accurately assess the required support needs for the new system. To do this you will
need to develop support procedures and assign suitably skilled people to the various support roles.
This unit will give you the knowledge and skills to analyze business IT systems and identify and establish
appropriate support systems.
The topics for this unit are as follows:
Activity 1
To practise identifying information technologies, complete Activity 1 – Identify information
technologies, located in the Activities section of the Topic menu.
What is a stakeholder?
A stakeholder is a person or organisation that has an interest in the system or is impacted by the
system.
As support is often negotiated towards the end of a project, you will have been working and
communicating with important stakeholders throughout the project. The most common stakeholder is
called the sponsor. The sponsor is the person or organisation which
is the major force behind the project
provides the funds for the project
has the authority to make decisions on support issues.
The last point is the most important one. You must find out who has the authority to sign contracts or
agreements and make decisions that will apply to the organisation. This may be a person (usually a
manager or director) or might be a committee (eg. executive management committee or council).
Although this person or committee may have ultimate authority regarding the establishment and
maintenance of client support arrangements, you may also be required to deal with others in the
organisation regarding these issues. This is especially true in our modern business environment where
people expect to be consulted over important business decisions which affect them.
The following are some simple methods for finding those with whom you will consult:
Meet with the project sponsor(s) and brainstorm; during a brainstorming session, everybody
puts in their ideas without evaluating them. This could help you find important stakeholders
quickly and easily.
Talk to people in the organisation. Find out who has an interest in the system and who is
affected by it. Who are the main users? Who will be receiving the support? Who will be
providing the support?
If you are in a large organisation, you can often find this document on the company’s intranet or by
asking the Human Resources department.
If you are in a small organisation, the organisational structure will often be quite simple. It will often
consist of an owner-manager-workers or something similar. In this type of business, there is often no
documented organisational structure.
Activity 2
To practise identifying stakeholders and project sponsor, complete Activity 2 – Identify stakeholders
and project sponsor, located in the Activities section of the Topic menu.
Organisational culture is the beliefs and values that exist - whether formally or informally - in an
organisation. Put plainly, it is ‘The way we do things around here.’
Organisational politics is closely related to culture. Culture is the values and beliefs; politics is the
things that happen - the informal and formal policies, procedures and working relationships.
‘Office’ and ‘Organisational’ Politics really are the same thing!
Formal politics is defined by the organisation’s official policies, procedures and structure. This is
easily understood from the organisation’s documents.
Informal politics tends to be undefined and undocumented. It consists of a complex interaction of
relationships between people in the organisation. At times, the informal politics is stronger than the
official version.
How can politics work for you, and why are politics and culture important in establishing and
maintaining a support system for business Information Technology?
Most support agreements are based on the official version (i.e. the formal organisational structure).
This is because informal politics are generally regarded as undesirable. However, this can fail if we
are not mindful of informal politics. If harnessed, informal politics can be a help in providing support.
As you can see from the diagram, the visible part of customer service (the ‘front line’ delivery) is
only the tip of the iceberg. It is supported by many things such as standards, systems, quality issues,
management support, etc. This is an important concept to grasp when approaching the set up of a
client support agreement. You should understand that by supporting IT systems that run in the
background, you are, in fact, helping make the business more efficient and competitive. Efficient
support of those parts of the iceberg that nobody sees results in better front line service to customers.
Levels of support
There are a number of ways to view levels of support. When discussing level of support, you may
mean the type of support that is to be provided. For example, we could offer the following levels (or
types) of support:
1. Informal peer support – workers help their co-workers with problems. The organisation can
provide training to key workers so that they are able to be called upon for informal support.
2. User support combined with other responsibilities – a dual role of IT support and other
responsibilities.
3. User support as a separate position or group – setting up a dedicated position such as ‘IT
Systems support officer’ or a unit such as ‘Technology Services Group’.
4. Help desk support – an internal or external support function that provides a broad range of
support for business IT systems.
5. Totally outsourced user support – an external provider provides all necessary support.
Activity 3
To practise identifying support requirements, complete Activity 3 – Identify support requirements,
located in the Activities section of the Topic menu.
Summary
In this topic we have looked at identifying the information technology in use in a business, the
stakeholders with whom you should consult when establishing a support agreement, the structure,
culture and politics of the organisation and – finally - the levels and type of support that is required.
Feedback
Table: Technology analysis
Already
Technology Description Support Required Provider
exists?
Software that
Customisation, training,
SlowBooks keeps track of
upgrades, bug fixes None No
software all accounts,
(patching), user support
stock, GST, etc.
Pentium 4 Upgrades, repairs,
Desktop Cloned troubleshooting,
PCs None No
IBM maintenance, backup,
Compatible customisation
User account management,
Linux Server security policy
Server with tape implementation, home folder None No
backup management, permissions
management, backup and
If you were building a website for the organisation represented by the organisational chart provided
above, who would you identify as the stakeholder in this project?
the business owner
the relevant manager
the local workers
the remote workers
all of the above
Feedback
Correct! All the staff (the business owner, the relevant manager, the local workers, and the remote
workers) are stakeholders as they either affect the project or are affected by it.
Almost! Go to the Reading notes and review the section on Identify stakeholders.
If you were building a website for the organisation represented by the, who would you identify as the
project sponsor?
the relevant business manager
the business owner
the local and remote worker’s union
There is no specific text for this topic. The following list contains some suggested texts and manuals
only. There are many software manuals, reference books and user guides available from libraries,
bookshops, CD- ROMS, or on the Internet. Ensure that the manuals used are written for the version
of the software being used.
Note that many textbooks only cover the technical issues of a topic and do not discuss client user
relationships. Techniques to improve client and team communication may be found in books on
management techniques and interpersonal skills.
Internet
4. A project sponsor is
a person or organisation that will take ultimate responsibility for the project
the person or organisation approving the funding for the project
all of the above
Feedback
Correct. A project sponsor can be a person or organisation that will take ultimate responsibility for
the project, or the person or organisation approving the funding for the project.
Almost! Go to the Reading notes and review the section on Identify stakeholders.
In order to verify support needs, you should contact the organisation and check that you have all the
relevant documentation. This would include a list of all the hardware and software that needs support,
as well as input from key stakeholders.
Verification is a quality assurance technique. You will not only do it before you draft the agreement,
but after as well. If you are thorough with your consultation, you will be less likely to miss things.
A support agreement that has missing key elements would be generally considered unworkable in
today’s present IT environment.
Tip: Sometimes it is difficult to document all the necessary components within a system (especially if
you are new to a workplace or you are a contractor hired to do a specific job). Attempt to understand
and view the system from a few different aspects.
Often IT staff state that a system or a format may be a certain type (eg when designing for the web, a
manager might say all resolutions are 800 x 600 and there is no need to design for any other types).
Try and check with a wide variety of users and see what they have. The time spent doing this may
save a lot of rework or support later!
Be thorough with your investigations and ensure you have all the resources and parameters for your
support project.
Customer expectations
When providing IT services, customer expectations can be a major challenge and often difficult to
define - particularly in the IT industry where change is constant.
Perceptions of performance can differ from customer to service provider. If customers believe that
your service is below standard or that you are unresponsive, then you are - regardless of your own
assessment.
Customer satisfaction levels can fluctuate, often depending on customer expectations or your
performance in providing service. It is important that you, as an IT service provider, monitor both
satisfaction and performance carefully. If satisfaction is increasing, you need to work out what has
changed in the way you provide service. If it is decreasing, go back to customer expectations and look
at how well you meet them. Changes in your business environment and that of the customers also
need to be closely observed.
Source: adapted from http://www.nkarten.com/mce.html
Establish procedures
What sort of procedures need to be established?
Incident management (for help desk) is actually one of the best ways of answering questions and
providing a professional support service.
Typical incident management involves the following steps:
Image: Typical Incident management procedure: 1 receive, 2 prescreen, 3 authenticate, 4 log, 5 screen, 6
prioritise, 7 assign, 8 track, 9 escalate, 10 resolve, 11 close, 12 archive.
In the diagram above, the user contacts the help desk or other support position. When the help desk
receives the call, the first step is to authenticate the call (i.e. that the caller is entitle to support and
that the problem is legitimate). The help desk should also give advice about problems that are
currently affecting all users (such as server outages).
Incident management or help desk software is used to log a call. The call is then screened to
determine priority and severity. Problems such as interruptions to a critical system (eg a flight check-
in system at an airport) need to be dealt with swiftly.
Finally, the incident is assigned to the appropriate person to deal with that particular problem.
Support staff can determine who is working on a problem, what action they have taken, and whether
or not they have resolved it through the use of tracking software.
(Adapted from: Beisse, F., A Guide to Computer User Support for Help Desk and Support Specialists
(2nd ed.) (Course Technology, Boston MA, 2001), p. 145-151)
Developing procedures for each of the incident management functions involves answering the
following questions:
What will be done? (the scope of the procedure)
Who will do it?
How will it be done? (eg onsite, over the telephone, etc.)
How long will it take?
Activity 1
To practise, complete Activity 1 – Customer support procedures, located in the Activities section of
the Topic menu.
Activity 2
To practise, complete Activity 2 – What makes great support?, located in the Activities section of the
Topic menu.
Reflect
Reflect on why performance indicators are important. What would occur if they were not included in
the SLA?
Feedback
Performance indicators are needed to clarify the process expectations and the customer experience.
This helps to quantify the process. Without it, management would find it hard to measure the
outcomes.
A performance indicator could be the amount of time taken to acknowledge an emailed help request.
The performance target in this case could be that all emailed requests are to be acknowledged within
one working day of reception. This enables managers to quantify the quality of the service by
measuring how much the service varies from its performance targets.
The indicators also help to measure services and staff performance. For example, they allow them to
offer bonuses, adjust training strategies and handle customer complaints better.
To clarify expectations: The SLA describes in detail the terms of service and the
responsibilities of the customer and service provider.
To incorporate indicators of quality: This is done by specifying performance indicators
and performance targets. For example, a performance indicator could be the amount of
time taken to acknowledge an emailed help request. The performance target in this case
could be that all emailed requests are to be acknowledged within one working day of
SLA examples
Summary
This topic covers the development of support procedures for the new system you have implemented
in an organisation. It addressed issues such as procedures, quality issues and standards and how we
incorporate these into a support agreement.
Activity 3
To practise, complete Activity 3 – Establishing a service level agreement, located in the Activities
section of the Topic menu.
Identify a company that has what you consider a great support philosophy and gather evidence to
support your viewpoint. Download support information such as a service level agreement and the
company’s mission statement. What is positive about the support philosophy in this company? One
example could be http://www.adobe.com/support/programs/policies/sla.html
Feedback
Look back at the Reading. What does an SLA contain? Check that the SLA for the company you have
identified meets the criteria for service level agreements set out in the Reading.
Review the document ‘Key Steps in Establishing a service level agreement’ available at the following
website: http://www.nkarten.com/sla.html#key
Comment on whether or not you agree with these steps.
Feedback
There is no specific feedback for this activity.
References
There is no specific text for this topic. The following list contains some suggested texts and manuals
only. There are many software manuals, reference books and user guides available from libraries,
bookshops, CD- ROMS, or on the Internet. Ensure that the manuals used are written for the version
of the software being used.
Note that many textbooks only cover the technical issues of a topic and do not discuss client user
relationships. Techniques to improve client and team communication may be found in books on
management techniques and interpersonal skills.
Internet
LO2: Test
This quiz will help you review the content you have learned in this topic.
Answer the questions, check the feedback at the end of each question and take note of the areas you
need to review.
1. What is an SLA?
Feedback
A service level agreement (SLA) is essentially a contract that binds a service provider to give a
certain level of service.
2. When developing support procedures for help desk staff, which point would – generally - not be
clarified?
What will be done? (the scope of the procedure)
Who will do it?
How will it be done? (eg onsite, over the telephone, etc.)
How long will it take?
What is the business case underlying the changes in the support procedures?
What actions will be taken first?
Feedback
Correct! When developing support procedures for help desk staff, the business case underlying the
changes in the support procedures would generally not be clarified.
Incorrect. Go to the Reading notes and review the section on Establish procedures.
3. What is often included in an SLA?
Feedback
The following are often included in an SLA:
the name of the provider, customers, etc.
the objectives of the service
the service provider’s responsibilities
the customer’s responsibilities
the process of requesting service (eg method of contact, forms to be used, etc.)
4. In your own words, why is a service level agreement necessary?
Feedback
A service level agreement is necessary for the following reasons:
Activity 1
To practise identifying skill categories, complete Activity 1 – Skills categories, located in the
Activities section of the Topic menu.
Having listed the technical and ‘soft’ skills required to deliver the support, you must now find the
person or people who have these skills.
There are several alternatives:
1. The person you need already works in the organisation either in an IT role or a non IT role.
You may be able to negotiate to obtain that person for the support team.
2. The person you need does not yet work in your organisation. If you find yourself in this
situation, you have several options. For example, you could
Prepared by: ICT DEP’T Page 23
Axum Polytechnic College Establish and Maintain Client User Liaison
Training, Teaching and Learning Materials Development Lo-1
advertise for a new employee and go through the interview and selection process
engage an employment agency to find the right person for you (eg
http://www.seek.com.au/
3. The skills you require are too diverse, and it is therefore unlikely that any one person has all
of the required skills. If you have this situation you could
employ more than one person
outsource part or all of the support function.
Again, it is vital to realise that the interview process is often a poor way to select the best applicant.
Interviews generally favour applicants that are confident, can verbally express themselves, know the
jargon and sell their ‘assets’.
If at all possible, attempt to ask for samples of their work or employ them for a short period to assess
them. Generally, one can gain a good idea of someone’s skill levels within a few days.
If this is impossible, then attempt to look at short-term contracts before offering full-time
employment. This also works both ways, as the employee is able to gain an idea of the work
environment and can assess whether it suits them.
Activity 2
To practise reviewing and writing job placement advertisements, complete Activity 2 – Review job
placement ads, located in the Activities section of the Topic menu.
Technical skills
In the IT industry, technical knowledge, experience and hands-on skill is essential in most areas.
These days, most staff specialise in particular fields:
security
web (eg web design, flash, multimedia)
desktops
operating systems (eg Windows/Linux)
networks (eg Novell)
databases (eg Oracle)
project management
business analysis
software development/programming.
These areas are not always distinct areas of the industry. Many IT professionals’ skills are broad and
encompass many of the above areas. However, it should be noted that few have comprehensive
experience in all.
Verify availability
The person or people you decide you want on your support team may or may not be available.
Normally, when you offer somebody a position of employment, they must tell you if they accept that
offer or if they decline the offer.
The person you want may be available but there may be complications, such as the following:
they may not be available full-time
they may not be available to work at the times your customer needs support
they may not be available to start immediately
they may be in the process of attending numerous interviews and they could play one
employee against each other.
In these cases, you may decide to offer the position to somebody else or negotiate with the person you
have chosen.
Also, as many services are now available twenty four hours a day and technology is changing to
make telecommuting easier, it may be worthwhile discussing other possibilities such as part-time, late
or early starts, telecommuting, etc.
Remember: a satisfied worker often proves to be a productive worker, and if your objectives are
being met, sometimes some flexibility is a useful strategy. This may not work in all industries, but it
certainly has merit in the information technology industry.
Provide support
Now that you have the support agreement and suitably skilled staff, you are ready to start providing
the support. The support will be provided in accordance with the service level agreement.
You will not only provide the customer with support, but you will also do some reporting. This is
covered under the next heading ‘Obtaining feedback’.
You will probably find that there will be some tension between you and the customer regarding the
provision of the service.
The most common problem is a lack of clarity regarding what is supported and what is not or the
customer’s expectations regarding the support.
Obtain feedback
Feedback is a necessary part of the delivery of the support function. It is information that you receive
from the following people regarding the delivery of the support service:
your support team
your customer
any other appropriate person (eg. hardware or software vendors).
Why?
Why do we need feedback on delivery of support?
to learn of problems occurring in the delivery of the service. This can help you be proactive
and head-off conflicts before they occur.
to improve your service to the client by finding out where the problems are occurring and
fixing them. These problems may be recurrent problems in the system you are supporting or
problems with the delivery of the support.
How?
Feedback may take the following forms:
reports – as detailed in the SLA. These may include the number of support issues dealt with
over a fixed period of time, the time taken to resolve problems and any outstanding support
issues.
meetings – may be detailed in the SLA, but in any case, it is a good idea to meet with your
support team and your customer to discuss the support service you are providing. This can be
an informal meeting over coffee or a formal meeting with an agenda.
impromptu feedback – you should always be open to receive feedback from any source at
any time, especially if it means that – ultimately - you can improve the service you deliver.
Many professionals believe that comments received back in forms or evaluation sheets are not always
completely honest, as many do not like criticising via writing. Speaking to a cross-section of users in
an open and frank way is a much better way of obtaining accurate, substantive feedback.
Prepared by: ICT DEP’T Page 26
Axum Polytechnic College Establish and Maintain Client User Liaison
Training, Teaching and Learning Materials Development Lo-1
Here is an example:
ETSA Utilities, South Australia’s electricity distributor, provide online reports detailing how they are
performing against the performance indicators they have set for themselves in their customer charter.
Go to http://www.etsautilities.com.au/default.jsp?xcid=96
This feedback may come
by phone call
by email
by text message
by fax
verbally
by web form
or any other process you have set up for contact between you, your customer and your team.
Summary
In this unit, we have looked at the delivery of support to users. In order to assign appropriate support
personnel, you need to identify the IT skills required, find the right person and verify their
availability.
References
Internet
LO3: Test
This quiz will help you review the content you have learned in this topic.
Answer the questions, check the feedback at the end of each question and take note of the areas you
need to review.
1. What are technical skills?
Feedback
Knowledge of particular hardware (building shells) and software (experience in Novell, Linux, MS
Office or Dreamweaver) are considered technical skills. This could include other technical skills
such as the ability to write technical documentation, programming and analysis of databases.
2. What are soft skills?
Feedback
Soft skills are things such as communication skills (eg. being a clear communicator, being customer
focused, etc.), time management skills, problem solving skills, the ability to learn new procedures
quickly and to work in teams.
3. What would you do to recruit IT support staff?
Feedback
What would you do to recruit IT support staff? Possible answers:
use an online job site because IT staff usually look for employment through this type of
technology
advertise in papers only
try and find someone in your organisation, as they will already have a strong understanding of
your business
use whatever tools and resources you can to find the best person for the job
divide the task up and bring in specialist consultants for each specific task (as it is now so
diverse)
hire contractors.
4. According to your readings, why is feedback about the support you are providing so important?
Feedback
Feedback about support provision is important for the following reasons:
to learn of problems that are occurring in the delivery of the service. This can help you to be
proactive and head-off conflicts before they occur.
to improve your service to the client by finding out where the problems are occurring and
fixing them. These problems may be recurrent problems in the system you are supporting or
problems with the delivery of the support.
5. What are some of the important issues to consider when writing job advertisements?
Prepared by: ICT DEP’T Page 29
Axum Polytechnic College Establish and Maintain Client User Liaison
Training, Teaching and Learning Materials Development Lo-1
Feedback
Some of the important issues to consider when writing job advertisements include
language
length of ad
jargon
skill mix (is too much expected?)
sales pitch (did it motivate or excite you?)
title (did it grab your attention?)
positioning (was it the first on the list or 131st?).
6. Why is it important to understand the technical environment when hiring someone to work within such
an environment?
Feedback
Why is it important to understand the technical environment when hiring someone to work within
such an environment?
It is imperative that before you hire your ‘guru’, you must have a reasonable idea of what is expected
and be able to measure that both during their interview and by observing their work performance.
(Note – this is easier said than done).
Many projects have not been completed on time as a result of poor selection of staff and unrealistic
management expectations. If you don’t know about programming, for example, then how are you
going to be able to judge pay rates, timeframes or coding quality?
R