How does product and engineering execute user stories?
1 comments
I don't understand why "title"s are so partitioning?
Obviously, the PO is accountable for the user stories, but they are not to write them all by themselves.
Let the PO decide what is the next big feature, then pair them with a dev to split into manageable stories. Such stories will be then smaller and still have to be split in task. But at least, the user story will be small enough to be develop as is.
PO will have the last word about the big picture and the details (user facing) but the means are in dev hands.
Obviously, the PO is accountable for the user stories, but they are not to write them all by themselves.
Let the PO decide what is the next big feature, then pair them with a dev to split into manageable stories. Such stories will be then smaller and still have to be split in task. But at least, the user story will be small enough to be develop as is.
PO will have the last word about the big picture and the details (user facing) but the means are in dev hands.
The way we do it now is product write epics and user stories. These stories contain the business problem, the acceptance criteria, design, etc. The problem is these stories are usually not small enough for an engineer to work on in a sprint so they need to be broken down. To break them down, engineering creates our own story and links it to the product story so we can point these broken down engineering stories so we can measure velocity. The engineering stories are light weight with little technical details since the title is usually self explanatory.
How does everyone else do it? I feel like i'm always battling how to manage execution of product and engineering, especially in a startup environment.