Best Use of Themes, Epics and User Stories

Moderator: kwalford

New Member
New Member
Posts: 2
Joined: Wed 01 Apr 2015 3:50 pm

Best Use of Themes, Epics and User Stories

Postby lilbird1981 » Wed 18 Nov 2015 9:57 am

Hi All,

I am just doing some project management training for agile, and I am wondering how I would structure requirements for the following:

I am managing a multinational project for company A. Company A is implementing a new software for countries 1, 2 and 3. The requirements for each country are slightly different. Where would you split the country? Would you have 1 theme or epic per country?

For example:
All countries have stock management. Country 1 wants an automated stock management system which resends articles once the stock has reached a certain number.

Country 2 wants a manual stock management system, i.e. the technician has to order stock when they think they need more.

Country 3 has an even more complex system, which orders stock based on the historic demand of items in the area.

What would be the best way to structure these requirements?
I would say that stock management is the theme, but what would be the epic, and where would I indicate the country? Do you think I should just say in the user story that As a Country 1 user, I want the system to automatically send new articles once my stock reaches x so that I always have stock.

Thanks for your advice.

Who is online

Users browsing this forum: No registered users and 2 guests