Google TechTalks
February 9, 2006
Rick Mugridge
Rick Mugridge is the lead author of the first book on storytests: "Fit for Developing Software". He has developed and is evolving FitLibrary to better support storytest driven development. He is a leading thinker and inventor in this area, and consults and coaches internationally in storytesting, executable specifications, and agile software development.
ABSTRACT
We raise four software development issues and show how Fit can be used to address them. The issues are as follows: (1) How can we improve test coverage on a legacy system without discouraging its evolution? (2) Now that we have a successful product with a great UI, how do we provide program access, such as through SOAP? (3) How can QA be involved earlier and more effectively? (4) How can product managers better utilise their expertise?
Each of these issues can be addressed with Fit storytests. Storytests satisfy the demands of both requirements and quality assurance, in an amalgam that initially looks weird and counter-intuitive. Storytests are concrete examples that express important things about the business domain and about the system. They are matched and generalised in the code, using the same "ubiquitous language". Week by week, as thinking and understanding grow and change, the storytests grow and change. And so the code evolves.Google TechTalks
February 9, 2006
Rick Mugridge
Rick Mugridge is the lead author of the first book on storytests: "Fit for Developing...all »Google TechTalks
February 9, 2006
Rick Mugridge
Rick Mugridge is the lead author of the first book on storytests: "Fit for Developing Software". He has developed and is evolving FitLibrary to better support storytest driven development. He is a leading thinker and inventor in this area, and consults and coaches internationally in storytesting, executable specifications, and agile software development.
ABSTRACT
We raise four software development issues and show how Fit can be used to address them. The issues are as follows: (1) How can we improve test coverage on a legacy system without discouraging its evolution? (2) Now that we have a successful product with a great UI, how do we provide program access, such as through SOAP? (3) How can QA be involved earlier and more effectively? (4) How can product managers better utilise their expertise?
Each of these issues can be addressed with Fit storytests. Storytests satisfy the demands of both requirements and quality assurance, in an amalgam that initially looks weird and counter-intuitive. Storytests are concrete examples that express important things about the business domain and about the system. They are matched and generalised in the code, using the same "ubiquitous language". Week by week, as thinking and understanding grow and change, the storytests grow and change. And so the code evolves.«
Download is starting. Save file to your computer. If the download does not start automatically, right-click this link and choose "Save As". How to get videos onto the iPod or PSP.
