Types of Software Projects

A friend of mine used to classify projects into 2 mutually exclusive categories:

Strategic or Political projects
Profitable projects

At first, I thought this classification was a joke, but after some contemplation, I found that it is very true… Most or almost all of the projects I worked in fell under the first category (strategic). This means that I was either always chosen to work in such projects or that all projects are strategic non-profitable ones!! Which of course cannot be true, so, let’s stick to the first assumption!

Strategic Projects Characteristics

First of all they are… Strategic!
Either start with quick-wins or are major-projects
Non-profitable
Low or no price quotation offered with pleasure to clients
Very tight in time
Killer teams are allocated on them
Strategic importance and priority only apply on the team who works in the project, i.e. not on other needed helper functions such as IS, DB or Operations teams
Teams working in them are burned out/destroyed after some time
Clients don’t accept the output
Clients don’t pay bills
Most of the times, such projects are discontinued after a while. Termination time is based on how much the company can endure the financial losses which by the way are looked at as sacrifices (not losses). Sometimes termination depends on the number of months the team spends sleepless
End catastrophically, catastrophe size varies from losing a team to losing a whole company in addition of course to losing the client himself and the company’s reputation

Profitable Projects Characteristics

Are not Strategic, this is obvious!
Are usually support projects (non-new-development)
Clients are billed on time and material basis

I think I might have worked in a profitable project once, but I can’t recall anything about it!

Comments

The Triangle of Tactics

Sometimes referred to as the Triangle of Horror… where the PM tries his best to maintain his balance while walking on the very thin project rope between this triangle and the Project Constraints Triangle (time, cost & scope). The triangle sides represent: The Team, The Client and The Management Every side of this triangle is obsessed by the sole idea that the other two sides want him dead, i.e. the team thinks that the client and the top management want him dead and vice versa. Usually a good PM gets lost while trying to maintain this triangle in good shape to keep all parties satisfied and happy while making them think they are his first and only priority to get out what is needed from them for the sake of the project. From my perspective, this is a much harder balance to keep rather than maintaining and managing the Project Constraints Triangle… It highly depends on people, their culture, maturity level, and on the PM’s ability to understand this and deal with it in a ...

The Bus Driver

They took some time to plan for the trip… They drew the road map, bought some food and beverages… and got equipped with the necessary tools… They were going to travel through the woods to draw the magnificent scenes which were observed by their neighbors early this year… This wasn’t their first trip together as a team, though they were all excited… The bus driver was in charge for making the big decision in the trip while taking care of the travellers’ team while of course driving the bus and communicating daily with his supervisor in the station. The map was clear, the weather was very well studied, though the bus driver expected to pass by some pitfalls in the road as there were some reparation in the way. He reported this to his supervisor and requested to take some more supplies just in case they have to camp one or two days more, but the supervisor refused “ the trip has to be completed on time and the painting should be ready for sale by the end of the week ” Anyways, ...

The Triangle is missing The Circle

By experience -the bad one of course- I discovered that the famous Project Management triangle is missing a very important containing circle… The Strategy Circle . The Strategy Circle is my simple explanation for many of the catastrophic situations projects end up with. I totally believe that this should not happen and that Strategy exists to set goals and directions for the benefit of organizations and accordingly for the benefit of projects and teams. Unfortunately, I witnessed many cases where it was exactly the opposite. I was an eye witness of the failure of many projects and sometimes companies because of misunderstanding the meaning of Strategy and how to use it to bring companies to success. Some companies bankrupted because of this! De-formation Effect The Strategy Circle is sometimes surrounding the Project Management triangle and thus imposing pressure on it and suppressing it and some other times it is pushing on the triangle from the inside and thus inflatin...

A Project Manager's Diary

Search This Blog