How do you organize the technical aspects of your work? Do you create technical stories or technical user stories alongside your user stories? If so, we suspect that you are probably accumulating some problems.

In this episode, Dave Farley, author of Continuous Delivery and Modern Software Engineering, talks about technical stories and the use of technical stories versus user stories. He also describes why he thinks technical stories are not a useful way to talk about and plan our work. In software development, the way we plan, organize, and prioritize our work has a big impact on its quality. This episode explores why that is and how to do it better.

—————————————————————————————————

NEW COURSES for acceptance testing:

Check out my collection of 3 courses on ATDD. Learn a BDD approach to acceptance testing: analyze problems in a way that helps determine what product features to develop, learn to write better stories and specifications, reduce reliance on manual testing, and build better, results-oriented software for your users.

YOU CAN FIND THE LIST OF 3 COURSES HERE ️ https://courses.cd.training/pages/about-atdd

—————————————————————————————————

PATREON:

Join the Continuous Delivery community and get access to additional perks and content! If you join by the end of October, you'll be entered into a book giveaway to win a free copy of Dave's latest book, Modern Software Engineering.

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.