I would like to start with a story.
The Story

A particular year, an elder of the community started to practice a ritual. A ritual dedicated to the god of rain. It consisted on stepping over a small rock, and pray to the god of rain very hard. If his prayer were good, then a big rain will start. The elder knew when there was about to be a rain, and he used that trick to convince people the god of rain existed. Therefore many people started to believe in the god of rain, and thinking he will be able to give them rain on the dry season.

The dry season didn't appear for many years. It was a great time for the community, because they finally got time to do other things, things they always wanted to do. After a couple of years, everybody forgot about the dry season or saving water.

A few months later, everybody was desperate for water. Everybody in the community blamed everybody else, because other don't pray as hard as they. The elder kept telling them, they were not praying right, so the god of rain got mad at them. Many people from the community left it in search for water somewhere else. The ones who stayed died before the next rainy season arrived.
What does the story has to do with my failing project?
You might be asking, "What does the story has to do with my failing project?"
Blame everybody else
The first thing that happens when project starts failing is everybody points their fingers to others. People blame others, because nobody followed the process as hard and good as they did. Nobody wants to be responsible for anything, because they know it will be used against them. Everybody always have a reasonably good excuse not to do things right. Nobody is able to backup what they did in the project. Bottom line, nobody and everybody at the same time is responsible for the project failure. As you go up in the hierarchy, more weight you have in the results of the project, so more responsible you should feel.
A process leading to nothing

The Parasites

The Followers

The Lifesavers

Process Managers
There is an elder telling them which process to follow and they weren't doing it right. Same thing you get from your manager when the project is failing. They define or inherit a process to follow for the project, and they think by just following the process they will lead to results. They only focus on the process adherence, instead of looking to add value to the project.
They spent their time updating reports, and asking for time logs, status updates, and looking at to-do lists. They do not care what the lists are about, or why you had to spend twice as time as you should. They never review what has to be done, just review if the process was followed. They do not attempt to create a process to add value and reduce waste. They just aim to copy something they learn from internet or on a two day course. If there is no value in the project coming from managers, then for sure the project will fail.
The only way they know to save a project from failing is to push the team harder. Sometimes this works, because parasites need to be pushed to get them doing something. Most of the time, they only get something from the lifesavers, putting those on the verge to leave.
Value comes from people, not from the process. The process will only help to increase or decrease the value from people. If your team cannot create value, then the process is useless and might just waste the little value the team has to give. If you cannot get value from the team, then you need to stop, reconsider and start again.
Is leaving the only option?
First think what a project is. A project is created with an objective to generate value, with a time frame and limited resources. Projects are used in companies just to give work a frame or boundaries, to make it measurable and manageable.
Can a team provide products or services without doing it in a project? Yes, they can, and they are probably better without projects, because they can really focus on what is needed when it's needed. They will be completely based on value driven work.
Some companies are project driven, some are value driven, some are wish driven and some are not driven at all. If a project does not have an objective to create value, a time frame, and resources well defined, then you should reconsider your project, and call it a wish.
Wishes are the main cause of failure, because a wish is hard to express and understand. A wish is not measurable or manageable. They are hidden as projects and the lack of measure gives management the sense of everybody is not working hard enough. Management sets an impossible end date to make the lazy team work hard. That generates the sense of failing to all the team. This causes every body to run and trash things to get to that impossible date making things worst.
Your management expects everything to be done by the end of the time frame without committing to the project at all stages. Your management only focuses on process adherence and not on how to get more value from the team. Your are working on a wish without realistic planning and measurable goals. Your company does not create an environment to keep the guys who can make a difference. You should start asking yourself what am I doing there?