         Américo Sampaio 1 , Alexandre Vasconcelos 1 and Pedro R. Falcone Sampaio 2 1 Centro de informática, Universidade Federal de Pernambuco Recife, Pernambuco – Brazil {atfs, amlv}@cin.ufpe.br 2 Computation Department, University of Manchester Institute of Science and Technology Manchester, United Kingdom p.sampaio@co.umist.ac.uk  Delivering high quality web applications complying with severe project delivery time constraints is still an elusive goal for a software process. In many software projects, development teams often resort to "short cuts" in the software development process avoiding recommended software process disciplines to speed up delivery. The usual side-effects of this ad-hoc approach are low software quality and high maintenance costs. In this paper we empirically address the tension between quality and agility (speed) in web application development describing a set of software disciplines that were added to Extreme Programming to improve web software quality without sacrificing development agility.   Delivering high quality web applications complying with severe time constraints is a highly challenging dilemma within the software engineering community [20]. In many software projects, development teams often resort to “short cuts” to accelerate the development process, adopting ad-hoc approaches to build web applications [3,7]. In these situations the success of the project relies heavily on the skills and knowledge of the people in the software team, increasing the risk of potential negative side effects on usability, maintainability and robustness of the application. Therefore, it is highly important to have a more rigorous and organized approach to build high quality web applications while retaining agile properties in the development effort. A possible approach towards reconciling quality and speed can follow two converging directions: (1) start with a prescriptive software process such as Rational Unified Process [21] and evaluate how the gradual relaxation of disciplines under similar project development conditions affects quality and speed; or alternatively, (2) start with an agile software process and evaluate how the gradual incorporation of disciplines under similar project development conditions affects quality/speed. In this paper we adopt the latter approach by departing from an agile software process [1] and gradually incorporating quality related software disciplines. A