Flylib.com

Books Software

 
 
 

PSI CONTRIBUTION

   

PSI CONTRIBUTION

graphics/psi.gif

To get most or all of your ten points here is very simple. The ten points is a measure of how much you are going to embrace all the jobs on a project and take them forward. Pause for a moment before you award yourself an automatic ten here.

A ten means that you are going to move heaven and earth, do whatever has to be done to make a project happen. Irrespective of formal structures, political considerations, resource or personnel constraints, famine , fire, flood, pestilence, war, nothing is going to stand in your way.

Now it seems to me that as human beings we may be able to bring such energy to bear on some projects. By and large, I don't think we can do it on all projects we become involved in. This, of course, merely reflects the rather obvious fact that some projects are more important than others. Thus, there may be some projects under our control that we are going to do everything possible to make happen. Then, fair play, we draw our ten points. Similarly, though, there may well be others where we decide that we just aren't prepared to give them that level of energy. There is no inherent problem with this provided we recognize that the lower score we award ourselves here reflects the fact that things may get forgotten or fall between the cracks, and we need to perhaps keep a weather eye out for these.

STRUCTURED PROJECT MANAGEMENT

Planning the project

  1. VISUALIZE WHAT THE GOAL IS; SET YOUR EYES ON THE PRIZE

  2. MAKE A LIST OF THE JOBS THAT NEED TO BE DONE

  3. THERE MUST BE ONE LEADER

   
   

Chapter 4. STEP 4: ASSIGN PEOPLE TO JOBS

INTRODUCTION

EACH JOB HAS A NAME

PEOPLE'S OTHER COMMITMENTS

MONOLITHIC TEAM OR FLAT STRUCTURE

HIERARCHY OR TEAM STRUCTURE

MAXIMIZE STRENGTHS

ASSIGNING PEOPLE TO JOBS

ASSIGNING PEOPLE TO JOBS WITH FORM 2

APPLICATION TO SOFTWARE ENGINEERING

PSI CONTRIBUTION

   
   

INTRODUCTION

Many of the projects we encounter are too big for one person, and are carried out through using other people. When I first drafted this section of the book, the Gulf War was raging. This was a project which had nearly three quarters of a million people on the Allied side alone.

The overall goal of the project can be thought of as a picture broken down into pieces like a jigsaw puzzle. There are as many pieces as there are people. If each person completes his piece, the picture will complete, and the goal will be achieved. (Note that by our definition, each person becomes engaged in his own individual project and can apply structured project management to that project.)

There are three things you need to do as part of this step:

  1. Make sure each job has a name against it

  2. Take people's other commitments into account

  3. Try to maximize the strengths of the team you've got.

We discuss each of these in turn .

   
   

EACH JOB HAS A NAME

One of the things we do in my company is to turn around projects that are running out of control. There are basically two phases in doing this. One is to understand why the project is the way it is; the other is to do a new plan (that is, apply Steps 1 “5) to take the project from where it is now to where it needs to be. One of the first things we do in trying to understand why the project got into a mess in the first place is to take a look at the current project plan.

Sometimes there isn't one! If that's the case then the investigation is pretty much over.

More often though there is a plan of sorts. That being the case, one of the most common things we find is that jobs don't have people's names against them. What you find instead are things like the following:

  • ANO (also known as "A.N. Other")

  • Mr (or Ms) X

  • Programmers 1 “6

  • S/W Eng.

and other equally mysterious personages. In other words, the jobs were never assigned to anybody. You might think that people wouldn't be too surprised then if these jobs weren't done. But, invariably, surprised is exactly what they are.

The first thing in assigning people to jobs is that every job must have a human being's name against it. Any of the above or organization names should be avoided as far as is humanly possible. Even if you are subcontracting something so that an organization is actually working on one of the jobs on your project, the name you should have against that job is the member of that organization whose ass is on the line for the successful delivery of that particular job.

It may be that at the beginning of a project you don't know who all the people will be, and that's OK, but then one of your priorities as project manager has to be that the unknowns get replaced by warm, living, loving human beings as quickly as possible.