Summary:
Agile development methodologies (in our case, Scrum) often assume that the customer and developers work together so closely that there is no need for a functional analyst or tester to be present on the team. In real life, our customer does not always know what he wants, so you do need an analyst; and our developer occasionally makes a mistake, so you do need a tester. This document explains how you can fit "functional testing" into the Scrum methodology without too much overhead or deviation from the basic principles of Scrum. This method was successfully tested in at least two projects.
