- Management Reference Guide
- Table of Contents
- Introduction
- Strategic Management
- Establishing Goals, Objectives, and Strategies
- Aligning IT Goals with Corporate Business Goals
- Utilizing Effective Planning Techniques
- Developing Worthwhile Mission Statements
- Developing Worthwhile Vision Statements
- Instituting Practical Corporate Values
- Budgeting Considerations in an IT Environment
- Introduction to Conducting an Effective SWOT Analysis
- IT Governance and Disaster Recovery, Part One
- IT Governance and Disaster Recovery, Part Two
- Customer Management
- Identifying Key External Customers
- Identifying Key Internal Customers
- Negotiating with Customers and Suppliers—Part 1: An Introduction
- Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
- Negotiating and Managing Realistic Customer Expectations
- Service Management
- Identifying Key Services for Business Users
- Service-Level Agreements That Really Work
- How IT Evolved into a Service Organization
- FAQs About Systems Management (SM)
- FAQs About Availability (AV)
- FAQs About Performance and Tuning (PT)
- FAQs About Service Desk (SD)
- FAQs About Change Management (CM)
- FAQs About Configuration Management (CF)
- FAQs About Capacity Planning (CP)
- FAQs About Network Management
- FAQs About Storage Management (SM)
- FAQs About Production Acceptance (PA)
- FAQs About Release Management (RM)
- FAQs About Disaster Recovery (DR)
- FAQs About Business Continuity (BC)
- FAQs About Security (SE)
- FAQs About Service Level Management (SL)
- FAQs About Financial Management (FN)
- FAQs About Problem Management (PM)
- FAQs About Facilities Management (FM)
- Process Management
- Developing Robust Processes
- Establishing Mutually Beneficial Process Metrics
- Change Management—Part 1
- Change Management—Part 2
- Change Management—Part 3
- Audit Reconnaissance: Releasing Resources Through the IT Audit
- Problem Management
- Problem Management–Part 2: Process Design
- Problem Management–Part 3: Process Implementation
- Business Continuity Emergency Communications Plan
- Capacity Planning – Part One: Why It is Seldom Done Well
- Capacity Planning – Part Two: Developing a Capacity Planning Process
- Capacity Planning — Part Three: Benefits and Helpful Tips
- Capacity Planning – Part Four: Hidden Upgrade Costs and
- Improving Business Process Management, Part 1
- Improving Business Process Management, Part 2
- 20 Major Elements of Facilities Management
- Major Physical Exposures Common to a Data Center
- Evaluating the Physical Environment
- Nightmare Incidents with Disaster Recovery Plans
- Developing a Robust Configuration Management Process
- Developing a Robust Configuration Management Process – Part Two
- Automating a Robust Infrastructure Process
- Improving High Availability — Part One: Definitions and Terms
- Improving High Availability — Part Two: Definitions and Terms
- Improving High Availability — Part Three: The Seven R's of High Availability
- Improving High Availability — Part Four: Assessing an Availability Process
- Methods for Brainstorming and Prioritizing Requirements
- Introduction to Disk Storage Management — Part One
- Storage Management—Part Two: Performance
- Storage Management—Part Three: Reliability
- Storage Management—Part Four: Recoverability
- Twelve Traits of World-Class Infrastructures — Part One
- Twelve Traits of World-Class Infrastructures — Part Two
- Meeting Today's Cooling Challenges of Data Centers
- Strategic Security, Part One: Assessment
- Strategic Security, Part Two: Development
- Strategic Security, Part Three: Implementation
- Strategic Security, Part Four: ITIL Implications
- Production Acceptance Part One – Definition and Benefits
- Production Acceptance Part Two – Initial Steps
- Production Acceptance Part Three – Middle Steps
- Production Acceptance Part Four – Ongoing Steps
- Case Study: Planning a Service Desk Part One – Objectives
- Case Study: Planning a Service Desk Part Two – SWOT
- Case Study: Implementing an ITIL Service Desk – Part One
- Case Study: Implementing a Service Desk Part Two – Tool Selection
- Ethics, Scandals and Legislation
- Outsourcing in Response to Legislation
- Supplier Management
- Identifying Key External Suppliers
- Identifying Key Internal Suppliers
- Integrating the Four Key Elements of Good Customer Service
- Enhancing the Customer/Supplier Matrix
- Voice Over IP, Part One — What VoIP Is, and Is Not
- Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
- Application Management
- Production Acceptance
- Distinguishing New Applications from New Versions of Existing Applications
- Assessing a Production Acceptance Process
- Effective Use of a Software Development Life Cycle
- The Role of Project Management in SDLC— Part 2
- Communication in Project Management – Part One: Barriers to Effective Communication
- Communication in Project Management – Part Two: Examples of Effective Communication
- Safeguarding Personal Information in the Workplace: A Case Study
- Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
- Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
- References
- Developing an ITIL Feasibility Analysis
- Organization and Personnel Management
- Optimizing IT Organizational Structures
- Factors That Influence Restructuring Decisions
- Alternative Locations for the Help Desk
- Alternative Locations for Database Administration
- Alternative Locations for Network Operations
- Alternative Locations for Web Design
- Alternative Locations for Risk Management
- Alternative Locations for Systems Management
- Practical Tips To Retaining Key Personnel
- Benefits and Drawbacks of Using IT Consultants and Contractors
- Deciding Between the Use of Contractors versus Consultants
- Managing Employee Skill Sets and Skill Levels
- Assessing Skill Levels of Current Onboard Staff
- Recruiting Infrastructure Staff from the Outside
- Selecting the Most Qualified Candidate
- 7 Tips for Managing the Use of Mobile Devices
- Useful Websites for IT Managers
- References
- Automating Robust Processes
- Evaluating Process Documentation — Part One: Quality and Value
- Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
- When Should You Integrate or Segregate Service Desks?
- Five Instructive Ideas for Interviewing
- Eight Surefire Tips to Use When Being Interviewed
- 12 Helpful Hints To Make Meetings More Productive
- Eight Uncommon Tips To Improve Your Writing
- Ten Helpful Tips To Improve Fire Drills
- Sorting Out Today’s Various Training Options
- Business Ethics and Corporate Scandals – Part 1
- Business Ethics and Corporate Scandals – Part 2
- 12 Tips for More Effective Emails
- Management Communication: Back to the Basics, Part One
- Management Communication: Back to the Basics, Part Two
- Management Communication: Back to the Basics, Part Three
- Asset Management
- Managing Hardware Inventories
- Introduction to Hardware Inventories
- Processes To Manage Hardware Inventories
- Use of a Hardware Inventory Database
- References
- Managing Software Inventories
- Business Continuity Management
- Ten Lessons Learned from Real-Life Disasters
- Ten Lessons Learned From Real-Life Disasters, Part 2
- Differences Between Disaster Recovery and Business Continuity , Part 1
- Differences Between Disaster Recovery and Business Continuity , Part 2
- 15 Common Terms and Definitions of Business Continuity
- The Federal Government’s Role in Disaster Recovery
- The 12 Common Mistakes That Cause BIAs To Fail—Part 1
- The 12 Common Mistakes That Cause BIAs To Fail—Part 2
- The 12 Common Mistakes That Cause BIAs To Fail—Part 3
- The 12 Common Mistakes That Cause BIAs To Fail—Part 4
- Conducting an Effective Table Top Exercise (TTE) — Part 1
- Conducting an Effective Table Top Exercise (TTE) — Part 2
- Conducting an Effective Table Top Exercise (TTE) — Part 3
- Conducting an Effective Table Top Exercise (TTE) — Part 4
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
- The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
- The Information Technology Infrastructure Library (ITIL)
- The Origins of ITIL
- The Foundation of ITIL: Service Management
- Five Reasons for Revising ITIL
- The Relationship of Service Delivery and Service Support to All of ITIL
- Ten Common Myths About Implementing ITIL, Part One
- Ten Common Myths About Implementing ITIL, Part Two
- Characteristics of ITIL Version 3
- Ten Benefits of itSMF and its IIL Pocket Guide
- Translating the Goals of the ITIL Service Delivery Processes
- Translating the Goals of the ITIL Service Support Processes
- Elements of ITIL Least Understood, Part One: Service Delivery Processes
- Case Study: Recovery Reactions to a Renegade Rodent
- Elements of ITIL Least Understood, Part Two: Service Support
- Case Studies
- Case Study — Preparing for Hurricane Charley
- Case Study — The Linux Decision
- Case Study — Production Acceptance at an Aerospace Firm
- Case Study — Production Acceptance at a Defense Contractor
- Case Study — Evaluating Mainframe Processes
- Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
- Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
- Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
- Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
- Disaster Recovery Test Case Study Part One: Planning
- Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
- Disaster Recovery Test Case Study Part Three: Execution
- Disaster Recovery Test Case Study Part Four: Follow-Up
- Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
- Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
- Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
- (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two
Most newly proposed IT projects begin with a requirements phase. Staffing for systems management also has a requirements phase in the sense that necessary skill sets and skill levels need to be identified and prioritized early on. A skill set is defined as technical familiarity with a particular software product, architecture, or platform. For example, one enterprise may use primarily IBM mainframes with IBM's information management system (IMS) while another may use mostly Sun Solaris server platforms with Oracle databases. A third enterprise may use only web-enabled applications that require extensive knowledge of Internet programming and protocols. The skill sets needed to implement the various systems management functions in these three environments would be significantly different from each other.
Within a skill set there is another attribute known as the skill level. The skill level is simply the length of experience and depth of technical expertise an individual has acquired and can apply to a given technology. The process of determining and prioritizing the required skill sets and levels has several benefits. First, quantifying the skill sets that will be needed to implement selected functions forces you to more accurately reflect the diversity of technical experience your environment will require. Second, estimating necessary skill levels within each required skill set will reflect the amount of technical depth and expertise that will be needed. Finally, the quantifying and qualifying required skill sets and levels are valuable aids in building the business cases for a given project or proposal.
Estimating accurate requirements for skill sets and skill levels provide a more comprehensive picture of support costs. Strange as this may sound, this can actually strengthen the credibility of a business case by providing a more realistic total cost of ownership (TCO). I have witnessed many a project that went far over budget during implementation due to support costs causing the TCO to far exceed original estimates.
Developing a skill set matrix that is customized for your particular environment can help simplify this process. Table 1 shows an example of a skill set matrix for a relatively typical client-server environment. The first column describes the major areas of focus for which systems management functions would apply and for which staffing would need to be considered. These major groupings would obviously differ from company to company depending on their own particular area of focus. Similarly, the second column that describes various platforms will likely differ from enterprise to enterprise.
Next are the five groupings of skill levels, starting with the least experienced intern level and progressing to the senior and lead levels. The appropriate box can be check-marked for each skill level required. The value of a table such as this is that it helps to visually qualify the skills that will be needed to implement selected systems management disciplines. The table can also be used to quantify how many individuals will be needed for each skill set and level. Occasionally a skill set and skill level requirement may amount to less than one full-time person. In this case a decimal portion of a full-time equivalent (FTE) is commonly used to represent the staffing need.
A similar type of matrix can be used for mainframe environments as well as those for midrange computers. In all cases the area of focus and the platforms will be customized to fit the exact characteristics of the shop in question. The particular skill levels specified in the table should also be tailored to meet current job descriptions which can over time. One of my clients a few years ago completely re-structured their technical job descriptions, many of which had become redundant or obsolete. They streamlined them from 67 unique descriptions down to 39.
Alternative Sources of Skill Sets and Levels
Several alternative sources for infrastructure skill sets and skill levels are available inside most reasonably sized enterprises. One source involves cross-training existing infrastructure personnel in related skill sets. For example, if a company decides to change from one type of UNIX platform to another, a systems administrator who is familiar with only one variation of Unix may be cross-trained in the alternative version. Similarly, an NT systems administrator may be cross-trained on UNIX.
A more challenging transition, though nonetheless viable, may be between systems administration, database administration, and network administration. In some instances, suitable candidates may be found outside of the infrastructure group. Application departments may be able to supply DBA prospects or performance specialists, and planning groups may offer up metrics analysts. In certain cases, even business units outside of IT may have personnel qualified for selected positions within an IT infrastructure.
The two key points in any discussion about skill sets and skill levels is to know what you currently have on board inn terms of technical expertise, and to know what you need. An skill set inventory and a skill matrix can help any these questions.
Table 1. Client-Server Environment Skill Set Matrix
Area of Focus |
Platform |
Manufacturer |
Skill Level |
||||
Intern |
Junior |
Associate |
Senior |
Lead |
|||
Operating Systems |
UNIX |
IBM/AIS |
|
|
|
|
|
SUN/SOLARIS |
|
|
|
|
|
||
HP/HPUNIX |
|
|
|
|
|
||
REDDOG/LINUX |
|
|
|
|
|
||
Support products |
|
|
|
|
|
||
Other |
|
|
|
|
|
||
NT |
Various |
|
|
|
|
|
|
Support products |
|
|
|
|
|
||
Database Management Systems |
UNIX |
Oracle |
|
|
|
|
|
Sybase |
|
|
|
|
|
||
Informix |
|
|
|
|
|
||
Support products |
|
|
|
|
|
||
Other |
|
|
|
|
|
||
NT |
MS SQLServer |
|
|
|
|
|
|
Support products |
|
|
|
|
|
||
Other |
|
|
|
|
|
||
Network Systems |
LAN |
Various |
|
|
|
|
|
WAN |
|
|
|
|
|
||
Support products |
|
|
|
|
|
||
Other |
|
|
|
|
|
References
Kern, Harris, and Galup, Stuart D., and Nemiro, Guy, IT Organization: Building a Worldclass Infrastructure, Prentice Hall, 2001
Schiesser, Rich, IT Systems Management, Prentice Hall, 2002