"Lean replaces traditional user stories that can be declared “done” by a product owner with User Hypotheses that can be validated or invalidated. In other words, a feature isn’t finished when it’s shipped to a user." A feature isn't finished "until the feature has been used by customers and the results on key metrics have been measured. And even then, the feature isn’t really “finished.” It’s just ready for its next iteration."
However, we will use the term User Story to mean the agile concept of user story enriched with all its associated Lean UX artifacts and workflow process elements, and we call this a (structured) user story, as detailed in #6 (User Story Template).
The ProcessWorkflow #4 shows a number of artifacts taken from Gothelf:
Problem Statements
Assumptions
Hypothesis Statements
Personas
User Story
Wireframe
Living Style Guide
Instead of including these as separate issues in the backlog of a given milestone, which would lead to an excessive degree of atomization and unnecessary complexity, we will include them as part of the structure of a given User Story, with the possible exception of re-usable Personas, as references, of multiple Wireframes, as well as GitHub Flavored Markdown Task Lists, which appear as of GitHub Issues 2.
At the same time, all User Stories are recursive MVP's in themselves, so before using #6 User Story Template, be sure to familiarize yourself with #15 MVP Planning Guide first.
References:
Klein says:
"Lean replaces traditional user stories that can be declared “done” by a product owner with User Hypotheses that can be validated or invalidated. In other words, a feature isn’t finished when it’s shipped to a user." A feature isn't finished "until the feature has been used by customers and the results on key metrics have been measured. And even then, the feature isn’t really “finished.” It’s just ready for its next iteration."
However, we will use the term User Story to mean the agile concept of user story enriched with all its associated Lean UX artifacts and workflow process elements, and we call this a (structured) user story, as detailed in #6 (User Story Template).
The ProcessWorkflow #4 shows a number of artifacts taken from Gothelf:
Instead of including these as separate issues in the backlog of a given milestone, which would lead to an excessive degree of atomization and unnecessary complexity, we will include them as part of the structure of a given User Story, with the possible exception of re-usable Personas, as references, of multiple Wireframes, as well as GitHub Flavored Markdown Task Lists, which appear as of GitHub Issues 2.
At the same time, all User Stories are recursive MVP's in themselves, so before using #6 User Story Template, be sure to familiarize yourself with #15 MVP Planning Guide first.