Resource Library

Knowledge Management examines how we acquire, organize, manage, share, and utilize knowledge and information. The Internet gives us an overwhelming amount of information on a daily basis — and the volume of information available is growing rapidly! One of the biggest challenges for individuals and organizations involved in project management is to make the best use of this knowledge and information so they can operate more efficiently, improve decision making, and sustain a competitive advantage.

Lessons learned is a theory, or conclusion, based on evidence at a given time and describes what went wrong (as well as what went right) throughout the lifecycle of a project. Although it’s completed during the project closeout process, it should occur during the entire project lifecycle to ensure all information is captured and documented. Consequences of not having a project review of lessons learned are the increased likelihood of repeating actions that might have caused:

Global Knowledge practice director for cloud solutions, Hank Marquis, explains the people, process, and technology aspects of cloud computing.

Everyone has been involved in a learning program or project that has not delivered its intended impact. Across organizations, remarkably similar but preventable missteps are made in needs identification, learning strategies, program development and implementation.  Instructor Tom Gram, Senior Director of Professional Services at Global Knowledge, will present six classic mistakes learning professionals make that reduce chances for success along with evidence-based practices to help prevent them. 

During a recent ITIL foundation class, a student asked an interesting question. She wanted to know: “What is the difference between a project and a service?” To be honest, I haven’t spent much time thinking about this distinction. However, I think that those of us who practice ITIL consulting and training should have good answers to questions such as this. Here’s how I answered this question.

The term "life cycle" implies two things: that a process is perpetual and that the sequence of events is obligatory or uni-directional. There is no beginning or end to a life cycle and the sequence of events cannot change. A seed cannot go directly to being a mature plant nor revert back to the blossom stage.

In my last post I discussed aspects of problem management in the context of a real-life situation regarding the first vehicle I owned. In that scenario, and throughout this series of posts, I’ve demonstrated a real-life situation from a standpoint of the incident and problem management processes that ITIL describes.

In this informative, hour-long webinar, Global Knowledge instructor Debbie Dahlin will explore an abundance of important cloud computing security issues. She will help you gain insight into the key cloud security issues of maintaining the confidentiality, integrity, and availability of corporate information and applications.

In the fourth of his five-part series, Eric Strause explores the hardware and application benefits inherent in a cloud-based architecture.

I attended a meeting this week with a customer of mine and a potential new vendor. The new vendor was there to pitch his configuration and setup service offerings for a specific ITSM toolset. My customer has already had one bad experience with an ITSM tool configuration vendor who promised one thing and delivered much less. He ended up with a tool that’s minimally used and not configured to match his business needs. He’s looking for a vendor that can understand his business needs and priorities and quickly help him get his tool configured and working in a short time frame. Then the topic of standard changes came up. My customer asked for examples of standard changes. The vendor responded, “Server reboots are an example of standard changes.”