Resource Library

Introducing new talent to an established organization can be difficult for many reasons. Seasoned employees may view the incoming new hires as "too green" or as not having the required skills to contribute in a meaningful way. They may worry about having to "waste time" teaching the newbies things that they should already know or get aggravated when the new employees are not familiar with "the way we do things around here." Additionally, it is difficult to know if the right new hires are being put into the right positions for their interests, abilities and talents. After all, a resume and an interview can only tell a hiring manager so much about the person they are bringing on board, and often talented employees are simply being put into a role that is not a good fit.

We often discuss how to manage projects, but we overlook an essential step: proving project value. Proving project value ensures that organizational strategies are aligned with project objectives.

Your organization and a seller have just agreed to a contract with a total cost of $150,000, an estimated profit of $10,000, buyer/seller sharing of 70/30 and a ceiling price of $170,000. What is the PTA (point of total assumption)? A. $170,000 B. $160,000 C. $164,2...

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.

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.

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.

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.

Accessing cloud-based resources, whether they be IaaS/PaaS/SaaS-based, is very convenient. With a browser and Internet connection, you are up and running. No driving to your work office, no need to log into the corporate network. Just open up your web browser and go. This convenience, however, comes with a security risk. All of your business work is conducted over an insecure communication network. Unlike your office network, where the network link between you and the data center is under corporate control and is physically secure, the cloud access link is over the Internet.

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

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.