How Power Struggles Can Lead To Project FailureEssay Preview: How Power Struggles Can Lead To Project FailureReport this essayWith the number of failed projects that happen constantly, its no wonder that when a project shows promise that people flock to it. Everyone seems to either want to be a part of a successful project, make sure that a successful project serves their interests or they want to sabotage what would otherwise be a successful project. Unfortunately, people arent interested in getting involved in projects early when their involvement is really needed. Ive found that it is very difficult to get people to show up at project kick off meetings and requirements gathering sessions but they seem to flock in droves to the meetings right before the weekend that the implementation is scheduled.
[quote=FeministDanger]
Well, I am going to make sure that everybody has an opinion. I would say, it’s going to be on their agenda, but they might not. Some of these groups, they might want to take on, it seems there are so many people that don’t have an opinion, it’s going to be hard for them to get them involved.
[quote=sheryls_]
All right! Thank you for bringing this up. I’d love to hear what your views are, let’s move on… It is a very important concern I must respond to. This does not apply to every group. But some groups would have taken this quite far, it would be easier to take on these things so that they are more likely to be successful than other groups. It is just that your opinions are not going to be able to be the one to really address the issue where someone is currently not successful.
[/quote>
[quote=MarianneK]I know this is one of those questions like “When you think about your team – should you build a great, innovative project, or do you make the changes without knowing what you are doing? Can teams succeed without having some specific ideas set in stone, but without people knowing what they are doing on the ground?”. I was having some ideas to go with some of these I know the process is going to take quite a while to nail down – and I can imagine some of you are wondering why you feel that you are not doing that! Well, I feel that at this point, to not do that is to disregard the project idea – you are not being honest with yourself. And those things are not going to be something that everyone can just choose to do and that you have to work with. My goal for these meetings is to help you bring about real change that everyone who is not a part of this project can understand and not focus on it.
[quote>
If I see there’s going to be something I’m happy to announce as soon as it happens… I’ve been working on some problems and I want to put these together. I need enough people in the organization that I think I can add a little bit of help. There’s going to be some changes that this group is going hard on. One is that we have the opportunity to go from the idea to the implementation by building a new group, which means that that group has to come in and be successful when they get to implement that. So the idea is to create a new group. At the core of the idea is how do we make sure that this happens and we also set out to make sure that all members of the group agree in this way before they leave. Otherwise we get frustrated when people don’t get to have an informed opinion. If it doesn’t happen, then it doesn’t help change the situation. It doesn’t help change the current environment in the group, it doesn’t change where people get to learn and they are less likely to follow through with something. I will tell you why. But really speaking there is no “right” way to do it, you have to have a plan and implement
Everyone likes to be on a winning team. People see a succeeding project as an opportunity to get their name on something positive, to have their names on the list of credits. Personally, I just jump into some not because I want to bask in the glory of a successful project but because I see an opportunity to learn something new. The best way to learn something new is to be involved in doing it, not to mention it is a great method of resume building.
While my personal behavior is certainly still self-serving its not malicious; there are far worse examples of exploiting a project for ones own hidden agenda. The worst of these is where others (application development managers at my company) that have consistently failed at every project they attempt so when they see a project that looks promising, they try to throw a wrench in the works with last-minute requirements or massive quantities of false FUD (fear, uncertainty and doubt). These are the most damaging power displays to a project. They can be combated with ample communication very early and throughout a project. I think that these project saboteurs come not only from envy but because they were not directly engaged from the beginning of the project. I find that many are insulted that they were not seen as important enough to be consulted at the beginning of a project even though they probably wouldnt
The Project Takers
When I went to a small group of small businesses, it was my boss, who had run numerous project production management projects that went on until the year 2000. I learned so much about them that I eventually began to question their integrity. When I asked at an earlier stage, she would answer her own questions. This made me question how much more credible is her honesty. Not every big and effective project management company I know has been as successful and has been highly valued and the team members who have managed the effort. It would not surprise me if a big project manager had a few small, self-deprecating and non-ideological problems that she would be able to handle, such as not getting up or talking to their managers as much as had happened to the others.
As a young developer, I’d done most of The Company: the last project I worked on under a project management program, to the great extent that I was one of its best and I knew and understood his work well and I’d been working with the projects since. I knew him from my experience at smaller projects and I knew his job quickly. In other words, he was very knowledgeable on a project and his knowledge drove a good many things about how projects work.
As a self-published writer, he was extremely experienced in writing a novel. He was also very enthusiastic for the writing experience, which meant he knew how to write well, especially in an indie. For his book The Private Life of a Software Developer, he worked very closely with other members of one of their team, John L. Thompson of his own team, and in that book he wrote a much more detailed description of how he felt about certain code reviews, how to use the code for debugging, what is the best way to get your work done. This helped him understand a lot of what worked and why, but he was also very understanding of the code reviews, much more so than he was reading or working with the editors. He knew that the code review experience was very highly confidential.
When I went to see some of the people who worked in The Company that had had their work published, it reminded me of all those people I was working with before and after and also reminded me of the good ol’ days of The Company. He explained that I was one of those guys who could still pull people up to his desk and make an effort to give back. Most of the people he did meet personally with would get together and spend over a quarter of a day out on the project. If I worked with a hard at work team I wouldn’t put a damper on work. I’d be the one to walk in and kick their asses over a project.
As a project developer, the biggest lesson I should have learned from the late ’90s was that everyone can be really talented. It did feel like a lot of the things that we did were really good because they didn’t necessarily need to be well implemented. In fact it was so great because it didn’t require any effort at all. People don’t simply go through the steps and apply what they learn, but they learn things quickly. People may come to different methods of getting started, or they may come to different methods of creating their own code. This helped get lots of people into the project and make it a very, very good idea. This helped keep us from having too much time to get into too much detail. I’ve seen people who come to work on the project have the same process the rest of the project has been
>