Introduction
Effective communication with implementers is crucial for the success of any Enterprise Architecture (EA) initiative. Implementers need clear guidance on the gaps they must fill, the specifications they must conform to, and the controls they must implement. This guide will provide practical advice and examples on how to communicate effectively with implementers, ensuring they understand their responsibilities and can deliver value aligned with the target architecture.
Key Components of Communication with Implementers
1. Implementation Project Context
Purpose: Provide implementers with the context of their project within the broader roadmap. This includes understanding where the project fits, the value it will deliver, and any dependencies.
Examples:
- Roadmap Integration: Show implementers how their project aligns with the overall roadmap. For example, if the roadmap includes initiatives to improve customer experience, highlight how the implementer’s project contributes to this goal.
- Value Dependency: Explain the value or value dependencies the project will provide. For instance, if the project aims to enhance data security, clarify how this will support overall business objectives.
2. Scope
Purpose: Define the scope of the implementation project, including the work packages and gaps the implementers are responsible for, as well as any gaps they are not responsible for.
Examples:
- Work Packages: Clearly outline the work packages within the project. For example, if the project involves migrating to a new CRM system, specify the work packages such as data migration, system integration, and user training.
- Gap Responsibilities: Identify the gaps the implementers are responsible for filling. For instance, if the gap is related to compliance with new regulations, specify which regulations and what needs to be done to achieve compliance.
3. Conformance
Purpose: Specify the set of architecture specifications and controls the implementation project will be assessed against. This ensures that implementers understand the standards they must meet.
Examples:
- Architecture Specifications: Provide detailed architecture specifications. For example, if the project involves developing a new application, specify the required architecture patterns, data models, and integration points.
- Controls: Define the controls that must be implemented. For instance, if the project involves enhancing security, specify the security controls such as encryption standards, access controls, and audit requirements.
Practical Tips for Communicating with Implementers
1. Use Exclusionary Specifications
Purpose: Draft specifications that highlight what is prohibited rather than mandating what is permitted. This approach reduces the need for omniscience during architecture development and encourages creativity during implementation.
Examples:
- Prohibited Actions: Instead of mandating specific technologies, specify what is prohibited. For example, “The use of unencrypted data transmission is prohibited” rather than “Data must be transmitted using SSL/TLS encryption.”
- Creative Solutions: Encourage implementers to find creative solutions within the boundaries set by the exclusionary specifications. For instance, “Any data storage solution that does not comply with GDPR regulations is prohibited.”
2. Reasonable Interpretation Test
Purpose: Assess specification compliance through a reasonable interpretation test by a reasonable person. This ensures that implementers understand the intent behind the specifications and can interpret them correctly.
Examples:
- Requirement/Specification Pairs: Link specifications to requirements to provide context. For example, “The system must support real-time data processing (Requirement) by ensuring that data latency does not exceed 50 milliseconds (Specification).”
- Value Testing: Ensure that the implementation can be value-tested against the requirement/specification pairs. For instance, “The implementation must demonstrate that data processing times are within the specified latency requirements.”
3. Architecture Contract
Purpose: Use the Architecture Contract to link the implementation project to the target architecture in terms of context, work required, and conformance tests. This ensures that implementers understand their responsibilities and how their work will be assessed.
Examples:
- Context: Provide the big picture to guide projects implicitly to value production. For example, “This project is part of the broader initiative to enhance customer experience by improving data processing times.”
- Work Required: Specify the work required to fill gaps and meet architecture specifications. For instance, “The project must integrate the new CRM system with existing data sources and ensure compliance with data privacy regulations.”
- Conformance Tests: Define the tests that will be used to assess the implementation. For example, “The system must pass security audits and performance tests to ensure it meets the specified architecture standards.”
Examples of Effective Communication with Implementers
Example 1: CRM System Migration
Context: The project aims to migrate to a new CRM system to improve customer relationship management and enhance data analytics capabilities.
Scope:
- Work Packages: Data migration, system integration, user training.
- Gap Responsibilities: Ensure data integrity during migration, integrate the new CRM system with existing applications, and train users on the new system.
Conformance:
- Architecture Specifications: Use standard data models, ensure real-time data synchronization, and comply with data privacy regulations.
- Controls: Implement encryption for data transmission, enforce access controls, and conduct regular security audits.
Exclusionary Specifications:
- Prohibited Actions: Do not use unencrypted data transmission. Do not store customer data without compliance with GDPR regulations.
Reasonable Interpretation Test:
- Requirement/Specification Pairs: The system must support real-time data processing (Requirement) by ensuring that data latency does not exceed 50 milliseconds (Specification).
Example 2: Security Enhancement Project
Context: The project aims to enhance the security of the enterprise’s IT infrastructure by implementing advanced security controls and compliance with industry standards.
Scope:
- Work Packages: Implement encryption, enforce access controls, conduct security audits.
- Gap Responsibilities: Ensure compliance with industry security standards, implement advanced security controls, and conduct regular security assessments.
Conformance:
- Architecture Specifications: Use industry-standard encryption algorithms, enforce multi-factor authentication, and comply with data protection regulations.
- Controls: Implement intrusion detection systems, enforce access controls, and conduct regular security audits.
Exclusionary Specifications:
- Prohibited Actions: Do not use outdated encryption algorithms. Do not store sensitive data without encryption.
Reasonable Interpretation Test:
- Requirement/Specification Pairs: The system must comply with industry security standards (Requirement) by implementing advanced encryption and access controls (Specification).
Conclusion
Effective communication with implementers is essential for the success of any Enterprise Architecture (EA) initiative. By providing clear context, defining scope, specifying conformance requirements, and using exclusionary specifications, architects can ensure that implementers understand their responsibilities and can deliver value aligned with the target architecture. This guide provides practical tips and examples to help you communicate effectively with implementers and support the successful implementation of your EA projects.