Resource Library

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...

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...

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 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...

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.

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.

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.

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. 

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:

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.

There is a reason why the Agile methods are becoming mainstream. They can work! Although every Agile practice is not necessarily appropriate for every organization, each practice has delivered real value to many organizations, and some Agile practices can be used by anyone! This four part series explores twelve ways in which the Agile methods are valuable. I’ll bet that you will find more than a few that could be valuable for you!

We already covered the first three of the twelve advantages of Agile software development. These three advantages focus on team development and refining the process. Advantage #4: Motivated Development Team The positive relationship with a reasonable and satisfied customer is only one of the reasons why many developers prefer to work on Agile projects. The other main contributor is that they tend to value working in self directed teams (which the Agile methods require for success).

ITIL describes a service portfolio as a collection of the overall set of services managed by a service provider. A service portfolio describes a service provider’s boundaries and promises across all of the customers and market spaces it serves. I like to think of a service portfolio as describing the past, present, and future collection of services offered by a service provider. The figure below shows a high-level view of a service portfolio.

In a recent post, I gave an overall description of a service portfolio and the key components of a portfolio. Here, I will describe how a cloud services provider might implement an ITIL service portfolio. A cloud services provider will regularly have a set of services under development, a set of service in live operation, and a set of services that are retired.

Enterprises, whether they are commercial, non-profit, or government entities, are operational organizations that operate through the execution of hundreds of processes. The quality of these processes affects every aspect of the enterprise and these processes are rarely static. Business Process Analysis (BPA) is the discipline of examining processes so that they may be changed to align with enterprise objectives.

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:

This paper proposes a unifying model for project plans. A distinction will be made between the outputs of project planning and the project plan itself. The significance of this distinction is to allow projects of all types to be described at a high level, in a common language, regardless of the type of analysis used to develop the plan.

For a project manager (PM) who has served as a military officer on a battalion or higher staff, the parallels between the military decision-making process (MDMP), the orders production process, and project management doctrine prescribed by the Project Management Institute (PMI) are difficult to ignore. Both the MDMP and the processes outlined in A Guide to the Project Management Body of Knowledge—Fifth Edition (PMBOK® Guide) are iterative in nature, allow for the introduction of changes to the original plan, assign tasks and responsibilities, and involve the concept of managing the scope of the operation or project.

Now that we have looked at the similarities and differences between the first two steps of the military decision-making process (MDMP) and the project management processes from the planning process group that align with them, it’s time to take a look at the third ste...

Today, every project comes with limited resources and an impossible timeline. You have to prioritize, but how do you determine what's most important? The answer is to do more than just prioritize. You have to fully understand your company's strategic direction and make every action align with that strategy. In this hour-long webinar, project management expert Yvan Bastien will show you how to reach that full understanding and make the kinds of informed decisions that lead to success.

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.

Communication is vital within projects and contributes significantly to project success. PMs and BAs have important—and different—roles. Let's take a look.

Whether you're a Project Manager or a Business Analyst, you can certainly relate to a situation where you've felt like your cohort on a project was from a completely different planet! This panel discussion webinar between our PM expert, Ori Schibi, and our BA expert, Cheryl Lee, will explore some of the misconceptions that each role has and learn how to play nicely with each other in the project world.

Global Knowledge Course Director Samuel Brown introduces the Work Breakdown Structure and why it matters to project management.

Samuel Brown, project management instructor and consultant, has taught Global Knowledge courses for more than fifteen years. In this video clip, Samuel discusses Global Knowledge's unique and effective approach to helping students prepare for PMP certification.

Kirsten Lora, Global Knowledge Senior Product Director, discusses the benefits of our IT Project Management course.

The project manager (PM) and business analyst (BA) have to be key allies in the management of any project. That can be difficult when project work is duplicated because of the overlapping tasks defined by the International Institute of Business Analysis (IIBA®) and the Project Management Institute (PMI®). Still, as long as roles are clearly defined and understood, the two can cooperate and collaborate, instead of competing. In this hour-long webinar, Global Knowledge instructor and PMP-certified project management expert Daniel Stober will explain how to delineate the roles.

