I have gathered and documented thousands of requirements for hundreds of applications over
the years. Good requirements are easily understood by the IT team and are testable.
I recently found a great post by David Shaffer called “It’s the Requirements fault! A Recipe for Requirement Clarity “. He really provides a clear concise method for developing solid requirements. Below are a list of questions from his article that I highly recommend any analyst consider when gathering and documenting requirements.
For each requirement you ask the following questions:
- Is the requirement written in S-V-O format? (Subject-Verb-Object)
- Is the requirement written in active voice using a strong auxiliary verb?
- Does the requirement focus on the business need rather than a technical solution?
- Is the requirement easy to understand by all audiences?
- Is the requirement simple, short, and unambiguous?
- Will an example improve the understanding of the requirement?
- Will a visual figure or wireframe improve the understanding of the requirement?
- Can the requirement be tested?
- Does the requirement contradict any other requirement?
- Does the requirement describe how it must be implemented (Ex: display in alphabetic order, ascending/descending order, required/optional field, alphanumeric, numeric, etc.)
What are some questions you normally use when gathering requirements?
Emails are part of the business landscape so including them in your Salesforce application makes sense. Designing the look of the email and its contents is important so that the emails provide users with the right information at the right time.
So what are some typical scenarios that result in email notifications?
- Acknowledgement – when a user submits a request, CASE, etc
- Status Update – providing user with status of request, CASE, etc
- Escalation – providing user with information on an escalation
- Information – providing user with information
Design Considerations for Salesforce Email Templates
Every email should include the following:
- Reason person is receiving the email
- ID / Link back to the Salesforce record which resulted in the notification (if appropriate)
- Relevant information
- Next Steps for person receiving the email (if any)
- Next Steps for Company/Group (helps to set user expectations)
- How to contact us
In the process of creating your templates consider the following:
- Pick the appropriate email template type based on what your email recipients can handle and the level of layout control you require.
- Maximize your subject line
- Keep it concise but informative
- For mobile recipients some researchers feel the first 35 characters are key
- Use Merge Fields to personalize content
- Be sure the merge fields you will be using have data. The merge field will not appear in the email for a record where there is no data in that field.
- Email templates give you access only to the fields that are accessible to you via your page layout and field-level security settings.
- Configure your email Deliverability Settings — Information about these settings can be found here.
A great place to see how to create a Salesforce Email Template is the article “How to create an email template in Salesforce” at wikihow.com.
How do you use email notifications in your business?