34868Re: [scrumdevelopment] How to write Stories for backend components?
- Dec 1, 2008Mark,
Writing user stories to include a final user is somewhat a stretch,
mainly in very large projects with components talking to each other.
One solution I have implemented in such cases is to consider the system
itself as a user.
For example, let's say you have a search engine team and an analytics
team, each building their own product. Assume the search engine needs to
store data into the analytics library, which at some point will be used
by an end user through some existing dashboard system.
You could label your story "The analytics engine can store search
parameters"; you may include "SLAs, speed etc through your story
conditions of satisfaction".
In doing so, you want to make sure you don't transform all user stories
into technical stories, but it may give you some nice support for some
Some trainers even advocate to have a small percentage of stories in
each iteration where the system is the user (maybe 10%) so you can
handle some necessary refactoring withing begging to the product owner
(when this practice is not the de facto culture).
Mark Levison wrote:
> I'm sure this has been asked before - but after 20 minutes of digging
> I can't find the reference.
> One team team that I working with is building a backend component that
> suppports a number of other systems. I'm familiar with the idea that
> we shouldn't have component teams but rather feature teams
> However at the moment I can't help make that change, in addition the
> technology stack is deep enough that feature teams might not be enough.
> So my problem: How to write stories for backend components?
> In this case the product supports 4-5 other applications further up
> the stack than them (not all of which are end-user applications). So
> I'm wondering are stories written in the form:
> "The XXX application needs ..... for business reason*" or* do you find
> a way to write in terms of the actual end user even though this
> component doesn't work directly with end-users.
> Mark Levison
> Blog: http://www.notesfromatooluser.com/
> Recent Entries: Agile/Scrum Smells:
> Agile Games for Making Retrospectives Interesting:
- << Previous post in topic Next post in topic >>