Why project management fails?

Project failure
Project failure

In an interesting article that I have read called “ why does project management fail?”, the author tries to bring his own experience and theories into play. He starts talking about how many companies question themselves and that they think that project management is just just a mixture of tools and techniques that should guarantee their success.
As we learned in class, project management consists of two parts, the first one is dependent on science which are tools and techniques. The second is that its also an art, it is important to put in our mind that even with the best planing techniques possible, even if we put a contingency for every event, things still go wrong. It is in the art of project management that we learn how to adapt and move on to make something work.
The author goes on explaining that there are some factors which lead to the failure of project management in organisations such as the” Lack of knowledge, lack of organisational policy, lack of enforcement of policy and procedures, lack of consideration for the magnitude and complexities of project management”. It is true that project management tools are only as good as the people who use them and it is a philosophy that would work only if everyone in the organisation or at least the specific project is onboard.
Some times it is better to outsource, if a certain company doesn’t have enough knowledge/resources and doesn’t feel it has the discipline to adopt project management methodology. There are some companies whom specialize in consultancy and project management, in fact outsourcing could save those companies a lot of money and energy as well as add proficiency.
It is also important to look at the role of the project manager himself, we spoke in class about Active and reactive managers. I think that the article focuses on the benefits of active managers and dismisses reactive managers. It is true that being active means that you should be ready for different scenarios and prepare all contingencies in advance, but that is the science part. Reactive management is more like the art part where you would have to work with whats introit of you. A balance of the two is always needed, you don’t want to start a project without any plan, in the same same time you don’t want someone whom wouldn’t know how to respond when something goes wrong and he had no way of putting a contingency plan for it.
Some think that project failure is only due to not being able to deliver to costs or expected quality or even missing the deadline. Those are all valid reasons, but leadership and organisation philosophy is what could be put as the thin line between project success and project failure.

Reference:
http://www.projectsmart.co.uk/why-does-project-management-fail.html

Will the Qatar-Bahrain Causeway Ever See the Light of Day?

qatar_bahrain_causeway

The Qatar-Bahrain Causeway is a continuously delayed project in the Arabian Gulf region. The project consists of constructing a 40km (25mi) bridge (claimed to be the longest in the world) between the Qatar and Bahrain.

Plans for the construction of the bridge were first made in 2001. The project was approved for construction in 2005, and a formal agreement between the two GCC (Gulf Cooperation Council) members was signed in 2006 to form a company, the Qatar and Bahrain Causeway Foundation, that would manage the project. Everything seemed to be on track for the project when it was revealed that construction would begin in 2008 and construction would last four years.

However, a series of events have dramatically delayed the project. The 2008 financial crisis certainly had a toll on the mega project, causing the estimated cost of the project to rise unexpectedly. In 2009, the initial plan to have the bridge accommodate motor vehicles was changed to include a railway as well. The railway itself is part of a GCC-wide railway project. Delaying one critical project can and will have significant effects on the other. Numerous re-designs to the bridge and escalating costs further delayed construction initiation from 2008 to 2011 and then to 2015, with a plan to complete the causeway shortly before the FIFA World Cup 2022 held in Qatar. Of the two countries, Qatar especially needs to manage all the projects they have at hand before hosting the world’s biggest event. This can be achieved by assigning more resources to all their projects, something not too difficult for the rich gulf state.

bahraingraphic

Politics always play a role when a project involves multiple countries. Bahrain and Qatar have had territorial disputes since the nineteenth century. One case is that of Hawar Islands, a series of islands located between the two countries. In 1939, when both countries were under British rule, London ruled that the islands belonged to Bahrain. Qatar tried to appeal the decision multiple times, only for the other GCC countries to intervene. In 2010, a Bahraini fisherman was found roaming Qatari waters, leading the Qatari coast guard to fire at his vessel. This incident reignited the dispute over the islands of Hawar. The bridge, dubbed the “Qatar-Bahrain Friendship Bridge”, ironically, may never see the light of day if these differences are never settled.

All obstacles and issues aside, the bridge will boost the economies of both countries considerably. Currently, a trip between Bahrain and Qatar can take up to five hours, and involves crossing through Saudi Arabia, which can be problematic for non-GCC nationals trying to obtain a Saudi visa. The new journey will be cut down to less than an hour.

If this project is ever completed, it will be one step closer to unifying the Gulf states as one country–a project of its own that’s been frequently discussed.

Do you think the Qatar-Bahrain Causeway will get completed before the 2022 World Cup, if ever? Is bad project management and estimation to be blamed for the delay of the bridge, or are there other factors?

 qatar-bahrain-friendship-causeway-size-chart

