Discussion Locked

My project has ended in the first phase

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear tech republic members,

I have worked for the last 2 years as a projects manager and my second project has failed in the first phase (the analysis phase).

My project was for a military department in Riyadh, Saudi Arabia. I have had difficulties dealing with a military personal representing the IT department with minimum experience in project management.

My question is:

How can I analyze that failing and avoid any up coming similar projects with similar environment

Thank you,

FAB

17 replies

by why me worry?

The problem with U.S. gov't and military personnel is that the most incompetent seem to be promoted into positions which are well beyond their levels of knowledge or expertise. I have worked in a state gov't agency and have seen my fair share of idiots who were promoted simply due to seniority, yet had absolutely no clue or intelligence to fulfill the role the position required. Thus, my suggestion to you is to avoid dealing with U.S. gov't or military altogether because you will drive yourself crazy trying to sell a project or idea to a bunch of morons who simply don't get it nor ever will. That's why I as a consultant refuse to accept gov't contracts because I've already had my fair share of bullsh*t from the public sector.

by fabishi

This project for Saudi Military and my company is a Saudi company. We kind of far from the US military and gov. touch.

Do you want to say, dealing with military is the same all over? i would agree

But still want to analyze what went wrong...

by why me worry?

who no matter how many ways you present it to them, will simply refuse to understand the project scope nor do they want to make an effort to understand. Many factors come into play, such as time, money, resources, etc, but with gov't, it's usually not about money, as they have tons of money to spend, and more about some egotistical beaurocrat who "thinks" he/she can do a better job than someone who is highly experienced in this technology, such as outside contractors or project managers.

by why me worry?

but I am not sure if you are allowed to disclose such information, as it may be bound by legal clauses of non-disclosure and such. There are too many factors and variables involved that could have killed this project, but to fully analyze what happened, you need to examine the history of the project, from the initial concept, to the time it was prematurely killed. Somewhere in there is the answer to why the plug was pulled. Perhaps it was cost, or time, or resources, or perhaps the intial requirement that justified this project was no longer there or the initial requirements changed so radically that the entire project scope became invalidated.

by john.a.wills

You were working to increase the power of a despotism that suppresses even minor calls for democracy and has no freedom of religion. Perhaps the failure of your project resulted from God's interference in human affairs to make the world a little bit safer.

by rosejm1884

The govt does not have a "lock" on the Peter Principle (people rising to their highest level of incompetence). I have worked for both the private sector as well as the govt and found that "the knife in my back" was more often put there by folks in the private sector. If the military "stabs" you, they often do it facing you...

by fabishi

Yes my friend, I understand the differences between government and private sector...

The dilemma here is not all military not knowing what they are doing, but this project was administrated by incompetent military personal that doesn't have the right experience.
As far as their moral behavior, they were good people..

by tig2

You don't.

At the analysis phase, you are still determining if the project will add value. My guess is that the project was deemed to not add sufficient value from either a cost or time perspective.

Even considering the difficulties you have encountered, it is most likely that the project failed on its own merits.

YOU did not fail. The desire to implement the project did.

When I find myself dealing with "difficult" teams, I try to understand WHY they are being difficult. There is always a rationale. Perhaps that approach will help you going forward.

Best of luck!

by fabishi

Thank you guys for your support but I want to emphasis on some aspect.

My team and I (11 of us) were nothing but dedicated to this project but as you said the requirements were changing dramatically. For the purpose of the customer satisfaction, I had to accept some of the new requirements and it become abuse then the refusal of the total project.

Military personals, the project manager, the IT department manager, the general of the control and on the top the lieutenant general were hard to get them sign ever time on each request. Unfortunately, because of their minimum experience, they agree initially then when things didn't satisfy their higher commander, they reject them. They didn't have a clear image of what exactly want and misinterpretation of what the contract said.

I am hoping my story can bring up some closure to what happened and everyone who would want to work in Saudi Arabia will learn from it.

By analyzing what happened, and creating does and don't in project management in Saudi Arabia, I would have eventually successes in the upcoming projects because they are so many of them in this country with large pay!

Thank you again

FAB

by jck

I worked in government contracting for only 2 years...not because I didn't like the work, but because of the stupidity of the parties involved.

The project that almost burned me out of being programmer:

1) Had a defined timeline, scope of work, etc
2) Had a customer who wanted changes past the agreed-upon deadline for changes to the design
3) A program manager who was willing to allow these changes without requiring the customer to allow timeline slippage for redesign/re-test
4) My employer's willingness to ask salaried employees to work upward of 90 hour weeks to make up for bad management.

It sounds to me like you, indeed, were dealing with some real inexperienced and/or stupid members of military administration who don't want any risk involved in their projects.

It's wide-spread in government, as well as private sector. There's nothing you can do to avoid it.

by tig2

I work frequently with Indian staff. What I have found as an American is that I have to begin each project with some "cultural training".

My Indian partners often over promise and under deliver. From a US perspective, that is worse than failure to deliver. It becomes important to then clarify what will be delivered and when. It is also important for my partners to understand that I WANT them to tell me what they can reasonably do and when. This way, we can set expectations.

