New feature, existing screen
A product owner plans a new feature. The map shows that no new interface is needed, and writes the user story with acceptance criteria.
Transcript
A product owner is planning a new feature: customers should see the invoice number on their own order. Before release, the question is whether it needs a new interface. We ask as an analyst.
Acting as an agent, the chat goes through the map, checks the screen and the query behind it, and a few seconds later the answer is there: it doesn't. The data is there, the order query already returns it, the screen just doesn't show it. There is even a pattern for it, in the provider interface.
We follow up: write a user story from it that the development team can pick up right away. Done, with acceptance criteria, and a source behind every claim. Until now, this would have meant asking a developer.
