What makes a successful project?

[Rookie]

Now imagine trying to run 5 test projects at the same time using one test environment and two amateur testers, who can’t take over each other’s work, when the customer can’t even tell you which projects have which priority.

I'd sooner not. It sounds like a shambles. 3 testers for 5 projects? FFS.

[Mich the Tester]

I'd sooner not. It sounds like a shambles. 3 testers for 5 projects? FFS.

Two testers, neither of which is a trained tester. I’m the one with the qualifications but I’m not allowed to test because I don’t have user rights.

[TykeMerc]

So much for my list, this is like herding cats!

That's Project Management in a nutshell.

As others have already said the key to a successful project is obtaining, understanding and satisfying the clients requirements. That's mainly a matter of stakeholder management.

[Pondlife]

It's all about management of expectations. Disappoint early and often then they won't be so shocked at the end.

[Cyberman]

In my experience, one of the most important things is to ensure that proper analysis is done initially to define the scope, and this should be signed off.
Then you make sure that you have a person with sufficient authority external to IT to ensure that users agree at every stage during the project and sign off at the various phases as they complete. This person is also responsible for ensuring that all designated users are dedicated to the project and available as required for testing, meetings etc.
On the IT side you must ensure that people have the necessary skills and training where required.
I have never worked on a failed project, funnily enough.

[TheBigD]

Two testers, neither of which is a trained tester. I’m the one with the qualifications but I’m not allowed to test because I don’t have user rights.

Someone ought to mention that to the managment

[Platypus]

It's all about management of expectations. Disappoint early and often then they won't be so shocked at the end.

You're on fire today !

[expat]

Try the NuLabour methodology Stop aiming to build something to some predefined level of utility or quality and just aim to spend a shedload of money. Guaranteed success and BOOMED for contractors.

Don't just take the client's request, but define the targets yourself. Then define the measurement of the targets. Then measure your performance against your targets by your metrics, and announce that targets have been met so the project is a success.

Not invented by New Labour, already well-developed by Accenture.

[Mich the Tester]

Don't just take the client's request, but define the targets yourself. Then define the measurement of the targets. Then measure your performance against your targets by your metrics, and announce that targets have been met so the project is a success.

Not invented by New Labour, already well-developed by Accenture.

Go on! Be a Tiger!

[PM-Junkie]

Don't just take the client's request, but define the targets yourself. Then define the measurement of the targets. Then measure your performance against your targets by your metrics, and announce that targets have been met so the project is a success.

Not invented by New Labour, already well-developed by Accenture.

aka "ready, fire, aim"