Developing an FSD outlining tasks to be automated
In this section, we will briefly look at an FSD and decide which steps of the specification can be automated. Identifying these upfront in the FSD will help not only the technical team to build the functionality and automation, but also set expectations with the business users. Socializing this with all key stakeholders will help form a collective understanding of the requirement and how it will be performed. Sometimes, what we think needs to be automated may not be agreeable to the business stakeholders. This is good to know beforehand, and resources can be better utilized for other requirements.
How to create an FSD is not in the scope of this book. In this section, we will take a quick look at typical CRM functional design document fields that are important.
Typical FSD fields are listed next. Notice the Can be automated? and Estimated effort columns in the following table. This will help us to identify if the functional steps...
