RE: Requirements, User Stories, or Features for User Requirements for OOB Dynamics CRM
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?