Gojko Adzic
Specification by Example
September 10, 2019 Comments.. 971
Specification by Example Gojko Adzic Summary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in shSummary Specification by Example is an emerging practice for creating software based on realistic examples, bridging the communication gap between business stakeholders and the dev teams building the software In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles.About the Technology Specification by Example is a collaborative method for specifying requirements and tests Seven patterns, fully explored in this book, are key to making the method effective The method has four main benefits it produces living, reliable documentation it defines expectations clearly and makes validation efficient it reduces rework and, above all, it assures delivery teams and business stakeholders that the software that s built is right for its purpose.About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban.This book is written for developers, testers, analysts, and business people working together to build great software.Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning Also available is all code from the book.What s InsideCommon process patterns How to avoid bad practices Fitting SBE in your process 50 case studies For additional resources go to specificationbyexample.. Specification by Example Summary Specification by Example is an emerging practice for creating software based on realistic examples bridging the communication gap between business stakeholders and the dev teams building the
  • Title: Specification by Example
  • Author: Gojko Adzic
  • ISBN: 9781617290084
  • Page: 488
  • Format: Paperback
  • Specification by Example Gojko Adzic

    • BEST KINDLE "✓ Specification by Example" || UNLIMITED (KINDLE) ☆
      488 Gojko Adzic
    • thumbnail Title: BEST KINDLE "✓ Specification by Example" || UNLIMITED (KINDLE) ☆
      Posted by:Gojko Adzic
      Published :2019-09-10T22:24:57+00:00

    1 Blog on “Specification by Example

    1. Stijn says:

      The book offers some very good ideas and is an interesting read, but too me it s too repetitive You keep reading the same arguments and explanations over and over again, without going into concrete examples It would have helped if the book contained a full blown actual example of the artifacts that are produced by SBE, and not just describing what the process is.

    2. André Heijstek says:

      The majority of the book is just an expansion of the praise pages typically found in USA books.Never the book become concrete on HOW to create good test specifications.

    3. Torben Rahbek Koch says:

      Awesome

    4. Lance Willett says:

      Enjoyed this overview of a testing methodology that brings in BDD principles to automated software testing environments It s a bit too complex for my needs, yet I love the idea of capturing everyone s opinion in specification business owners, testers, developers, analysts as well as the philosophy of living documentation.Two favorite bits 1 Functional requirements, specs, and acceptance tests are the same thing.2 Don t just disable failing tests either fix the problem or move to a set of low pri [...]

    5. Luboš says:

      I was about to not finish the book at all because it the introduction was to talkative But it started be interesting from the chapter 4 The main message I took is to use behavior driven development BDD e.g Cucumber but not be focused on tool itself I would appreciate examples of specification by example, which are not there.

    6. Andy says:

      I like the concepts in this book about having a living documentation system through testing There are real world, high level case studies, but I would like to have seen examples of actual tests and tools.

    7. Paul Childs says:

      Some of this book was interesting, some of it was not so much 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.Adzic interviewed a bunch of people from various companies that use Specification by Example and the book basically describes practices that these people used Not all the companies did Specification by Example the same way, so while you are getting a bunch of [...]

    8. Gali Valiente says:

      Too many software projects go to waste, exceed budgets and overshoot schedules simply because project teams do not take specific steps to understand the true business need of the client If you are still not satisfied with your existing methods on how to best understand what your client truly requires and deliver your project to the clients satisfaction then this book gives you specific take aways on how to do it Highly recommended read for those who manage software development projects, business [...]

    9. Nikolay says:

      I have mixed feeling about the book I almost gave up to read it after first few chapters because it was too abstracted and ambiguous Then I liked Part 2 of this book, but by the end of this part it started to be too technical for me probably because I m business analyst, not auto tester Nevertheless I got some useful information from the book and do not regret that I ve spent some time on it e.g now I have an idea what BDD is about and also some advises from this book very useful e.g QUPER appro [...]

    10. Gabor Hajba says:

      Although this book is a bit old, I think the concepts are still valid and software projects can still benefit from Specification by Example.I never used this approach but I am thinking about it in a future project if I can convince the stakeholders and fellow workers development, test, business analysis or I just go renegade and implement it all alone.

    11. Daniel Assis Alfenas says:

      Must read for everyone interested on modern software development Sets the ground and basics for every good test practice.

    12. Fred Esere says:

      Some practical, helpful actionable items in this book Didn t need to be as long as it was.

    13. Vladimir Kotov says:

      Have read few first chapters Expressed ideas are great by for me it was too abstracted.

    14. Bárbara Cabral da conceição says:

      It s good to defend the concept to the development team.

    15. Robert Batůšek says:

      The book has a long and rather boring start but there are some interesting thoughts Later chapters are much better.

    16. Ash Moran says:

      Often I wish I could say about some aspect of software development, literally, let s do this by the book Only then do I realise there is no book It s like realising there is no spoon, except the problem can be solved by an experienced software developer, rather than the saviour of mankind Until now, the process of capturing, formalising, and validating the high level specification of software has been one of these inconsistently documented problems Gojko Adzic has changed that by structuring man [...]

    17. Ronald says:

      I m currently trying to better understand the BDD mind set and how it might improve things on my current project so I was really excited when Specification by Example showed up in my Kindle I was looking forward to finding a whole check list of dos and don ts to help accelerate me to BDD nirvana Instead, I learned that implementation of SBE is very contextual one size does not fit all Different teams use different techniques The author interviewed several teams using SBE and discovered what work [...]

    18. Karl Metivier says:

      Gojko bring us another book about specifications The first one was Bridging the Communication Gap Specification by Example and Agile Acceptance Testing and talked about the author personal experience in this subject This time, we see other people s experiences with the using of Specification by Example In addition to that, we see how Gojko has evolved his thinking about specification and after a few chapters, we go beyond the basics.By the way, this book doesn t talk about code or tools Just pri [...]

    19. Toni Tassani says:

      Some practical advice around BDD and ATDD using a different acronym SBE The case studies in the end are really interesting No tool is introduced but in the examples Concordion, FitNess and Cucumber are always there I missed practical examples.

    20. Brett says:

      According to Dan North, if you need a book on BDD, this is the book to read In fact, Dan has said that he did not write a book because this one captures the essence of what he was trying to get across.This book is based on actually talking with real projects and gives examples of what has and had not worked on projects for writing Executable Specifications This contains a wealth of information on things to avoid based on what has has not worked for other teams On the other hand, when you read th [...]

    21. Deniss Ojastu says:

      A book on how to create and deliver software which is a quality b what is needed c not than needed One way to achieve that is needs and requirements specification together with clients In addition, using different examples illustrating what software is supposed to do.Capturing needs, not scripts that is probably one of the most important messages from the book.All in all, there are very good ideas and practices presented many of them are still ahead of their time , albeit in somewhat preaching [...]

    22. Torben says:

      Gojko Adzik has managed to lay out practices in the area of test driven acceptance testing, autmated testing and documentation This certainly feels like testing done right and describes a collaborative approach to specification, testing and documentation focused on automation The key practices introduced are Deriving scope from goals Specifying collaboratively Illustrating using example Refining the specification Automating without changing the specification Validating frequently Evolving a docu [...]

    23. Helene says:

      This book was an excellent description of how to develop and maintain good software He does a great job explaining how product, development and testing can get on the same page Every stage in the process is illustrated with stories of successful and unsuccessful teams and what teams learned going forward The footnotes and references at the end are very helpful for people like me that want background Because I do not have a working knowledge of Cucumber and FitNesse, I had difficulty visualizing [...]

    24. Johnny Graber says:

      The book is all about using examples to specify a software product and not an example of a specification This distinction is important and should be considered before buying this book The book explains in great detail how example cases and scenarios can help you better understand the purpose and ideas behind a complex system It will give you plenty of ideas and many things to think about What you will not find is code To adapt the ideas of the book in your project is therefore not so simple The [...]

    25. Eduardo says:

      It is definitely a book for a 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 All this on teams where they already have started or reaching a mature Agile software development process.This set up makes for a complex read since there are lots of related data and not all of them are clear at the beginning.All in all is good book and worth reading it, even if you are in the middle [...]

    26. Pavleras says:

      my interest has been risen progressively I didn t have any expectation and I ve changed my opinion The framework proposed to apply BDD is very understandable and easy to follow This book focuses on how to increase collaboration, how to modify your development process The book explains to the reader, other team experiences applying BDD I miss a detailed explanation about how to make the tests but the book would be probably much longer.

    27. Rick Austin says:

      Great introduction to the concept of specification by example This is not a technical book and will not teach you how to implement but it does provide a deep overview of specification by example Extensive interviews with a number of companies provide real world examples of how this works and the benefits gained by each Very open about mistakes made by some teams which was very helpful.Great read that now has me wanting to learn about how to implement these practices.

    28. Sebastian Gebski says:

      Deep analysis of ATDD Acceptance Test Driven Development , enriched with several real life cases Detailed and precise sometimes even a bit too much, what made it dull at some points I leaned towards 4 stars, but this book answers a lot of questions about user acceptance and specifications in agile methods the questions other are usually afraid to address That s why it s 5 stars after all.

    29. Bjoern Rochel says:

      I really like the case studies used throughout the book I had hoped that the book would go into detail, but nevertheless It left me with a lot of ideas of how to improve what we re doing in my current team.

    30. Daniel Temme says:

      Really nice book Especially liked the different context of the different projects experiences.At times I might have wished for some technical examples but the RSpec book seems to be a good companion book for that.

    Leave a Reply

    Your email address will not be published. Required fields are marked *