UAT – me, how do I do that?

The problem with C Image via WikipediaOTS purchases and traditional testing methods is just that.
Well, it’s just that the methods were designed for a world where teams of engineers spent months writing code and then began to stabilise it and introduce it slowly into the business environment until it was a stable release and a good match for the tightly defined requirements. At least that was the theory,

Contract negotiation and on we go

A shock for the project manager

In the last instalment we discussed the way in which a vendor had been chosen that near total disregard for the goals of the project in the course of making that decision. Now we will look at what happened after the decision was made.

Requirements gathering the first big mistake.

Many seasoned project managers will start off a project by sending out his business analysis team to carry out requirement gathering.
Sometimes this is the right thing to do, in particular you should do this when you have a successful proven process that you want to automate using IT. Requirement gathering then educates the IT people responsible for system design (the features) on what they need to achieve.

This is a different scenario