web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Requirements, User Stories, or Features for User Requirements for OOB Dynamics CRM

(0) ShareShare
ReportReport
Posted on by 75

If you were starting a new implementation of Dynamics CRM, are there Requirements, User Stories, or Features for User Requirements for out of box CRM that could be used for User Requirements so that you don't have to develop those for features already implemented in Out of Box CRM?  It would seem that this would be easier to start with and get acceptance of these OOB requirements rather than starting from Scratch.. any ideas on whether these items exist somewhere?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    ScottDurow Profile Picture
    21 on at

    I have found that it isn't a good idea to reverse engineer requirements from a product. Rather collect user stories/requirements in the context of Dynamics Crm. Training your BAs/product owner in dynamics Crm before this process starts can really make this process run smoothly.

    Hope this helps,

    Scott

  • Suggested answer
    Magor Kovacs Profile Picture
    1,835 on at

    Hello tsheives,

    I would start with cross referencing the specific customer's requirements with the capabilities of CRM. There isn't a one size fits all solution, unfortunately.

    I also second Scott's suggestion of avoiding reverse engineering in such situations.

  • tsheives Profile Picture
    75 on at

    Thank you for your response.  I like the idea of training Product Owner on CRM prior to even detailed requirements - that is a good idea.

    In a recent project, the client wanted (and we wanted because it was fixed price) features that were OOB. Certain features that the client wanted were not OOB.   Instead of informing the client this, the client starts getting the expectation that this feature was going to be available.  We then had to turn the client round and inform them that the requirement they asked for could not be filled with an OOB solution.  The BA did not have enough CRM knowledge to know not to tag requirements early on that were not OOB.

    So I was wondering if there existed a nice full featured documentation of requirements for CRM Dynamics that met the needs of good requirements such as testable, success criteria, etc.??  The training would help... in our case both for the BA on our side and for sure the Product Owner side.

    Any further thoughts are appreciated?

  • Suggested answer
    Magor Kovacs Profile Picture
    1,835 on at

    Hello tsheives,

    As mentioned before, finding success stories will not be difficult :) But a one size fits all solution will likely not be found, simply because of the wildly varying needs of customers (for instance an automotive company will have completely diffrent Dynamics CRM needs than, say, an Insurance company).

    As such, a Business Analyst, possibly supported by a technically knowledgeble person will be a huge bonus in mapping out the customer needs.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans