0 Comment

3 Apr I recently had the pleasure to attend Gojko Adzic’s “Specification by Example: From User Stories to Acceptance Test” training course taught. 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 . 7 Apr I recently had the pleasure to attend Gojko Adzic’s “Specification by Example: From User Stories to Acceptance Test” training course, taught by.

Author: Gajind Daizshura
Country: Niger
Language: English (Spanish)
Genre: Sex
Published (Last): 12 November 2004
Pages: 173
PDF File Size: 2.91 Mb
ePub File Size: 16.43 Mb
ISBN: 782-3-50944-238-5
Downloads: 47874
Price: Free* [*Free Regsitration Required]
Uploader: Gutaur

Creating a shared understanding of the overall goal is the most important part of specifying a problem, and one that developers hide away from spedification their peril. Must-read for everyone interested on modern software development.

These are two typical situations in larger organizations. Chapter 8 Refining the specification 8. Return to Book Page. Book Description Specification by Example is a must read for anyone serious about delivering software that matters. Adzic recommends specifying collaborativelyand describes practices ranging from all-team workshops where the team is new to SbEto pair-writing and informal conversations for mature teams or those with easy access to domain experts.

In it, author Gojko Adzic shares the secrets of how teams all over the world specify, develop, test, and deliver the right software, without defects, in very short iterative delivery cycles.

This book examines the development process beginning at the point of deriving scope from goalsand ending with validating frequently and evolving a living documentation system. Opinions expressed by DZone contributors are their own.

More stuff

Jul 03, Ronald rated it liked it Shelves: Paperbackpages. Enjoyed this overview of a testing methodology that brings in BDD principles to automated software testing environments.

The first one was Bridging the Communication Gap: Chapter 4 Initiating the changes 4. Specifying collaboratively Chapter 7. Based on dozens of interviews with successful teams worldwide, this brilliantly rich and informative book will change the way software developers work. Illustrating using examples Chapter 8. My goals for the course were as follows: Gojko Adzic has changed that by structuri Often I wish I could say about some aspect of software development, literally, “let’s do this by the book”.


About the Technology Specification by Example is a collaborative method for specifying requirements and tests.

All in all is good book and worth reading it, even if you are in the middle of methodology change like me. This book helps readers understand how successful teams bridge the communication gap between stakeholders and development teams by implementing specification by example, agile acceptance testing, and behavior driven development.

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 deliver software in short, iterative delivery cycles. It is common to get specifications that include lines of code.

But it started be more interesting from the chapter 4. Stay ahead with the world’s most comprehensive technology and business learning platform. 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. I learnt from Metaphors We Live By that people think primarily in terms of prototypes, rather than in abstract categories, and so the idea of specifying by example seems inherently congruent to how we model the world.

All this on teams where they already have started or reaching a mature Agile software development process. The book explains to the reader, other team experiences applying BDD. To adapt the ideas of the book in your project is therefore not so specificatin.

Functional requirements, specs, and acceptance tests are the same thing.

PART 1 Getting Started

From that you, should be able to get some ideas on what might apply to your current project. On the other hand, maintaining a system without any documentation also causes headaches. Some of this book was interesting, some of it was not so much.


See the original article here. Here is what I learned.

All in all, there are very good ideas and practices presented many of them are still ahead of their timealbeit in somewhat preaching mode. About the cover illustration. The first 3 chapters were rough to get through, they seemed to discuss this at such a high level in such vague language that I didn’t really get a grasp of where it was all going.

One a suitable specification is prepared with its examples, the challenge becomes to automate its validation. Giulia joined Codurance driven by the desire to apply the Software Craftsmanship mindset and values to the whole product and service design process.

About the author A UK based consultant, Gojko Adzic helps teams worldwide implement Specification by Example and agile testing practices. She is a Certified Scrum Master and Certified Scrum Product Owner with a strong focus on the present and the future of a product, backed up by her Integrated Design background and the mastery of User Experience Design skills. Giulia has worked as a design consultant and art director in an integrated communications agency for more than ten years, developing both the design talent and business knowledge necessary for creating meaningful holistic brand experiences.

Gojko Adzic – Specification By Example on Vimeo

Validating frequently Chapter With Safari, you learn the way you learn best. Choosing a collaboration model. We learned how to discover the right questions to ask by collaboratively visualizing a team’s and the stakeholders’ understanding through real examples. Creating documentation from executable specifications. This is important as it helps to actually start the conversation.

Having read his brilliant books: Different teams use different techniques. Living documentation should be consistent.