Guiding the team

We read about this function of the SA in previous chapters, but in this chapter, we will do a deeper dive into how an SA can proactively help a team before they even ask for help. This helps in two ways – it eliminates the deliverables being delayed and helps to mitigate the shy nature of developers who will avoid asking for help. The SA’s primary job is to make sure that developers get all the help they need. The SA is the caretaker. If developers make mistakes, it comes back to you. Do not, in any situation, think that they are responsible. Think of this as a student-teacher relationship. If a student fails in any subject, it is not entirely the student’s fault but also the teacher’s.

So, now let’s see how an SA can sharpen their instincts to sense and detect that a developer needs help:

• Experience: A lot can be learned over time and with experience. SAs use their experience as one of the tools to detect these knowledge...