Sources:

http://countrystudies.us/persian-gulf-states/44.htm

http://www.qatarvisitor.com/travel/Qatar-Bahrain-bridge

http://en.wikipedia.org/wiki/Qatar_Bahrain_Causeway

Agile Project Management Methodolgy

While researching sources to use in my project management blog post, I came across an article called “Top 10 Project Management Trends For 2012” written by J. LeRoy Ward from ESI International.  The trends that Mr. Ward enumerates in his article relate to changes in the project management practice (PjM), changes in management perception of the value achieved by using project management principles and the employment landscape for project management professionals.

The full text of this article is available at http://www.manufacturing.net/articles/2012/01/top-10-project-management-trends-for-2012.  I will cover the widespread adoption of Agile in this post while my second post will cover the adoption of collaboration software tools.  Together these two trends will have a profound impact on PjM and project success rate.

Traditionally, PjM used the waterfall model popularized by Dr. Winston Royce in his seminal paper entitled “Managing the Development of Large Software Systems,” advocating a production line method to software development in which each phase must be completed before the next phase is started with little to no iteration or communication between phases.  Although it made sense to use this methodology in the 70’s and 80’s when expertise was highly specialized and computing resources were scarce, it soon became apparent that errors and changes found in later phases of development were extremely costly to address.  These errors or changes required stopping the current phase and going back to previous phases to fix or change requirements thus adding expensive delays to the project, increasing cost and in some cases completely abandoning the project due to severity of the errors discovered at a late stage of development.

With the advent of the internet and dramatic cost reduction in computing resources, alternative project management methodologies are being experimented to address inherent drawbacks in the waterfall model.  Over the years, Agile project management methodology has gained popularity. Agile uses a different approach to project development.  It attempts to provide many opportunities to assess the direction of a project throughout the development lifecycle. This is achieved through regular cadences of work which are known as sprints or iterations, at the end of which teams must present a shippable increment of work.  This iterative process allows project teams to quickly adapt to changes or error detected in an iteration. Another benefit of Agile is allowing project teams to divide a large deliverable into key components prioritized by the customer thus allowing them to introduce products faster to the market.  Customers can evaluate the reception of the product and then decide to either expand or shut down the project. 

Thus, Agile provides greater flexibility and faster time to market for products.  It ensures higher project success rates as the cadences can be setup to ensure minimal resource usage per sprint.  Highly specialized and costly resources can be allocated in the just-in-time method to optimize usage and cost.  Nevertheless, project managers should be aware and manage the drawbacks of Agile such as spinning in a single iteration and scope creep.  As long as these issues are managed properly Agile or some hybrid form of Agile will become a dominant project management methodology of the future.

What are some of your experiences using Waterfall or Agile or both?

 

Project Managers vs Workers

During our first class, we got to do our first exercise. This exercise was making the paper puppets. Though I was not involved with the workers or even the timer guys. I was observing the whole operation. The teacher acted like the project manager, and 5 class colleagues were doing the assembly line workers job.

During this exercise, each worker was given a task to be done. The teacher was putting pressure on them as she was acting like the project manager. As a result, they were trying hard to finish as much paper puppets as possible. I was observing the behavior of each worker, since the last three workers were sitting idle until the second worker finishes her job. Her task was a longer task than the rest, thus she was a bottleneck. The class was fun and we have learned a lot.

Some of what we have learned from this class was:

  • The way you layout the operations space, is going to influence the production and product quality, it even influences the communication between the workers. During our exercise, though they were close to each other, each worker was only talking to the one right next to him/her.
  • During the exercise, the first worker tried to optimize the way he worked but the project manager which is the teacher told him to follow the process. This teaches us that if we ever want to  re-engineer a process, we need to talk to the workers. They see the obstacles, they most probably know how to optimize their work.
  • During the exercise, the workers found defected paper, but due to the pressure, they passed it on just to finish the process. What we could learn from this, when project managers or management puts so much pressure on workers, workers will have ethical issues and lead to high rate of defected products.
  • After we were done with the exercise, the teacher asked the workers how did they feel about their work load. Some said they were doing so much work, others said they didn’t have to do much. It is probably one of most faced issue with operation workers. Work isn’t divided equally among workers.
  • We also have discussed what we could have done to help our second worker which she had more complicated work to do, we have came with so many solutions which seemed to help, like hiring one more worker with her. Or distributing the work among other workers too.
Here are some pictures that I took during class while we were doing the exercise: (Note: Some faces are blurred because they asked me to blur their faces). Edit: One more colleague asked for her picture to be blurred., so I re-uploaded the images.