Doing Scrum, Being Agile › Story writing and getting ready for implementation
The purpose of a User Story is to help the Product Owner explain why the feature is needed and whether it should be implemented. Assuming the answer is yes, the team to understand who needs it, why they need it, and how to tell whether they have a good implementation. And stories going in the Sprint need to be small, so the team can get them finished quickly.
This month we’ll work through the challenges of getting backlog items ready for implementation. We last looked at this topic a year ago. Have you gotten better at it? What new challenges have arisen?
Here is my reading list for getting for next week, all drawn from Mark Levison’s Agile Pain Relief Guide to Agile Resources.
Vision and Visioning Tools
See you there!
You must be logged in to reply to this topic.