Why Do We Need a Solution Architect?

In the modern age of industrialization, every industry is divided into segments, sectors, and lines of business (LOBs). Each of these divisions is then subdivided into roles. These roles are assigned responsibilities that become the core functions of that role. The IT industry is no different. It is also divided into LOBs, and those LOBs have functions and roles assigned to them. One of the roles is of a solution architect (SA). This is a generic role with subcategories such as enterprise SA or SA for a software tool or application.

It is very important to understand why an SA is needed in a project. This will help in establishing the credibility of the role as well as understanding the value this role brings to the table. An SA is like the glue that keeps the team together and brings integrity to the team. People debate whether they need an SA or not, and this chapter will focus on resolving all those doubts. You can be an aspiring developer who wants to become an SA or a project manager putting together a team for a project—all can benefit from the knowledge of why an SA is important and how their contribution leads to successful project delivery.

The agenda of this chapter will cover the following main topics:

• Understanding the importance of the SA role
• Bridging the gap
• Being a guardian angel, influencer, and enforcer
• SAs as solution owners
• SAs and the multiple hats they wear

So, let’s dive right in!