Set Clear Criteria for Acceptance Tests
Working from barely sufficient documentation, the team will need to know a few things before starting to build a feature. Rather than working from step-by-step requirements, Product Owners need to know
-
What are their criteria for acceptance?
-
How much detail do they need in order to engage in a conversation with developers?
And developers usually need to know a fair amount about what is to be built.
No one should try to automate conversations between the Product Owner and the developers, but we can automate the criteria for acceptance:
-
what it should do
-
when it’s working
-
and when we’re ready to move on
This allows developers to then focus on edge cases—on problems or situations that occur at extreme operating ...
Get Beyond Legacy Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
