Can User Stories Be Technical?
A Technical User Story Is One Focused on Non-Functional Support of a System. for Example, Implementing Back-End Tables to Support a New Function, or Extending...
A Technical User Story is one focused on non-functional support of a system. For example, implementing back-end tables to support a new function, or extending an existing service layer. Sometimes they are focused on classic non-functional stories, for example: security, performance, or scalability related.
How do you convert user stories to technical tasks?
- Create Meaningful tasks. Describe the tasks in such a way that they convey the actual intent. ...
- Use the Definition of Done as a checklist. ...
- Create tasks that are right sized. ...
- Avoid explicitly outlining a unit testing task. ...
- Keep your tasks small.
Why technical user stories are bad?
Technical user stories are bad because they defeat the fundamental purpose of a user story. Which is to describe the desired behaviour from a user point of view. And to ensure that the value (for some person) is captured. Nobody gets value from an API talking to a database through an object-relational mapper.
James Sterling reports on renewable energy developments, climate policy, ecological conservation, and green tech innovations around the globe.