Incidentally, the basis for this is that my Indian partners do not understand that they may say "No" or even, "I don't think that I will be able to do this". So when we discuss the problem, part of the process is helping them to understand that I prefer to hear about limits and they are most welcome to talk to me about them.

I have learned this by working with Indians that understand the culture gap and have been willing to talk openly with me about what they perceive as the differences. It is a great help to me.

You are on the right path when you talk about understanding the culture of Saudi Arabia in order to work successfully there.

From a very high level, I can see that you did not have the proper decision makers involved at the beginning. The people who will not sign off for you are an indication of that- they do not wish to lose face.

Okay. Whoever the decision maker is must also sign off. That means that you engage the higher commander on key points. The lesser officers have their place but the guys that can make commitments are the ones who must sign off.

When I start seeing a lot of requirement changes coming to me from lower echelon officers, I simply call a meeting with the decision makers to ratify the change request- and I make sure that I have communicated with my project initiation that I will do so.

A verbal agreement is worth the paper it is printed on- nothing at all.

I think that you are very sincere in trying to develop a "Lessons Learned" document. One tip- when the project ends before implementation, call all of the players (sponsors, stakeholders, team) into a room and discuss what could have gone better. This will help you to identify what you can do more effectively in the future.

Good luck to you!

by a.evans

Nearly all project failures in the early stages are due to a lack of Urgency surrounding the project. I would suggest that you find a way assessing how important the project is by checking out which stakeholders are actively involved. ie the customer of the project, users of the project, CIO and senior staff of all impacted areas. This question is: Is the stakeholder community engaged and aligned to the project? if not, can they be? If not, find another project to manage.

Hope this helps

by drowningnotwaving

... pull the plug on an IT project, but not stop a war, or make it rain to grow crops to save babies and children ???

Does he have his priorities somewhat pear-shaped?

It's an incredible line though. Very useful. I've just instructed our help-desk to use it on recalcitrant clients.

"Your application just did what? Tell me, had any impure thoughts today? Yes, well that explains it. Three hail marys, reboot and call me if it happens again."

by b.lutgerink

Communication between highly skilled IT persons and persons who know little or nothing about this subject can sometimes be "somewhat troublesome" by the differences in views on the subject.

How was the "report" you had with them. Was there a mutual understanding of the goal of this project?

Please do not forget that the project is THEIR toy. Maybe, just maybe, you had a view that was out of their scope and you lost contact with them just because of this.

Maybe there simply was not enough support for the project or it became clear that this software project was NOT what they needed at that moment. In that case, having the guts to stop the project was a wise decision.

The best way (imho) is to look into yourself and see whether there is anything in the communication that you forgot, left out or did not understand.

The fact that this project stopped does not neccesarily mean it is a failure.
It will be if you refuse to learn from it.

Take it any way you want, try to listen to the customers, civil or military and actually tell them what you heard, nothing more, nothing less. Then start molding what you heard into a project proposal.

Present that and ASK whether your assumptions about what you heard are right (making notes during the conversations is helpful ).

Strange as it may seem but are you aware that even military persons are human being?
(WOW, THAT is an eye opener!)
Human beings are known to have needs, and they want to fulfill these needs. The simple fact that you show them you heard them is the first acknowledgement of their needs.

Only after you heard them you can propose a possible solution where, in the presentation, you reflect on the things they said. This way they will recognize their part in your solution.

Boudewijn Lutgerink.

by meryllogue

I agree with everything you say. Sometimes the hardest part of a project is ferreting out the "real" decision maker... the one everyone else is dancing to, and THEN getting him or her into the conversation. The lower-levels will try very hard to shield that person from you, thinking that is the right thing to do. (Lack of PM experience.) So sometimes the hard part is insisting on getting sign-off (face-to-face?) from that higher person. It is intimidating, you have to push your way through ranks of lower-levels guarding the "queen bee" and you have to be prepared to tell QB some hard facts and ask some hard questions. I agree with everything TiggerTwo says about requirements, about agreements, etc. BTW, did you get a CHARTER that was signed by QB? That is the most politically difficult piece of paper (preferably paper, but electro signature will do) you can get in a project, in my experience. You have to really nail down what they expect to see, and WHO is willing to pay WHAT to get it.

by karizmo

It seems to me that your case is a "typical" IT project case. What I could see that the real killer is scope creep (the Scandish Report) which is the top of the food chain in IT projects regardless of whichever phase you reached, or failed to reach. The report also mentions several other reasons, and you may devise your own.

You could conduct a post-mortum analysis on the project to identify the main cause(s), and you use that analysis to come up with lessons learned like: cultural preparation, additional risk mitigation to counter measure the scope creep effect, and even to sell the project to the not-so-willing sponsors to ensure project sucess.

Were these criteria taken into consideration during risk assessment and mitigation? Were contingancy plans for scope creep under-estimated, and so on forth.

The effect of bureaucracy are impaired to country, race, color, religion, sex, etc ... It is a plague, and we simply are not able to have a cure in the foreseen future!

This discussion is closed to new replies.