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.

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.

The principles in this white paper help you introduce greater predictability into your own Agile requirements activities, both individually and across your organization. As you start to apply these ideas and pose these questions, you'll likely see certain patterns emerge that will help you establish your own set of practices that make Agile work for you.

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.

You know you need to invest in training, but how do you get the best return on investment (ROI) from your training dollars? To help you make smart training decisions, we've put together this guide, which illustrates some alternative and little-known payment options, the types of discounts and promotions available with training and a suggested list of courses that give you excellent value.

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.