Who writes detailed user stories in Scrum Team?
This question was raised by an experienced Agile/Scrum consultant, Kiran, in a group where I also have participated and concluded with following points:
1. Development team discovers details by working with
customers/users on a regularly basis. Having a middle person a PO or BA
does not help in a long run and it is not an efficient process. Overtime
PO or BA becomes a bottleneck and may leads to Silos within a scrum
team.
2. Who would benefit documenting details? That is really depends on organization requirements on documentation. Do you have maintenance team(s) who needs to support the product? Maybe they would require some documentation to help them production support. If you do have a production support teams, try to integrate them as part of your sprint process as much as possible. So, they can support it better and they know what’s coming their way. Do you need to follow any compliance in your organization depending on your industry? They will require some kind of documentation so ask them.
3. Detailed means – enough details for development team to continue developing a working product without wasting their time during the sprint. Detailed enough for customer/user to provide meaningful feedback and acceptance of the work without constant emotional discussion at the end of the sprint.
No comments:
Post a Comment