>User stories evolved over twenty years ago as a way to communicate what a customer wanted into product requirements that a software team could deliver. ... Cus

>User stories evolved over twenty years ago as a way to communicate what a customer wanted into product requirements that a software team could deliver. ... Customers are tech-savvy enough to articulate basic product requirements HA. Sure. 20 years ago Customers were dum-dums, but today Customers are tech-savvy. >issue should describe a task with a clear, defined outcome. The point of user-stories is that the implementing developer also has a brain and is able to contribute to the solution. So a user story is supposed to communicate the problem the customer is trying to solve so that the specific solution can be derived collaboratively. Nothing is worse than writing a task to turn a developer into an automaton.