Skip to main content

How do I structure my requirements

Last post 07:14 am December 7, 2015 by Sanjay Saini
3 replies
08:45 am November 18, 2015

Hello,

I am just learning the concepts of Scrum and I am currently working on the following scenario.

We have a multinational company called WeStock. They work in Belgium, Netherlands and Germany and amongst other things, they do stock management.

I have the following requirements:

As a Belgium User I want the system to automatically restock my system when the stock level has reached 10, so that I always have enough stock in my van.

As a Netherlands User I want to be able to request new stock as needed, so that I always have enough stock in my van depending on demand.

As a Germany User I want to be able to set my maximum stock level, and items will always be restocked up to that level, so that I can always handle big projects instantly.

I have made these requirements up myself, so they might not be detailed enough etc, but my question is, how would I structure this into user stories? My main question here is, should I distinguish the user stories explicitly by country, or should I just mention the country in the user story.

So, my initial thought was:

Epic: Country
Theme: Stock Management
User Story: Specific Requirements

Does this make sense? Can a user story be part of more than one epic? Because of course, a user story might be valid for both Belgium and Germany etc.

What would be the best way to structure these requirements?
Tia,
Lily


05:17 pm November 18, 2015

Lily,

Your three requirements refer to different behaviors of functionality, irrespective of the country value stated. It's up to you how you'd like to classify them, whether to differentiate your user stories by country, or simply have the user stories stand on their own.

Hopefully, you are developing and grooming these stories with a team and a product owner familiar with the functionality that has the most business value.


12:24 pm November 20, 2015

Why don’t you try this:

As a <WeStock User>, I can <define my preference of being restocked> so <I can adjust the Restocking mechanism to my business needs>

Criteria of acceptance:
1. I can define restocking based on a minimum stock level (BE)
2. I can define restocking based on a maximum stock level (DE)
3. I can redefine my minimum / maximum restocking level at anytime, as I see fit (NL)

===

Probably everyone wants option 3, even they guys from BE and DE


07:14 am December 7, 2015


I agree with Chris.

The only thing I would like to add is that if your team is not able to accommodate the complete story then you can cut it into three slices one for each country.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.