Articles (629)

0

FEATUREJune6Getting the Most from Your Project Staff
Part 2 of a 3 Part Series

 


As a Project Manager you are tasked with getting work done through others. It may seem simple, after all these individuals are assigned to the project team and just need to do their job. But this is not reality.

What is reality is that project resources are often assigned work beyond your project and may even be involved in other projects. It is typical in the popular matrix project organization that team members do not report directly to the project manager, but rather a functional manager. This makes it even more important that the project manager have the skills to get work accomplished through others. Even the most experienced project managers continually report this as one of their top challenges.

In this three part series you will learn techniques that will maximize your ability to get the most from those individuals assigned to your project. The strategies presented will provide a solid approach that can be used immediately with your team.
Tuesday, 05 June 2012 03:00

Why is Benefits Management so Hard to do?

Written by

Almost every company accepts the need to manage project benefits, but very few actually do it!

Earlier this year, I started a discussion and poll on the topic of why benefits management is so hard to do. The response was intense, with over eighty-two PMO managers, consultants and professionals related to the topic. This article summarizes and comments on these responses and draws some conclusions.

The poll asked respondents to select one of five causes why benefits management is so hard to do. The results of the poll follow. This article will be structured around these five potential causes and, of course, as one respondent suggested, all of the above may be the winner.

In addition to upgrades and enhancements to their flagship ERP solutions, for a variety of reasons companies may also turn to specialty software companies for solutions to business problems. The rationale for using specialty software products can vary from filling gaps in their solution portfolio, gaining a competitive edge or responding to an outside factor such as new regulation.

Although these specialty software solutions are smaller in size and scope, they do require a relative measure of project management consideration. Many times I have seen dismissive or optimistic project managers assume that because a solution is smaller in size and scope, one can take a very relaxed approach to the implementation life cycle. In fact, greater care than what is found on ERP implementations needs to be emphasized in certain areas of the project.
Tuesday, 29 May 2012 08:00

Agile Misconceptions: What Agile is Not

Written by

Introduction

Over the course of my career in software development, I have had the fortune of working in a wide variety of companies employing radically different approaches to the software development life-cycle (SDLC). Some strictly stuck to traditional Water Fall. Others called themselves "agile" but never actually bothered to adopt any agile framework, and were thus a blend of Water Fall and Agile—and all too often, not a successful blend either. Another strictly adopted a true agile methodology and decided that there was no need for a PMO since, as they put it, "we're SCRUM." Other companies used the same Scrum methodology but saw the value of having a PMO as well.

As I have closely followed discussions on Project Times (and other blog sites), I have noticed some discussions around Project Management methodologies that are fine in theory, but often seem divorced from real-world applications. You can often find arguments prefaced by statements such as "good project managers do X," or "the PMBOK methods require Y," or even "any experienced Scrum Master knows..."

In today's competitive global market, all companies are looking to make improvements that drive bottom line results. Many of these organizations are turning to process improvement methodologies such as Lean Six Sigma. While this is a great starting point, your first question may be, "What exactly is Lean Six Sigma and how is it different from Six Sigma or Lean?" Your next question may be, "If my company is not in manufacturing, would Lean Six Sigma even be applicable for my organization?" In this article, we will answer these questions by providing an overview of the fundamental framework of this methodology. We will also draw on our SEI experience and take a look at how companies are using Lean Six Sigma as well as some of the common pitfalls.

When I ask students for their biggest challenges in managing projects, they usually tell me it's the lack of people, time, or money.  They just don't have enough resources to get done what's expected of them.

I don't doubt it.  The relentless battle cry to reduce waste and increase productivity has many project managers feeling like they are expected to build a bridge over the Mississippi River with one team member and a box of toothpicks.  By tomorrow.

How much of this challenge is exacerbated by the lack of clear organizational priorities to guide how those precious resources are allocated?

Feature May16 40432452 XSOne of the critical factors for project success is having a well-developed project plan. This article provides a 10-step approach to creating the project plan, not only showing how it provides a roadmap for project managers to follow, but also exploring why it is the project manager's premier communications and control tool throughout the project.

Step 1: Explain the project plan to key stakeholders and discuss its key components. One of the most misunderstood terms in project management, the project plan is a set of living documents that can be expected to change over the life of the project. Like a roadmap, it provides the direction for the project. And like the traveler, the project manager needs to set the course for the project, which in project management terms means creating the project plan. Just as a driver may encounter road construction or new routes to the final destination, the project manager may need to correct the project course as well.

What qualities are most important for a project manager to be an effective project leader? It's a question often asked and one that makes us sit back and think. Over the past few years, the people at ESI International, a leader in project management training, have looked at what makes an effective project leader. They quizzed some highly-talented project leaders and compiled a running tally of their responses. Below are the top 10 qualities in rank order, according to their frequency listed.

Wednesday, 16 May 2012 06:00

Project Success Plans - Planning for Success

Written by

Co-authored by Jeff Hodgkinson and Gary Hamilton

"A Project Success Plan can be a platform for ensuring all project stakeholders start off, and continue on, the right footing."

Setting up projects to succeed in the view of the customer/stakeholder is a critical part of the Project Manager's role. We suggest that, as part of project planning activities in the early stages of your project, you should hold a Project Success Plan (PSP) meeting with all key team members to agree on the project's goals, and to discuss the emotional success factors that will ensure the team gels successfully to deliver the required outcomes.

Co-authored by Jeff Hodgkinson

Realizingbenefits4_mainWe believe a simple methodology can be applied to attain Benefits Realization. You can achieve true project success by ensuring that:

  • Project benefits are clear, concise and relevant in 'value creation' terms from the Business Case onwards, and that they directly relate to your organisational strategy
  • People are held accountable for achieving these benefits
  • Benefits stated in a Business Case are actively measured throughout the entire initiative, ie:
    • During the project lifecycle (particularly if it is released in phases)
    • After the project is closed
    • When the product/output starts to be used
  • Appropriate action is taken if required to alter direction (i.e. the organization changes course and the intended project benefits are no longer relevant)