For most software teams, both complexity and value correlate highly with new user-facing system behavior. So, if a team is going to incrementally reduce risk and incrementally build value—or better yet, front-load for risk-reduction and value—it makes sense to organize the work into increments of user-facing system behavior.
In this episode, Richard and Peter answer the question, “How do we know whether an item on our Product Backlog should be a User Story or a Task?” They also dig into the most sustainable way to approach functional test automation on a software team.
The Humanizing Work Guide to Splitting User Stories
BDD with Cucumber Book