This power session is an introduction to Managing Stakeholder relations. It offers new ways of managing and dealing with projects, which focus more on communications, understanding stakeholders' needs and managing their expectations, as well as learning about organizational politics and culture, and performing value-add activities. It provides a practical approach to managing issues that matter most for project success - communication, stakeholder expectations, risk, change and quality; so that the scope, schedule and cost end up on target, achieving the desired outcomes for the organization.

In this hour-long webinar, Global Knowledge instructor and PMP-certified project management expert Daniel Stober will look beyond the triple constraint model and focus on the true essence of project success: stakeholder satisfaction. Many project managers (PMs) fall into the familiar habit of managing based on the constraints of time, cost and scope. While all of these are important, managing them effectively doesn't guarantee project success if the PM fails to conduct proper stakeholder management. To manage stakeholders effectively, the PM has to set expectations. Once expectations are set, the PM must influence the perception of project performance with the stakeholder. Tune in as Dan explores methods you can use to accomplish that goal.

In this series, we are looking at six things that can trip up project managers. We’ve covered the hazards of overcommitting, how to provide feedback, the importance of taking responsibility, staying focused, and what leading from the front can actually look like. Finally, we’ll take a look at handling team input.

In many organizations, the Program/Project Management Office (PMO) is viewed as purely a cost center, so it becomes marginalized by additional layers of bureaucracy, oversight and cost. But the essence of the PMO and portfolio management in general is to add value to the organization. So how do organizations reconcile the cost of the PMO versus the value it adds? The short answer is to flip the conversation on its head and talk about the PMO as a revenue driver rather than a cost center. In this hour-long webinar, Global Knowledge PMP-certified senior product manager Daniel Stober will explain how, by focusing on efficiencies gained and reduced waste, you can shift the conversation from the PMO being a necessary evil to the PMO being critical for organizational success.

Young adults unable to find work, employers unable to fill jobs, a recent GAO study that reported substantial declines in telecommunication expertise — there has been a lot of news about the pervasiveness of skills gaps, their causes, the actual impacts and what to do about them. It’s rather confusing, because the term “skills gaps” has been hijacked to politicize an extremely wide range of issues.

Complexity has always been a part of projects. But today, globalization, new technologies and changing markets have combined to add to the complexity. Today's projects have more stakeholders, more ambiguity and more politics than ever, and project managers need new tools and approaches to succeed. Join Alexander Stanisic and Michelle Moore of Global Knowledge for an information-packed hour on how to manage the complexity of the 21st-century project.

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.

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.

In this blog series, we'll get you up to speed on using the key tools listed in the PMBOK® Guide. First up, Work Breakdown Structure (WBS).

Most project team members report to a functional manager who controls their assignments, performance appraisals, raises, bonuses, etc. Until recently, project managers (PMs) had little input into any of these processes. In this paper, learn how a PM working in a functional or matrix organizational structure can get team members to perform.

In this blog series, we'll get you up to speed on using the key tools listed in the PMBOK® Guide, including Decision Tree Diagrams.

Change managers and project managers come at the same goal of maximizing ROI for their organizations, but from different perspectives and approaches and with different skill sets. While project managers are responsible for achieving specific objectives on time and on budget, the change manager's role is broader. Change managers apply a structured approach to helping individuals, teams and organizations negotiate relentless change. A project manager turns ideas into reality. Increasingly, project managers are required to take on the role of change manager as well. Business today can't afford to carry out tasks without considering the larger picture. Today, integration is unavoidable - and expected. In this hour-long interactive session, we'll discuss the similarities and differences between project management and change management. We'll also identify the occasions when both a project manager and a change manager might be needed.

The past months have seen the release of both the International Institute of Business Analysis (IIBA)'s long-awaited A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) v3 and the Project Management Institute® (PMI®)'s Business Analysis for Practitioners. While both represent interesting developments in the field of business analysis, they also provide lots of information to process. There's no need to go it alone! Join Global Knowledge instructors Cheryl Lee and Adam McClellan for this complimentary, hour- long webinar to learn about the differences between the two guides, how both guides compare to the previous version of the BABOK ® Guide, and where all this might be going.