Live Chat
Monday - Friday 8am - 6pm EST Chat Now
Contact Us
Monday - Friday 8am - 8pm EST 1-800-268-7737 Other Contact Options
Checkout

Cart () Loading...

    • Quantity:
    • Delivery:
    • Dates:
    • Location:

    $

Resource Library

Filter By

Topics

Show Filters
Result Filters:

107 Results Found

Results per page: 10 40 80

A Unified Model for Describing a Project Plan

White Paper | June 05, 2013

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.

How To Improve Purchasing Performance By Categorizing Suppliers

Article | Feb. 20, 2013

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:

The Business Process Analysis for a Project Manager

Article | Feb. 15, 2013

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.

Service Portfolio Real World Example – Cloud Services Provider

Article | Nov. 28, 2012

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.

What is a Service Portfolio?

Article | Nov. 14, 2012

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.

Meet Customers' Needs Through Agile Team Development

Article | Oct. 26, 2012

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

Meeting Customer's Needs Through Agile Development

Article | Oct. 12, 2012

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!

How to Apply Knowledge Management to Project Management

Article | Aug. 24, 2012

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.

Importance of Lessons Learned in Project Management

Article | July 27, 2012

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:

When Learning Fails: Six Classic Mistakes and How to Avoid Them

Webinar – Recorded | May 12, 2012

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.