Resource Library

The tools described in this white paper are essential PM tools. Tools that will best be used, regardless of the project, are the WBS, communication model, and the precedence diagram. The other tools will be needed depending on the project.

Projects are a social endeavor. Traditional project management approaches have shied away from the social advantages a more agile project environment brings. By nature, we are storytelling, pattern seeking and social people. We need colocation to shine truly in a project environment.

The value of IT certifications has grown considerably over the last decade. Examine the evolution of certification trends, see the top-paying certifications and learn how decision-makers are struggling to hire certified employees.

Good global project managers develop their own competencies, and those of their team members. We can use technology to bridge distance, but also focus on the human aspects of culture, work habits, management style, English as a mandated language, communication, and uncertainty. Perform a self-assessment and assess your team members, then look for on-the-job and other improvement opportunities. A good way to learn more about how to overcome these challenges is to become involved in the international community.

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.

As mentioned earlier, one of the most useful pieces of guidance that ITIL provides relates to the categorization of suppliers. ITIL describes four categories of suppliers:

Keep your project on time and within budget by controlling the baselines, budget, and schedule. View our comprehensive guide to project management, from project scheduling to cost control, from the experts at Global Knowledge.

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:

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.

Effective requirements collection at the outset of the project is the key step that will ensure that the project manager can deliver what is actually expected. In this respect, the business analyst must become a key ally and advisor to the project manager. Most project managers are not trained business analysts, so taking advantage of the skill set that a business analyst can offer can greatly enhance the possibility of project success.