It was time for BIT to introduce a framework for developing  IT architecture aligned with ISO 9001 requirements: TOGAF.

Emma (the General Manager of BIT) was convinced that ISO 9001 is a powerful tool to ensure a disciplined implementation of BIT principles.
She understood that the very high-level description of ISO 9001 norms allowed it to adapt to the changing activity of BIT. It allowed practitioners to fill the norm with their own best practices.
In particular, BIT found it very useful to integrate in their ISO 9001, ITIL best practices and the governance tool Balanced Scorecard.

Impressed by how ITIL best practices complemented ISO 9001 for IT service delivery, Emma tasked Paul (BIT’s Quality Coordinator) with finding a framework to develop an IT architecture for both BIT and their customers.

This framework should be:
1) compatible with the PDCA model (a true pillar of the ISO 9001 system);
2) Vendor agnostic;
3) compatible with the project management approaches used in BIT.
4) ensure that the IT infrastructure is aligned to the business requirements, both at strategic and operative level.

Since BIT helps customers develop enterprise architectures, it was natural for Paul to seek advice from the Enterprise Architect. Without hesitation, the architect recommended considering TOGAF.

The Enterprise Architect suggested focusing on the Architecture Development Model (ADM) component of TOGAF to demonstrate how this framework aligns with Emma’s principles.

The ADM outlines the phases and steps involved in developing an Enterprise Architecture. It defines the what and when of the architecture development process.

1) The ADM is compatible with the PDCA model.
The Architecture Development Model, the core component of the TOGAF, is fully compliant to the PCDA Cycle.

2) The ADM is Vendor Agnostic
TOGAF focuses on business needs and functionalities, not specific vendors.
It allows you to model IT components and their relationships without being tied to any brand.
Phase C and Phase D of the ADM model maintains a vendor-agnostic approach by focusing on methodologies, best practices, and standards that guide the development of a flexible and interoperable technology architecture. By emphasizing requirements, abstract modeling, and a structured evaluation process, TOGAF ensures that the Information and technology architecture can be implemented using a variety of vendor products.
Anyway, TOGAF is not an abstract framework. In phase E of the ADM it is necessary to identify the best vendor solutions that match the agnostic Information and Technology architectures identified in the previous phases.

3) The ADM is compatible with the project management approaches used in BIT.
TOGAF in Phase F (Migration Planning) allows for the use of both Agile and Waterfall project management techniques, providing flexibility for organizations to choose the approach that best suits their migration planning requirements.

4) The ADM ensures that the IT infrastructure is aligned to the business requirements, both at strategic and operative level.
Phase A (Architecture Vision) and Phase B (Business Architecture) of the TOGAF ADM ensures that the Information and Technology architecture is aligned with the strategic and operational business needs by defining the architecture vision, engaging stakeholders, and developing a detailed Business Architecture that supports business processes and goals

Paul understood that demonstrating TOGAF’s alignment with Emma’s four principles was just the first step for introducing it as BIT’s methodology. He also needed to clearly showcase the benefits of TOGAF and carefully consider any potential challenges associated with IT adoption within the framework.

BENEFITS OF TOGAF for BIT.

• Increased Efficiency and Consistency: TOGAF provides a structured approach to IT architecture development, leading to more efficient internal processes and consistent infrastructure design for both our company and our clients. This translates to faster project delivery, reduced rework, and improved cost control.
• Improved Communication and Alignment: TOGAF facilitates clear communication between our teams (architecture, development, support) and with clients. A common language and framework ensure everyone understands the “why” behind design decisions, leading to better alignment between business goals and IT infrastructure.
• Reduced Risk and Enhanced Security: TOGAF promotes the use of industry standards and best practices, which minimizes security vulnerabilities and project risks. This translates to a more robust infrastructure for both our company and our clients.
• Competitive Advantage: By adopting a recognized framework like TOGAF, we demonstrate a commitment to quality and best practices. This can give us a competitive edge when attracting new clients and differentiate us from less structured competitors.

THE OBSTACLES in Adopting TOGAF.

• Complexity and Cost: TOGAF can be a complex framework to implement, requiring significant investment in training and potentially new resources. The initial learning curve and potential disruption to our existing workflows could outweigh the benefits, especially for smaller projects.
• Overkill for Our Size? Our current approach using Kanban and Prince2 might already be sufficient for our current scale and project complexity. TOGAF’s rigidity may not be necessary for our current needs.
• Focus on Agility: Our clients likely value our ability to adapt quickly to changing needs. TOGAF’s structured nature might introduce delays and slow down our responsiveness.