Forms and inputs in a user story
Hello everyone,
So the company I work at is adopting agile and I have some questions regarding writing user stories. So when writing a user story, there are so many low level requirements behind it. The dev team always request those low level requirements. So my question is if I have a user story "As an admin, I want to add a new customer so that the customer can access the system" Here should I specify the inputs? i.e. Customer Name, Customer Contact Number, Package, Customer phone number. The developers need that information with the validation and wireframes in order to start implementing. Is this agile?
Can someone explain to me the confusion here?
Hi Meshal,
From what I am understanding, it sounds like the information that the Dev team is asking for revolve around having the User Story in a "Ready-Ready" state - in other words, the minimum criteria needed to provide the Dev team with the information they need to turn the User Story into a working increment of a release.
Yes, this is agile and does embody the three pillars of Scrum (Transparency, Inspection, Adaptation). The minimum requirements the Dev team asks for in the User Story (input values, wireframes, validation, acceptance criteria) must be:
- transparent to the developers so they know the Product Owner's "ask"
- useful for inspection if the requirements were met, and
- adaptable enough to be negotiated between PO and Dev Team
This criteria can also constitute the Scrum Team's Definition of Done in as much as the User Story has been developed, tested and meets the criteria on the User Story. So if the User Story does not have this "Ready-Ready" criteria fulfilled, there is a high probability that it won't be "Done-Done" at the end of the Sprint.