34849How to write Stories for backend components?
- Dec 1, 2008I'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 (http://www.infoq.com/articles/scaling-lean-agile-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.
Recent Entries: Agile/Scrum Smells: http://www.notesfromatooluser.com/2008/06/agilescrum-smells.html
Agile Games for Making Retrospectives Interesting: http://www.notesfromatooluser.com/2008/10/agile-games-for-making-retrospectives-interesting.html
- Next post in topic >>