Skip to main content

How to formulate order/customer request?

Last post 04:51 am November 18, 2016 by Arasi Mu
2 replies
01:55 pm November 17, 2016

Hi,

I'm working as a Scrum Master in a project at a very big place, over 20000+ employees. My biggest issue here is to implement scrum as it should. But with the hierarchy, policies and all deadlines they have here, it's impossible.

Making a long story short, we have issues with how the clients should formulate their "order/customer requests". So my question is, how should they formulate what they want with a good description and acceptance criterias? Are there any templates that we can use?

This is the first step before the scrum team takes over and creates epics and stories.


08:33 pm November 17, 2016

Try coaching them to frame the scope in terms of MVP's (Minimum Viable Products). This is often a struggle with clients who are new to agile practice, because they find it hard to think in terms of incremental value, and it would be better to tackle this sooner rather than later. An epic and story mapping workshop can follow on from that.


04:51 am November 18, 2016

The following strategy would help.

1. Group the related customer requests that will form one requirement/Main Feature. (E.g:- Payment gateway support in a mobile app)
2. Come up with the list of features under it(E.g:- include user option, gateway implementation, sync with user account)
3. Order the groups with the client request's importance.
4. Extract the minimum set of features from the top order ones to form MVPs
5. Epics can be created and stories can be evolved from there.


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.