IT Project Mechanic

Do you know how your project’s performing? Are you sure???

Measuring project results occurs in every project – task completion, performance to schedule, etc. Many PMs, managers and leaders believe that the efforts they are making toward measuring project results are “good enough”. There are, however, potentially fatal mistakes (figuratively) that can be made in managing the data collection and analysis of project measurement results. You can’t manage what you can’t measure is almost a cliché – but this saying has never been more appropriate.

So how do you avoid the 7 deadly sins of measuring project results? Knowing what to avoid or stop doing is half the battle. If any of these sound familiar – stop it! Set out at the beginning of your projects to define a data collection & measurement plan and strategically develop your method to measure your project’s success.

Here they are: (more…)

So you’re managing a project – you’ve got stakeholders, and they’ve got requirements. Rrrright…

This whole notion of getting your stakeholders to give up their requirements ought to be straight forward. You schedule a meeting with the players, setup the stage and they give you their requirements. Then you wake up, stop dreaming and remember one crucial fact;

Stakeholders are not entirely clear on what their requirements ought to be. (more…)

In the early phases of a project, the team members, stakeholders and sponsors are all focused on the work ahead – they are gathering requirements, setting up a business case or getting familiar with the product that will be central to the project. One of the items that doesn’t get much attention during this initiation phase is project success criteria, or said differently, what dictates project success.

This is an innocent omission by most accounts – there should be plenty of time to capture success criteria. However, more often than not, project teams and project managers alike forget to factor capturing and verifying success criteria back into the mix. (more…)

Project managers are all too familiar with how to manage their team’s performance and their projects -this is a core skill you quickly learn and enhance or you die as a PM.

Project managers, in large numbers, are either freaked out by or don’t know how to manage their leadership, managers and bosses to get the job done. This skill is just as important as the ability to estimate and manage tasks, but is slippery in its approach. Hopefully these sugesestions will help wipe some of the goop off the subject and help you manage your leadership better.

First and foremost – managing up is all about time and place. (more…)

The single most important component of project management is communication. Communication is also the one area discussed by PMI and the PMBOK the least and largely left to the imagination of Project Managers. The Standish Group produces a report titled “The Chaos Report” in which they review IT Projects and various aspects of managing projects in IT. For years, the ratio of successful projects against the whole has been at or below 1:3 – that is only one out of three projects are successful. Up to 81% (in one survey) of IT Projects are unsuccessful for one reason or another.

In the forums presented by the Project Management Institute, and featured in PM Network magazine, there are surveys that cover a wide range of topics. One of these was “Why Projects Fail”. Out of 193 respondents, 167 of these said that communication related issues were the primary cause of failure in their projects.

So, not to understate the point – this is a giant, vital and clear project success factor you have to become an expert in if you hope to deliver projects.

There are a few truths about project communication that go without saying:
(more…)

Six Sigma isn’t necessarily built for manufacturing environments. That was the original intended purpose, to be sure. The methodology, however, can accommodate all systems based improvement efforts that may be pursued. The other facet of the question, “How can Six Sigma work for IT projects?” rests on whether the technology based processes are known systems.

This question has a very simple answer – IT projects and processes are systems. They do not take on the physical shape of systems as manufacturing facilities might, but the repeatable series of steps and the defined methods used to execute an IT Project are very similar to all systems.
(more…)

It isn’t enough to be right, or to have an idea that will make the problem go away if you are presenting something “new”. In a majority of cases, others (that you work with) are reluctant to believe an idea or position that they aren’t familiar with. It’s not a trust issue, per se, in many cases – it’s easier to say no than to think about the idea presented and formulate a response. No is easier than accepting that a good idea is out there they didn’t think about. It isn’t a universal truth – but this happens more often than not.
(more…)

In nearly every case, I witness and experience the act of selling as a Project Manager. On a daily basis, I provide to my clients the same exact steps as a consultative sales professional does. There are two distinct differences between the sales professional and the Project Manager:

1. The Project Manager doesn’t “sell” as a full time job – it is a skill that is needed for parts of the project management method.
2. The Project Manager rarely “prospects”.

The first difference should not come as a shock – the fact is that PMs have lots of skills that we use to great affect that don’t consume a huge amount of bandwidth. The second difference may not make any sense if you have never had the fortune of selling or have been exposed to the selling process.
(more…)

Most Project Managers think selling as a PM’s skill is some sort of an oxymoron – being a PM is the opposite of selling. You manage and report the facts, deal with estimates and manage a group of people. The sheer fact of the job limits the ability for a PM to sell, right?

I couldn’t disagree more – PMs must sell, and we sell every day. Some call it negotiation, some call it “positional” authority, but break it all down and we’re selling our hearts out to get the project out the door. We sell to and with our team, to our stakeholders and definitely selling is an integral part of the client relationship. Don’t worry; I’m going to explain my assertion.

(more…)

Welcome to the IT Project Mechanic blog – a place where far ranging topics are discussed, analyzed and introduced that related to IT Project Management and the business of managing projects. The first question I can imagine your asking (and it’s one that I have asked myself) is “Why another IT Project Management source of information?”. I have strongly felt for quite some time that the honesty and brutal truth of the PMs operating model is under fire by academics and “clean room” practitioners – that the reality of a Project Manager’s work and driving pursuits is far different from the manuals, books and methodologies that are currently available.
(more…)