Hello all!
I'm a new ScrumMaster for my client and I'm working with a team whose primary focus is on integration and support for other project teams. We are struggling with how to create meaningful user stories that encompass the work we do, since a large amount of it does not result in delivery of functionality or creation of artifacts.
My client's SDM encourages us to capture all of our work in user stories, but I'm not sure how to craft a story to represent what basically amount to "buckets" of time to support an environment or particular system. For example, I may be asked to reserve 15% of a resource's time for supporting an external system that integrates with the product.
Does anyone have examples of how to write a meaningful story for this purpose?
Briana,
As I understand, user stories are simply users' requirements (in somewhat organized form). From your description it seems that the user in this case is technical and the stories can be technical too. So just write as if you are filling your timesheet /worksheet. I think that should serve the purpose here. I understand that the story should ideally represent a logial flow or a functionality, however, in cases when you are working in small buckets of time, this is what you can do.
Looking forward to more opinions.
It would help to know a bit more detail about what your team actually does. In general, its not a good idea to try and force fit production support into user stories. That's not what Agile/Scrum is for.
Here is a related Modern Analsyt interview question that might help. If you have more specific questions let me know.
Should-user-stories-be-created-to-plan-for-system-maintenance-and-support.aspx
brought to you by enabling practitioners & organizations to achieve their goals using: