2023-04-25-Capgemini-敏捷与IT体系结构第2部分（英）_30页_8mb

JIT-JEA in Action Summary

The JIT-JEA (Just In Time-Just Enough Architecture) model emphasizes lightweight and practical architecture practices within Agile methodologies. This document details 10 real-life examples from Capgemini engagements, illustrating the application of JIT-JEA across various domains.

Introduction

JIT-JEA is an Agile architecture approach that focuses on five pillars: Just Enough Architecture, Documentation, Governance, Time!, and Iteration Size Chunks. It ensures architecture aligns with business goals by embedding architectural activities into Agile workflows. The examples provide practical ways to integrate these pillars.

The 10 JIT-JEA Examples

1. Architecture Enablers: Introduces new task types into the Agile backlog to address architectural topics, improving visibility and integration with user stories. Benefits include better prioritization, iteration-sized chunks, and built-in Agile architecture.
2. Documentation as Code (DaC): Uses plain-text formats (e.g., Markdown) managed via version control for collaborative and maintainable documentation. Benefits include simple content focus, version history, and easy lifecycle integration.
3. Lightweight Architecture Decision Record (LADR): A simple method for tracking architectural decisions with versioning and sharing. Benefits include improved communication, decision alignment, and clear architectural history.
4. Architecture Styles Enabling Design Flexibility: Implements styles like hexagonal or clean architecture for clear separation of concerns, allowing delayed technical decisions and better testability. Benefits include the ability to change infrastructure with less impact and postpone decisions.
5. Walking Skeleton as Agile Architecture Reference: A minimal end-to-end implementation to prove basic architecture before building, providing early feedback on suitability. Benefits include validating architecture intent, scalability, and guiding developers.
6. Architectural Runway: Ensures existing code and infrastructure support near-term features without excessive redesign. Benefits include consistency, reduced rework, and continuous evaluation.
7. DevOps Guardrails: Uses DevOps tools to automate checks for architectural compliance and enforce governance. Benefits include decentralized decision-making, automatic enforcement, and risk avoidance.
8. Low Code for Rapid Evaluation of Architecture Alternatives: Employs low-code platforms for quick prototyping and testing of architecture options. Benefits include faster evaluation, reduced costs, and improved time-to-market.
9. Design Systems: Creates shared libraries and patterns for consistent user experiences and abstraction. Benefits include structural reuse, faster development, and better user adoption.
10. Technology Radar for Your Company or Division: A tool to track and share technology trends, guiding adoption and risk assessment. Benefits include shared insights, improved decisions, and centralized governance.

Concluding Remarks

JIT-JEA practices offer practical, value-driven methods for Agile architecture, enabling teams to balance speed and robustness. By democratizing these techniques, organizations can enhance architectural quality and adaptability in dynamic environments. Further exploration of JIT-JEA and its real-world applications can provide deeper insights.