I have been doing project management for seventeen years already. Although I was always trying to apply correctly the methods, identify and address risks properly, communicate with the team on a daily basis (this has never been a problem in our projects), communicate with the customer often, I have suffered the problems of having to work long hours and weekends to meet dates, “everything is urgent”, …
What is the purpose of project management? – Make sure that the project meet its stakeholders (clients and organization) needs. True?
If it is important to deliver quickly and on time, why what is [typically] measured is the effort to fulfil the tasks and not the actual time of their completion?
If quality is important, why defect data is so seldomly collected and analysed?
If cost is important, why is it so hard eliminating activities that consume resources and add no value?
Is there a more pragmatic way of managing projects and services?
What I usually see in the risk tables of project or service plans are “deliver late”, “surpass the budget”, or “does not pass customer acceptance due to unclear requirements”.
At the same time, teams most often complain from not being able to meet deadlines, and surpassing budget.
Obviously we are rather attacked than attacking risks.
In 1992 Bill Clinton chose an interesting slogan for his political campaign: “It’s the economy, stupid”.
Of course, there were many other important topics for the country and a lot of factors that were influencing their resolution. However, Bill Clinton’s key message was focused on the core driver for the country, the economy.
This month I had an interesting service for the IT department of a bank. I say ‘interesting’ because they asked me to visit them, see how they were carrying out and managing their projects and tell them how I found it. Nothing about particular problems they want to resolve, objectives they are pursuing, or a method that is interesting form them. Just come – see – and- give us your opinion.
Four years ago I started collecting photos of the problems that software development organizations face, regardless of the working method they use. Last year I started expanding my collection with photos from industrial companies.
Do you know which the most recurrent pain is?