Home > Articles > Software Development & Management

📄 Contents

  1. Management Reference Guide
  2. Table of Contents
  3. Introduction
  4. Strategic Management
  5. Establishing Goals, Objectives, and Strategies
  6. Aligning IT Goals with Corporate Business Goals
  7. Utilizing Effective Planning Techniques
  8. Developing Worthwhile Mission Statements
  9. Developing Worthwhile Vision Statements
  10. Instituting Practical Corporate Values
  11. Budgeting Considerations in an IT Environment
  12. Introduction to Conducting an Effective SWOT Analysis
  13. IT Governance and Disaster Recovery, Part One
  14. IT Governance and Disaster Recovery, Part Two
  15. Customer Management
  16. Identifying Key External Customers
  17. Identifying Key Internal Customers
  18. Negotiating with Customers and Suppliers—Part 1: An Introduction
  19. Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
  20. Negotiating and Managing Realistic Customer Expectations
  21. Service Management
  22. Identifying Key Services for Business Users
  23. Service-Level Agreements That Really Work
  24. How IT Evolved into a Service Organization
  25. FAQs About Systems Management (SM)
  26. FAQs About Availability (AV)
  27. FAQs About Performance and Tuning (PT)
  28. FAQs About Service Desk (SD)
  29. FAQs About Change Management (CM)
  30. FAQs About Configuration Management (CF)
  31. FAQs About Capacity Planning (CP)
  32. FAQs About Network Management
  33. FAQs About Storage Management (SM)
  34. FAQs About Production Acceptance (PA)
  35. FAQs About Release Management (RM)
  36. FAQs About Disaster Recovery (DR)
  37. FAQs About Business Continuity (BC)
  38. FAQs About Security (SE)
  39. FAQs About Service Level Management (SL)
  40. FAQs About Financial Management (FN)
  41. FAQs About Problem Management (PM)
  42. FAQs About Facilities Management (FM)
  43. Process Management
  44. Developing Robust Processes
  45. Establishing Mutually Beneficial Process Metrics
  46. Change Management—Part 1
  47. Change Management—Part 2
  48. Change Management—Part 3
  49. Audit Reconnaissance: Releasing Resources Through the IT Audit
  50. Problem Management
  51. Problem Management–Part 2: Process Design
  52. Problem Management–Part 3: Process Implementation
  53. Business Continuity Emergency Communications Plan
  54. Capacity Planning – Part One: Why It is Seldom Done Well
  55. Capacity Planning – Part Two: Developing a Capacity Planning Process
  56. Capacity Planning — Part Three: Benefits and Helpful Tips
  57. Capacity Planning – Part Four: Hidden Upgrade Costs and
  58. Improving Business Process Management, Part 1
  59. Improving Business Process Management, Part 2
  60. 20 Major Elements of Facilities Management
  61. Major Physical Exposures Common to a Data Center
  62. Evaluating the Physical Environment
  63. Nightmare Incidents with Disaster Recovery Plans
  64. Developing a Robust Configuration Management Process
  65. Developing a Robust Configuration Management Process – Part Two
  66. Automating a Robust Infrastructure Process
  67. Improving High Availability — Part One: Definitions and Terms
  68. Improving High Availability — Part Two: Definitions and Terms
  69. Improving High Availability — Part Three: The Seven R's of High Availability
  70. Improving High Availability — Part Four: Assessing an Availability Process
  71. Methods for Brainstorming and Prioritizing Requirements
  72. Introduction to Disk Storage Management — Part One
  73. Storage Management—Part Two: Performance
  74. Storage Management—Part Three: Reliability
  75. Storage Management—Part Four: Recoverability
  76. Twelve Traits of World-Class Infrastructures — Part One
  77. Twelve Traits of World-Class Infrastructures — Part Two
  78. Meeting Today's Cooling Challenges of Data Centers
  79. Strategic Security, Part One: Assessment
  80. Strategic Security, Part Two: Development
  81. Strategic Security, Part Three: Implementation
  82. Strategic Security, Part Four: ITIL Implications
  83. Production Acceptance Part One – Definition and Benefits
  84. Production Acceptance Part Two – Initial Steps
  85. Production Acceptance Part Three – Middle Steps
  86. Production Acceptance Part Four – Ongoing Steps
  87. Case Study: Planning a Service Desk Part One – Objectives
  88. Case Study: Planning a Service Desk Part Two – SWOT
  89. Case Study: Implementing an ITIL Service Desk – Part One
  90. Case Study: Implementing a Service Desk Part Two – Tool Selection
  91. Ethics, Scandals and Legislation
  92. Outsourcing in Response to Legislation
  93. Supplier Management
  94. Identifying Key External Suppliers
  95. Identifying Key Internal Suppliers
  96. Integrating the Four Key Elements of Good Customer Service
  97. Enhancing the Customer/Supplier Matrix
  98. Voice Over IP, Part One — What VoIP Is, and Is Not
  99. Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
  100. Application Management
  101. Production Acceptance
  102. Distinguishing New Applications from New Versions of Existing Applications
  103. Assessing a Production Acceptance Process
  104. Effective Use of a Software Development Life Cycle
  105. The Role of Project Management in SDLC— Part 2
  106. Communication in Project Management – Part One: Barriers to Effective Communication
  107. Communication in Project Management – Part Two: Examples of Effective Communication
  108. Safeguarding Personal Information in the Workplace: A Case Study
  109. Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
  110. Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
  111. References
  112. Developing an ITIL Feasibility Analysis
  113. Organization and Personnel Management
  114. Optimizing IT Organizational Structures
  115. Factors That Influence Restructuring Decisions
  116. Alternative Locations for the Help Desk
  117. Alternative Locations for Database Administration
  118. Alternative Locations for Network Operations
  119. Alternative Locations for Web Design
  120. Alternative Locations for Risk Management
  121. Alternative Locations for Systems Management
  122. Practical Tips To Retaining Key Personnel
  123. Benefits and Drawbacks of Using IT Consultants and Contractors
  124. Deciding Between the Use of Contractors versus Consultants
  125. Managing Employee Skill Sets and Skill Levels
  126. Assessing Skill Levels of Current Onboard Staff
  127. Recruiting Infrastructure Staff from the Outside
  128. Selecting the Most Qualified Candidate
  129. 7 Tips for Managing the Use of Mobile Devices
  130. Useful Websites for IT Managers
  131. References
  132. Automating Robust Processes
  133. Evaluating Process Documentation — Part One: Quality and Value
  134. Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
  135. When Should You Integrate or Segregate Service Desks?
  136. Five Instructive Ideas for Interviewing
  137. Eight Surefire Tips to Use When Being Interviewed
  138. 12 Helpful Hints To Make Meetings More Productive
  139. Eight Uncommon Tips To Improve Your Writing
  140. Ten Helpful Tips To Improve Fire Drills
  141. Sorting Out Today’s Various Training Options
  142. Business Ethics and Corporate Scandals – Part 1
  143. Business Ethics and Corporate Scandals – Part 2
  144. 12 Tips for More Effective Emails
  145. Management Communication: Back to the Basics, Part One
  146. Management Communication: Back to the Basics, Part Two
  147. Management Communication: Back to the Basics, Part Three
  148. Asset Management
  149. Managing Hardware Inventories
  150. Introduction to Hardware Inventories
  151. Processes To Manage Hardware Inventories
  152. Use of a Hardware Inventory Database
  153. References
  154. Managing Software Inventories
  155. Business Continuity Management
  156. Ten Lessons Learned from Real-Life Disasters
  157. Ten Lessons Learned From Real-Life Disasters, Part 2
  158. Differences Between Disaster Recovery and Business Continuity , Part 1
  159. Differences Between Disaster Recovery and Business Continuity , Part 2
  160. 15 Common Terms and Definitions of Business Continuity
  161. The Federal Government’s Role in Disaster Recovery
  162. The 12 Common Mistakes That Cause BIAs To Fail—Part 1
  163. The 12 Common Mistakes That Cause BIAs To Fail—Part 2
  164. The 12 Common Mistakes That Cause BIAs To Fail—Part 3
  165. The 12 Common Mistakes That Cause BIAs To Fail—Part 4
  166. Conducting an Effective Table Top Exercise (TTE) — Part 1
  167. Conducting an Effective Table Top Exercise (TTE) — Part 2
  168. Conducting an Effective Table Top Exercise (TTE) — Part 3
  169. Conducting an Effective Table Top Exercise (TTE) — Part 4
  170. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
  171. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
  172. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
  173. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
  174. The Information Technology Infrastructure Library (ITIL)
  175. The Origins of ITIL
  176. The Foundation of ITIL: Service Management
  177. Five Reasons for Revising ITIL
  178. The Relationship of Service Delivery and Service Support to All of ITIL
  179. Ten Common Myths About Implementing ITIL, Part One
  180. Ten Common Myths About Implementing ITIL, Part Two
  181. Characteristics of ITIL Version 3
  182. Ten Benefits of itSMF and its IIL Pocket Guide
  183. Translating the Goals of the ITIL Service Delivery Processes
  184. Translating the Goals of the ITIL Service Support Processes
  185. Elements of ITIL Least Understood, Part One: Service Delivery Processes
  186. Case Study: Recovery Reactions to a Renegade Rodent
  187. Elements of ITIL Least Understood, Part Two: Service Support
  188. Case Studies
  189. Case Study — Preparing for Hurricane Charley
  190. Case Study — The Linux Decision
  191. Case Study — Production Acceptance at an Aerospace Firm
  192. Case Study — Production Acceptance at a Defense Contractor
  193. Case Study — Evaluating Mainframe Processes
  194. Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
  195. Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
  196. Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
  197. Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
  198. Disaster Recovery Test Case Study Part One: Planning
  199. Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
  200. Disaster Recovery Test Case Study Part Three: Execution
  201. Disaster Recovery Test Case Study Part Four: Follow-Up
  202. Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
  203. Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
  204. Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
  205. (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two

A number of techniques exist to help transform marginal or mediocre strategy meetings into successful, effective planning sessions. This section provides some proven methods on the use of brainstorming rules; on helpful hints about meeting management; on determining the best set of meeting logistics; on how to invite all, and only, appropriate individuals to meetings; and on the analysis of strengths, weaknesses, opportunities, and threats of an organization. These techniques can help to turn an average strategy meeting into a very worthwhile planning session. Gatherings of this type can be expensive, time-consuming, and wasteful. With a little bit of planning and foresight, these sessions can be transformed into the efficient use of valuable staff time.

Brainstorming Rules

Almost any successful brainstorming session has a common set of rules to govern behavior, logistics, and results. This certainly applies to a strategic planning session. The following helpful ground rules are not necessarily unique or groundbreaking, but ensuring total buy-in to all of them prior to the start of any discussions, and adhering to strict enforcement throughout the gathering, can provide a smoother-flowing meeting with more successful results:

  • Agree on the clear objective(s) of the brainstorming.

  • Stay focused on the objectives(s).

  • Treat everyone as equals.

  • Listen respectfully to each person's input.

  • Participate honestly and candidly.

  • Maintain confidentiality when appropriate.

  • Keep an open mind; suspend personal agendas.

  • Ask anything—there are no dumb questions.

  • Question anything you don't understand.

  • Only one voice at a time; no side conversations.

  • Ensure that everything relevant is written down.

  • If prioritizing, agree on specific techniques.

  • If attempting consensus, agree on voting method.

  • Start and end on time—session, breaks, lunch.

  • Critique the brainstorming session for improvements.

Meeting Management

An effective meeting of any kind doesn't happen by accident. It seems only right that a meeting whose objective is to discuss strategic planning issues should be thoroughly planned for in the beginning. Following are twelve tips to more effective meetings:

  1. State the objective of the meeting. Know what you hope to accomplish and the type of meeting you plan to conduct—status, brainstorming, presentation, or evaluation.

  2. Identify appropriate participants. Based on the objective and the type of meeting, determine all (and only) appropriate individuals. This topic is covered in more detail in the next section.

  3. Schedule well in advance. Depending on who the participants are, the number who need to attend, and the availability of rooms, schedule the meeting well enough in advance to accommodate everyone's needs.

  4. Provide an agenda. Develop an agenda. In some instances a timetable of key meeting events may be appropriate. Include the meeting objective. Distribute the agenda to all attendees. If an online calendaring facility such as Outlook is available, take advantage of its confirmation feature.

  5. Assign a scribe. Arrange with an attendee to take notes. In the case of a brainstorming session, you may want to assign more than one if multiple flipcharts will be used.

  6. Assign a timekeeper. Fast-paced, free-flowing meetings often run out of time before all key issues have been addressed. An assigned timekeeper can help prevent this problem by keeping the meeting on track.

  7. Clarify issues and move on. Not all issues can be resolved in a single meeting. Highly intelligent individuals usually have strong opinions and want to be heard. A balance frequently needs to be struck between giving everyone a chance to contribute and knowing when to move on to more important topics.

  8. Agree on action items. Identify, assign, and schedule completion dates for all action items.

  9. Summarize results. Wrap up the meeting with a review of the results, especially confirming the assignment and completion dates of action items.

  10. Critique the meeting. Set aside a few minutes at the end of the meeting to critique its value. Take note of what could be improved at future meetings.

  11. Send out meeting minutes. The scribe or the person conducting the meeting should distribute meeting minutes as soon as possible to everyone who was invited, and anyone else deemed appropriate. Note who was invited and who actually attended.

  12. Follow up on action items. Depending on the number of action items and their completion dates, follow up on them at an appropriate frequency.

Meeting Logistics

The logistics of a meeting can often spell the difference between a rousing success and a dismal failure. One of the first steps to take is to thoroughly understand the purpose and type of meeting to be conducted, the number and makeup of the attendees, and the estimated duration of the session. From those details, you can determine the best day of the week and hour of the day on which to schedule the meeting; the best location in terms of room size; the best method of facilitation to use; and whether to hold the meeting in-house or offsite. Another consideration is the importance of meeting setup, visual aids, laptop hookups, lighting, acoustics, and so on. Finally, include provisions for meals, drinks, and refreshments if appropriate.

TIP

A possible alternative way to go offsite at marginal cost may be to use a company facility at another campus or in another area in close proximity.

Appropriate Meeting Participants

The type and purpose of a meeting normally dictate who the appropriate meeting attendees should be. In the case of a strategic planning meeting, this group may include representatives from senior or middle management, technical leads, and subject matter experts. In some instances it may also include members from applicable business units or from appropriate non–IT support groups such as human resources, finance, facilities, contracts, or legal. Some strategy sessions may also include input from suppliers or outside consultants. In these cases, an additional concern is to ensure that agreements of confidentiality and disclosure are fully understood and adhered to.

Analyzing Strengths, Weaknesses, Opportunities, and Threats (SWOT)

SWOT analysis is a process to identify the relative strengths, weaknesses, opportunities, and threats of a person, a small team, a large organization, or an initiative, normally in a business environment. Many companies find the process useful as a preparation for strategic planning. The results of a SWOT analysis can be used to help an organization build on its strengths, minimize its weaknesses, exploit opportunities, and mitigate threats.

A highly efficient SWOT session usually consists of four subprocesses:

  • "Round robin" method to identify items. Round robin is a fast-paced method to quickly identify items during a brainstorming session. The proper use of this process results in virtually no lost time in gathering meaningful information. The two keys to its success are brevity and handoffs. Participants sitting around a table must choose to briefly offer a response or to hand off to the next person. One or more assigned scribes record all responses. Individuals typically have only 10–15 seconds to offer a suggestion, so short, quick responses are a necessity. Handoffs are very common, especially during the first few rounds. Rounds continue until three full passes are made with no new responses.

  • Author/group consensus scheme to merge items. Some responses may turn out to be similar to ones previously mentioned. The author/group consensus scheme looks at those responses that may be merged and negotiates with the author of the response and the group to gain consensus on it.

  • Nominal group technique to prioritize items. The nominal group technique effectively prioritizes large lists of items in a short time by having each individual apply a point value to just a few of their top choices. What may normally take hours to accomplish with other methods can be done in 10–15 minutes using this method.

  • "Common threads" approach to categorize items. Once the items have been identified, merged, and prioritized, they can be grouped into major categories according to common threads that stand out from the prioritized lists. This process also should only take a few minutes to accomplish.

References

IT Systems Management: Designing, Implementing, and Managing World-Class Infrastructures (Prentice Hall PTR, 2002, ISBN 013087678X), by Rich Schiesser.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.