How to be an SA
As you go through the different chapters of the book, you’ll notice that we focus on the role of the SA. But what is an SA, and how do you become one? It’s not that hard a role, but it should be given to someone with many years of experience and deployment projects under their belts.
The SA is one of the leaders of the project.
Figure 1.17 – An example of a project team
They need to have a deep technical and functional knowledge of the D365 Finance and Supply Chain Management application. They also should have extensive knowledge of technologies and applications that could potentially integrate with D365. As the team leader, the SA is the point person who project members will contact for any issues that may arise during the project timeline. They also need to have a level of soft skills to be able to work and communicate with people about the project solution, as well as the tasks that need to be completed during the project.
As an SA, you are also the point person when it comes to issues that happen during the project. As we mentioned previously, as the solution blueprint is a living document, you will have the opportunity to modify it during the deployment. When changes need to be made, usually a change request is created and signed by the customer, so you have in writing that the customer agrees to the change and, depending on how the project is funded, will pay for it.
In the end, the SA is the person who is the most technically knowledgeable and is able to make design decisions across all areas of the project, including development, configuration, security, licensing, storage, data migration, and go-live tasks. It’s also helpful if the SA understands the customer’s business (if not in detail, from at least an industry level). Above all else, a really good SA is a master of collaboration within their team and across the organization.
A SA will also need to be an excellent problem solver. No one knows all the answers to every question, so they need to be comfortable with doing research or asking colleagues for assistance with any challenges they come across. They also need to be able to distinguish the difference between a problem, a design issue, and a bug.
And lastly, an excellent SA will always be an eternal optimist and level-headed. They can’t let anything get to them. They are the team leader, and if it looks like they are doing something wrong, that will filter down to the rest of the project team and have a negative impact on the team and the delivery of the application. You need to be able to have that human touch that will let you successfully interact with your team members. You must always be positive and happy, even when disaster is staring you in the face.
