2024 update: This was my second post showing some of the concerns we had in 2008 at Locaweb and how we searched and tested possible solutions to address these concerns. Unfortunately, Mike Cohn’s references are not working, but the overall idea is clear: define the expected behavior of a new feature only when we decide to build it, not earlier.

==========================================================

I’ve just read a post in Danilo Sato’s blog about writing acceptance test right after a user story enters a sprint.

Browsing Mike Cohn’s site, we found two documents pointing to the same idea:

• slide 15 of Effective User Stories for Agile Requirements, and;
• page 21 of chapter 2, Writing Stories, from User Stories Applied.

We will test this approach and let you know the outcome.

Workshops, coaching, and advisory services

I’ve been helping companies and their leaders (CPOs, heads of product, CTOs, CEOs, tech founders, and heads of digital transformation) bridge the gap between business and technology through workshops, coaching, and advisory services on product management and digital transformation.

Digital Product Management Books

Do you work with digital products? Do you want to know more about managing a digital product to increase its chances of success, solve its user’s problems, and achieve the company objectives? Check out my Digital Product Management books, where I share what I learned during my 30+ years of experience in creating and managing digital products:

• Digital transformation and product culture: How to put technology at the center of your company’s strategy
• Leading Product Development: The art and science of managing product teams
• Product Management: How to increase the chances of success of your digital product
• Startup Guide: How startups and established companies can create profitable digital products