Assignment
Having good requirements is key to the success of a Dynamics 365 implementation. Rewrite these requirements to make them useable by the project team.
Examples of poorly written requirements (select to reveal better requirements):
Users expect forms to load fast.
Forms for common tables must load in less than one second. Common tables include accounts, contacts, and opportunities.
We're obligated to comply with General Data Protection Regulation.
System contacts must be able to opt out of communication.
Sales managers must approve the closing of significant deals when they're lost.
An opportunity above $1 million can only be closed as lost by a sales manager.
Budgets must be approved by John Doe when generated.
Budgets must be approved by a financial controller role.
Master planning should run in less than an hour.
Master planning should run daily.
All frauds must be caught at point of sale.
Uncaught fraud should total less than three percent of daily transactions.