We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
Published online by Cambridge University Press: 26 October 2009
SYNOPSIS
In a fast-moving environment where requirements are changing all the time, in order to support the customer's needs, the testing strategy has to be superagile. How do you keep the relevant documentation up to date? How do you communicate the changes to your team? How do you ensure your testing covers the changes? How can you guarantee that you deliver a system that works and meets the customer's needs?
This case study reviews the issues that are being faced by a large, multiyear project practicing incremental delivery, and shows how the team has used agile techniques to address these issues. In particular we will look at how using techniques such as daily builds, pairing testers and developers through an iteration, and the use of automated testing tools for regression testing have enabled the team to successfully test and deliver a new, high-quality release every six weeks!
Introduction
My name is Nick Sewell and I work for Ivar Jacobson Consulting Ltd. as the European Managing Director. I have over twenty years' commercial experience in the software industry – twelve of these ensuring that software teams deliver software successfully using a range of techniques.
In a fast-moving customer environment where requirements are changing all the time to support the user needs, the testing strategy has to be superagile.
For example, I have recently been working as a part of a team enhancing a large business critical information system that needs to be updated every six weeks to keep pace with an ever-changing variety of information sources and analytical needs.
To save this book to your Kindle, first ensure no-reply@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.
Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.
Find out more about the Kindle Personal Document Service.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.
