Why does an architect need this skill?
Architectural change management is the process by which the architecture is moved into production and the target business value must be achieved. This involved both implementing the architecture into the target environment as well as monitoring and managing changes to the architecture as it moves into production environments. As change management is where the work of the architect is realized into actual business value it is arguably among the most critical skill of a successful architect.
Common tasks involved in this skill
The architect will be engaged in multiple tasks through the change management phase of architectural development and deployment. Among them are:
- Building change requests based on architecture
- Communicating nature/priority/details of change
- Working with areas to assess and address impact concerns
- Guide change through change control processes
- Manage the implications of any changes to the architecture based on input of the change control process
- Manage political and procedural concerns to ensure timely and efficient implementation
What is the architect’s ownership in this skill?
The architect will have contributor or responsible roles in developing change requests, communications with change management boards, may act as change owner either directly or by proxy, and will receive and assess architectural impact of any modifications requested by the change board.
How is this skill used by the architect in daily activities?
The architect would be expected to be able to:
- Build their architectures with an understanding of change management (architecting for operations / architecting for change) to minimize friction during deployment and maximize business value derived from the change.
- Have an understanding how changes are managed in an organization. This would include understanding what change management processes are used in an organization and how this may impact their architecture
- Communicating and guiding changes through the change management process. Ensuring that change requests are consistent to the principles and goals of the architecture. Accurately communicating impacts, dependencies and priority of the changes resulting from the architecture.
- Managing architectural changes resulting interaction with change boards. Specific change processes may impact multiple aspects of the architecture including scheduling of changes, sequencing of activities, impacts to other changes, risk management, and measurement of architectural targets.
Engaging with operational and change management teams to learn about challenges, opportunities and other elements which would influence current and future architectural decisions.