From the experience of leading teams worldwide, author Gojko Adzic distills seven key patterns and many practical rules for effective ways to specify, test, and . I recently had the pleasure to attend Gojko Adzic’s “Specification by Example: From User Stories to Acceptance Test” training course taught. Do you want to improve customer engagement and business involvement within your organization? Click here for more info!.
|Published (Last):||17 January 2015|
|PDF File Size:||14.98 Mb|
|ePub File Size:||17.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
Get unlimited access to videos, live online training, learning paths, books, tutorials, and more. Read more Read less.
Must-read for everyone interested on modern software development. Iowa Student Loan Chapter Sabre Airline Solutions Chapter The team extends the tests while at the same time implementing the code, writing the documentation, updating the design description, and so forth. In this book, author Gojko Adzic distills interviews with successful teams specifivation, sharing how they specify, develop, specufication deliver software, without defects, in short iterative delivery specificaion.
It is definitely a book for a more than one read, mainly because it exposes different scenarios and tips on how other teams have resolved them; so you’ll probably need to go back to them in the future.
PART 1 Getting Started
Chapter 8 Refining the specification 8. Chapter 9 Automating validation without changing specifications 9. For additional resources go to specificationbyexample. This might lead to new requirements or a change in the existing tests. Chapter 4 Initiating the changes 4. Initiating the changes Part 2. This was just the lever that I needed to secification the client to make the change.
Specification by Example by Gojko Adzic
In fact, his course is a 2-day hands-on experience which is a very effective way to show what you can get by Specification By Example SBE and when to use it. But it started be more interesting from the chapter 4.
The heart is the “three amigos workshop”, something that deserve an emphasis on, but shortly addressed.
Why we need authoritative documentation. Chapter 11 Evolving a documentation system We build well-crafted software for our clients, we help developers to get better at their craft through training, coaching and mentoring, and we help companies get better at delivering software.
Identify modelling problems how you name key concepts in your domain and solve them by building up a common language Ubiquitous Language. Develop —At the end of the workshop, the examples are distilled into tests and all activities needed to implement the requirement are done concurrently. Specifidation book was very dry though. Some requirements are just better expressed in a workflow multi-step scenario example. Specification by Example and Agile Acceptance Testing and talked about the author personal experience in this subject.
Living documentation should be organized for easy access. That said, there were some interesting ideas in the book that I liked. The method has four main benefits: My goals for the course were as follows: The whiteboard sketches are captured with photos.
It’s good to defend the concept to the development team. Cucumber but not be focused on tool itself. Given the acceptance criteria, ask people to write down the simplest possible examples of what we want to test.
Starting to change the process. Here are few guidelines to follow:. Two-week iterations are fast and therefore the team needs to conceive a way to work concurrently—sequential development in a short iteration does not work. My hope is that Specification by Example can be a template to improve this, and reduce one of the biggest sources of routine waste in current software development.