@airwhale@christianhujer If all roles are involved from the early stage, starting with the discovery the likelihood of surprises should be low. Having different perspectives helps to understand the problem. It also helps to build empathy towards users‘ issue.
I believe the stories should be created in collaboration, instead of being thrown through the fence by the PM. Worth mentioning: #productmanagement is responsible for the WHAT and engineering for the HOW.
Just agreeing with Christian that we should have some identification of the actual business value being delivered, as expressed by the requestor or PM, in each User Story.
Add comment