This month on the Cucumber Podcast, Matt Wynne and Seb Rose speak to Chris Glover, a lead test engineer who has been working in a team which has struggled with some of the common pitfalls of learning BDD. Matt invited him onto the podcast to share that story.
This month on the Cucumber Podcast, Seb Rose and Matt Wynne speak to George Dinwiddie, an old friend of the pod and author of a new book "Software Estimation without Guessing".
Next week the BDD community will gather remotely for Cukenfest. This intimate event will inform you about the latest developments and thinking in high-performing BDD teams as well as being a space for you to share your own experiences with like-minded people.
In the build-up to the conference, we spoke to Abby Bangser about what people can expect from her opening keynote, her thoughts on the demands on effective testing and agile ceremonies in remote teams.
Soon the BDD community will gather remotely for Cukenfest, a two-day meeting of the BDD community in which we will hear stories about how we can become better software professionals and stronger teams. It'll also be your opportunity to share your own experiences practising software with peers taking a similar journey.
On of our keynotes this year, Emily Bache, took some time out to speak to us about Approval Testing, the development and ideas in her blog, and her thoughts on how software teams might operate post COVID-19. You can learn more about the conference and Emily's keynote on the CukenFest website.
In the build-up to Cukenfest, we spoke to Rebecca Wirfs-Brock who will give the closing address. We asked Rebecca a few questions about her upcoming keynote and how she came to discover these ideas and become one of the world's most prominent figures in this space.
This month on the Cucumber Podcast, we welcome Diana Larsen, a world-renown author, speaker and co-founder of The Agile Fluency Model.
This is the third in a series of articles digging into user stories, what they're used for, and how they interact with a BDD approach to software development. You could say that this is a story about user stories. And like every good story, there's a beginning, a middle, and an end. This post is a continuation of the middle.
This is the second in a series of articles digging into user stories, what they're used for, and how they interact with a BDD approach to software development. You could say that this is a story about user stories. And like every good story, there's a beginning, a middle, and an end. Welcome to the middle!
This is the first in a series of articles that will take a look at user stories, what they're used for, and how they interact with a BDD approach to software development. You could say that this is a story about user stories. And like every other story, it's important to choose where to begin – because, contrary to the advice given in the Sound of Music, it's not always a good idea to "start at the very beginning".
There are lots of names for the conversations we have to prepare user stories for development. Some people hold Three Amigos or Specification Workshops, some hold Planning Poker or Backlog Grooming sessions. Whatever you call this work, essentially you're trying to answer two questions:
These two questions form a dynamic: when a clearly-defined requirement turns out to be complex to build, developers and product owners can usually negotiate to find a simpler what that has a more straightforward how. Similarly, product owners may not be able to clearly define what they want until they've had a chance to have it examined by the people who will think about how to build it.
I recently watched a team having what they called a Sprint Planning meeting. For this team, that meeting was their opportunity to have this conversation. As they laid out the stories for discussion--each on 5"x3" index cards--I came up with a suggestion.