search

ryanlevell / books

MIT License
0 stars 0 forks source link

Discovery: Explore behaviour using examples (100%) #1

Closed ryanlevell closed 2 years ago

github-actions[bot] commented 2 years ago

Congrats on starting Discovery by Gáspár Nagy, I hope you enjoy it! It has an average of unknown/5 stars and 0 ratings on Google Books.

Book details (JSON) ```json { "title": "Discovery", "authors": [ "Gáspár Nagy" ], "publishedDate": "2018-02-07", "description": "Written by the creator of SpecFlow and the author of The Cucumber for Java Book, this book provides inside information on how to get the most out of the discovery phase of Behaviour Driven Development (BDD). This practical guide demonstrates good collaboration techniques, illustrated by concrete examples. This book is written for everyone involved in the specification and delivery of software (including product owners, business analysts, developers, and testers). The book starts by explaining the reasons BDD exists in the first place and describes techniques for getting the most out of collaboration between business and delivery team members. This is the first in the BDD Books series that will guide you through the entire development process, including specific technical practices needed to successfully drive development using collaboratively-authored specifications and living documentation.", "image": "http://books.google.com/books/content?id=FwLGswEACAAJ&printsec=frontcover&img=1&zoom=1&source=gbs_api", "language": "en", "pageCount": 100, "isbn10": "1983591254", "isbn13": "9781983591259", "googleBooks": { "id": "FwLGswEACAAJ", "preview": "http://books.google.com/books?id=FwLGswEACAAJ&dq=intitle:Discovery:+Explore+behaviour+using+examples&hl=&cd=1&source=gbs_api", "info": "http://books.google.com/books?id=FwLGswEACAAJ&dq=intitle:Discovery:+Explore+behaviour+using+examples&hl=&source=gbs_api", "canonical": "https://books.google.com/books/about/Discovery.html?hl=&id=FwLGswEACAAJ" } } ```
I couldn't find details about this book using the Google Books API. Don't worry, you can still track it. When you're finished with reading this book, just close this issue and I'll mark it as completed. Best of luck! 👍
ryanlevell commented 2 years ago

I've reached page 45.

ryanlevell commented 2 years ago

In my current team, while running three amigos meetings, we need to use "red cards" i.e. when we don't know something write it down and continue.

Whenever a conversation like this is going round in circles, it’s because you don’t have enough information. Probably someone is missing from the conversation, or maybe you need to do some user research, or a spike. question [...] Instead of letting everyone share their opinion about what they think the outcome should be, simply capture the question and move on.

https://cucumber.io/blog/bdd/example-mapping-introduction/

ryanlevell commented 2 years ago

Examples don't replace rules (acceptance criteria). Product team begins with a rule, and the team explores their understanding by coming up with examples of the rule.

ryanlevell commented 2 years ago

An example should only illustrate a single rule. Two examples may appear similar and could technically be used interchangeably, but the wording should focus on only the rule under discussion.

ryanlevell commented 2 years ago

Our team often has to make up both the rules and examples. Should the rules be defined by product instead?

ryanlevell commented 2 years ago

Occasionally leave out a scenario or example to help ensure you have the right level of detail. If it is overlooked by product/analyst, work with them to get the level of detail they are interested in.

ryanlevell commented 2 years ago

TDD - Red/Green/Refactor: Write a failing test, write just enough code to get it passing, refactor the code as needed.

ryanlevell commented 2 years ago

My current team should begin adding tasks to stories, and ideally each task should relate to a single example, when practical.

ryanlevell commented 2 years ago

I've reached page 75.

ryanlevell commented 2 years ago

Our team breaks down stories using horizontal slicing. This book recommends vertical slicing so that all the "small tasks" required to get into a releasable state. Every story is also a work unit. Product can easily identify exactly how many scenarios are working based on the number of completed stories. Rather than saying "database work is done", which doesn't give the product team much insight.

github-actions[bot] commented 2 years ago

You completed this book in 14 hours, 8 minutes, 26 seconds, great job!