January 28, 2019
I recently attended the Application Strategies and Solutions Summit by Gartner, a leading information technology research and advisory company. One of the analysts shared with us that more than 50% of the organizations face application scalability, agility, resilience and other performance issues due to poor application architecture competency. Some of these organizations describe their architecture — a mess.
A competent architecture has three main characteristics:
How do you improve the architecture competency? Some organizations have tried to improve it, but with little success. The problem lies in the absence of a holistic approach that connects their people to a clear purpose and involves them in defining the practices that work for them.
The Communities of Practice (CoP) is an emerging approach for connecting people, sharing knowledge, and fostering individual as well as group learning and development. A successful Architecture CoP:
An Architecture CoP is a group of developers and architects who share a concern or a passion in Architecture and learn how to do it better as they interact regularly.
You may form CoPs across a variety of disparate areas within Architecture: application development, data management, integration, or infrastructure. Below is an example of API Communities of Practice for most organizations.
Purpose:
People:
Practice:
More companies are adopting the CoP approach today because it shares and diffuses architectural knowledge by connecting purpose, people, and practice altogether. I encourage you to introduce it to your Architecture organization, so that it creates better business alignment and decision-making, enables faster delivery of cost-effective projects, and improves productivity.