Acceptance Testing

Code is not finished until the stakeholder representative agrees it is. This is accomplished by the user executing some form of acceptance test on all new software completed during an iteration to insure it conforms to the User Stories that define it. This would appear to slow down the development process by having engineering unable to move forward until the stakeholder accepts each new feature and function. It does, but this is a good thing. When development gets continual feedback on what they are developing they can better understand the product objectives and improve their own processes. Most importantly, they and the stakeholders can proceed with the comfort that they are developing the right thing.