Background: Software development processes and techniques are used in a development context; controlled experiments typically trade less realistic contexts for repeatability. This paper describes an alterative method which includes a realistic context in a quasi-experiment.Objective: To understand how software development processes behave in context we have conducted a series of experiments primarily comparing extreme programming and plan driven approaches. Method: A quasi experiment was used that utilised a randomised complete block design [1] with a pre-test. Over the period of six years there were 20 blocks (projects) and 74 subjects (teams) assigned to the blocks. In total there were 322 students studied.Results: The experimental approach only uncovers small differences between the teams using different treatments. This is related to the variance in tasks undertaken and the fidelity to which the treatment is applied. Conclusion: This type of experiment can help to assess the generalizability of a technique by observing how it is used in the field. Due to the variations fidelity it is not an appropriate method to check the definitive benefits of a technique when there are no other pressures. Example: A team of 6 six students use Extreme Programming techniques to develop a software product in PHP working with a client. The client knows that he wants a document management system, with several classes of users but the team must help him identify his remaining needs.