![]() ![]() for services still in preview or just released. an out-sourcer or other system integrators (SI’s), or unproven / innovative technology, e.g. Azure IaaS and PaaS, or various parties involved e.g. ![]() Classified as riskier would be multiple implementation technologies, e.g. However, when technology or customer related risks are perceived as being significant, having a Solutions Architect in a project is advisable. If the project is limited to a single implementation technology that has been proven in a similar context, it is usually enough to assign a Technical Architect or Senior Consultant. Of course, having a Solutions Architect for every engagement is an overkill. Good Solutions Architect looks after technical soundness and integrity of the project the same way as good Project Manager looks after schedule and budget constraints. When in agreement with the customer and project team, this role can work easily part-time from remote. I also would add, SA have to be kind of extroverted and very strong in communication. Consequently, the Solutions Architect must have a balanced mix from technical depth to breath and even must have some business skills to contribute sensibly to all these activities. Instead, the SA gets involved through concept definition and requirement engineering, design and design documentation, implementation oversight and even hand-over to customers IT. Solutions Architect are not doing any hands-on as coordination of technical and project related activities takes most of their time. This makes the SA as the “go-to” person for any technology ask, conflicts, implementation issues, or decisions. Typical part of this role is to moderate between business and technology teams and various other groups or even companies. The Solutions Architect (SA) is assigned to an engagement or program to ensure technical integrity and consistency of the solution at every stage of its life cycle (in the project). The graphic below visualizes nicely how every one of these Architects would play an essential role on the soccer field: What type of Architect are you? The Solutions Architect ![]() That’s why these jobs are not competing they need each other to be successful and drive impact for our customers. ![]() Well, a person can become a Senior Technical Architect from an Associate Technical Architect over time, but that does not make him/her an Enterprise Architect. There is a misconception that these are different levels of an architect. That’s why these aren’t just different roles these architects are different job profiles. In this article, I try to explain the three primary architect profiles:Įvery of those Architect profiles will address different requirements, needs, and types of insight that may span business to technology. In IT, most of the Architects I know started as an Engineer or Consultant (some years ago), and becoming an Architect is a natural career path by taking more and more responsibility and leadership. Architects who design entire buildings bring unusually a university background rather than hands-on experience. In the world of woods and bricks architecture, this is probably not the most common career path. Perhaps the most interesting difference is that there is often an expectation from the customer, that the IT Architect is also bringing hands-on experience. You may wonder how does an IT Architect differ from a traditional Architect, those guys who design real houses and buildings? Architects are “ designer” and lead with “ innovation” to “ inspire” customers, which both have in common. But, which type of architect is the right one, and who would be the right candidate for the identified position?įirst a few steps back. There is a trend that companies and/or customers are starting those cloud or innovation teams with an architect. Not only inspiring with innovation, but customers also want to be taken care of and follow an experienced person or team. Moving entire systems or even a whole company to the cloud requires some efforts and often also a specialized skill set. Everyone these days speaks of digital transformation, the evolution of traditional business and processes to the next level – to the public cloud. ![]()
0 Comments
Leave a Reply. |