Summary
To summarize, an SA is one of the most important roles in an RPA project. We saw how an SA can be helpful for not only bringing integrity to the team but also bridging technical and functional gaps in the team. Other than their primary role and responsibility, they have to take on extra responsibility to make sure that the end goal is achieved. Only results matter—keeping that attitude, the SA helps the developer overcome technical impediments and at the same time helps the team as a guardian angel, influencer, and enforcer of best practices. They also keep the team moving forward in the right direction by guiding them and keeping them focused. They are the owners of the solution so as to make sure that it gets implemented to its utmost extent. They help in filling other people’s shoes, such as being a consultant, developer, and delivery facilitator. This gives us a clear picture of what it takes to be an SA. An SA has to possess many skills so that they can be used as a trump card whenever needed.
Having an SA on the team gives peace of mind and helps make sure that the project goes smoothly. This is why SA selection should be exhaustive.
In the next chapter, we will talk about a case study of a banking organization, which will be our reference point and help build a story for future scenarios. This will also help to visualize an end-to-end RPA engagement unclear for understanding the length and breadth of an RPA project.
