Doing more with less. Enhanced business agility. Reduced costs. The demands on IT have never been greater, particularly in light of lower revenue and uncertain demand for the goods and services offered by many companies. There are many ways that IT can help organizations adjust to this new economic environment. Learn about five key technology trends that can immediately impact your organization's bottom line, and how to build a strategy to implement these technologies within your current budget. more
My company is currently looking at ITIL as the end all-be all of process development. Let me explain further that I work for a subsidiary of the parent company, not headquarters.
I'm the poor schmuck who is responsible for our problem management system. I brought this thing in nearly a decade ago and have done all the development and support.
I know the very basics of ITIL. I've been spending more time on learning it since I found out just how brainwashed headquarters management is on it. What I've learned confirms that we're in pretty good basic compliance already. We just don't use the ITIL terminology.
On to the problem. Management has decided that our current product does not meet our needs if we're going to go ITIL. They've put together a team to define the business requirements. Guess who isn't on the team?
So now I'm torn. Do I strong-arm my way onto the team so I know what they're looking for or do I sit back and wait for them to provide a list of functions that may or may not be feasible in any product? From what I've found out about the team they've built there's no one on there that actually understands what needs to happen 'under the hood' to make ITIL work.
Any suggestions?
- Outside the tent
Dear Outsider ...
I think you're asking the wrong question, or perhaps you're asking the right question, but prematurely. A better place to begin might be to define more clearly what your personal goal is -- what you'd like to see come out of this.
Let's start by acknowledging that if the folks responsible for the ITIL initiative had the good sense that God gave rice they'd have included you in the effort. After all, you're the person who made the current system happen (I presume it's handling the basics of incident management competently). Unless your departure is part of the ITIL plan it's hard to imagine anything about the effort that's improved through your exclusion.
While that analysis explains whatever bemusement, indignation or resentment you might feel about the situation, it doesn't define your goal. Here are some possibilities:
Addressing Linux Threats Leveraging Fewer Resources
The increase in Linux popularity has increased the frequency and sophistication of malware attacks. Read this 2 page white paper now to learn how you can protect your Linux environment with real-time protection that is certified by all major Linux vendors.
Ensuring acceptable application delivery will become even more difficult over the next few years. As a result, IT organizations need to ensure that the approach that they take to resolving the current application delivery challenges can scale to support the emerging challenges. This handbook elaborates on the key tasks associated with planning, optimization, management and control and provides decision criteria to help IT organizations choose appropriate solutions.
A common misconception is that mid-range storage requirements are dramatically different than that of a larger enterprise. Mid-range storage users may require less capacity, but they have similar functionality and management requirements. This ESG paper examines mid-range storage needs and reviews a new solution that adjusts size while retaining value, performance and functionality.
9 Recommendations
