79 Results Found
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:
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.
No matter which IT field you're working in, there are several skills that are useful for every IT professional to know. Here, seven experienced IT professionals working in the networking, programming, project management, and security fields, share what they believe a...
Project procurement activities are often managed by specialists. By this I mean that the procurement department takes over responsibility for purchasing and contract management from the project manager. As a result of this separation of responsibilities, the steps and stages of procurement are often poorly understood by PMs. In this and the next few blog submissions, I will attempt to shed light on procurement activities and relate these activities to the PMI PMBOK.
No matter what book or manual you use to study for the CCNA examination, you will see various protocols and processes referencing an RFC. And, although frequently referenced, the RFCs are seldom actually included in the documentation. So, the logical question becomes...
The triple constraints model has been one of the main staples for teaching project management for as long as I can remember. The model is generally represented by a triangle with Scope on the horizontal leg, Time on the left leg, Cost or Resources on the right leg an...