Power Apps Consultants Canada

Customers 'Requirements Are Usually "Features", NOT "User Stories"

Customers 'Requirements Are Usually "Features", NOT "User Stories"


When a customer says to you, "we need the system to ...", they are generally referring to "features" and not "user stories". A lot of Business Analysts and Functional Consultants hear the words "need to ..." and instantly equate that to a "user story" when it is not.

Why is it a "feature", not a "user story"?

You can think of a "feature" as a workflow drawing, or swim-lane diagram. "Features" have steps along the way. Each one of those steps is a "user story" with "tasks" that a Developer must configure. When customers tell you their needs, most times that need involves many steps along a path to get to the end result: so it is a "feature".

Why the mix up with a "user story"?

The general format for a "user story" is as follows: "As a (job role), I need to (list the requirement here) because (reason the requirement exists)." Because the "user story" has the words "need to" or "want to" in the format that we write them down and the fact that most customers say, "I need to have the system do ...", people equate the requirement to a "user story". Just because someone says the words "need to" does not make their statement a "user story". Again, if what they ask for has steps, then it is a "feature".

Example ...

Customer says, "I need to do spell checking in Swahili." This is a "feature", nota "user story". The steps might include opening the spell checker, clicking the "language" button, and then selecting "Swahili". Each one of those steps is a "user story". A Developer would need to do a task or multiple tasks to enable each step, "user story", along the way.

Happy software engineering!

About Purely CRM

For close to a decade our Purely CRM team has been laser-like focused on delivering CRM solutions built solely on Microsoft Dynamics 365 CRM, combined with Power Apps and the Microsoft Power Platform. We’ve expanded our team immensely in the past years to help better serve our clients and partners. Most recently we merged with Endeavour Solutions, a top Microsoft ERP, CRM, and Cloud consulting firm to further expand our talented team of CRM consultants.

Our core focus is on large mid-market and enterprise CRM Design & Development projects, Staff Augmentation, and CRM Support. When needed we can also tap upon our peers at Endeavour for Dynamics 365 Business Central ERP to provide an All-in-One Cloud ERP-CRM.  We provide services to clients Coast to Coast across the United States and Canada. We do not use resources overseas.

Reach out to explore our track record, rates, skills, and approach to discover how we can collaborate and drive YOUR SUCCESS.

Are You Ready To Get Started?

Let's Talk