Transitioning a Team to Agile Test Methods
Susan D. Shaye
Abstract
Susan D. Shaye
Abstract
This experience report describes the challenges and initial steps taken to move a large development team from traditional waterfall test phases to agile test methods. In late 2007, our development team started the transition to incorporate agile practices of user stories, daily scrums and time-boxed iterations. This paper focuses on the changes in test strategies necessary to support agile.
OpenAlex reports 14 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This experience report describes the challenges and initial steps taken to move a large development team from traditional waterfall test phases to agile test methods. In late 2007, our development team started the transition to incorporate agile practices of user stories, daily scrums and time-boxed iterations. This paper focuses on the changes in test strategies necessary to support agile.
Key concepts: Agile software development, Waterfall, Agile usability engineering, Waterfall model, Test (biology), Agile Unified Process, Scrum, Lean software development