Capgemini-敏捷与IT体系结构第2部分（英）-30页_8mb

AGILE & IT ARCHITECTURE REPORT SUMMARY

JIT-JEA Overview

The report explores Just In Time-Just Enough Architecture (JIT-JEA), a framework for agile architecture that emphasizes delivering value through minimal essential practices. It aims to illustrate not only the definition but also practical application through ten real-world examples, mapping them to agile pillars such as Just Enough Architecture, Just Enough Documentation, Just Enough Governance, Just in Time, and In-iteration Size Chunks.

Key Examples

1. Architecture Enablers

• Description: Introduces SAFe Enablers (Exploration, Architecture, Infrastructure, Compliance) to handle architectural topics in agile backlogs.
• Benefits: Enhances visibility of architecture in the backlog, enables prioritization and iteration-sized development, integrates architecture into standard agile workflows.
• Action: Used in JIRA to track enablers with custom fields and workflows; helped visualize balance with user stories, track progress, and demonstrate impact.

2. Documentation as Code (DaC)

• Description: Uses plain-text formats (e.g., Markdown) managed with source control tools like Gitlab.
• Benefits: Simplifies content focus, improves readability, supports versioning, collaboration, and lifecycle management similar to software.
• Action: Applied to Capgemini product documentation with Gitlab for automatic rendering; enabled easy updates and collaborative editing.

3. Lightweight Architecture Decision Record (LADR)

• Description: Tracks architectural decisions with lightweight, searchable records, including context, scenarios, and implications.
• Benefits: Improves decision sharing, speeds up alignment across roles, maintains an architecture history.
• Action: Implemented in SharePoint with mandatory inclusion in the Definition of Done; decisions tracked via an architecture decision log.

4. Architecture Styles Enabling Design Flexibility

• Description: Utilizes styles like hexagonal/Clean Architecture for clear separation of concerns, delaying technical decisions.
• Benefits: Allows postponing technical choices, easier infrastructure changes, improved testability.
• Action: Applied in a public-sector project with hexagonal architecture; ensured domain logic independence, simplified evolutions with minimal effort.

5. Walking Skeleton as Agile Architecture Reference

• Description: A minimal, end-to-end working prototype proving architectural viability.
• Benefits: Provides early feedback, guides implementation, sets initial direction.
• Action: Created for an insurance microservices project; included core technologies and patterns, eased scaling and changes.

6. Architectural Runway

• Description: Existing infrastructure and components to support near-term features without excessive redesign.
• Benefits: Ensures consistency, reduces rework, enables continuous evaluation of the architecture.
• Action: Set up for a digital transformation client with Azure environments and CI/CD pipelines; monitored via KPIs to guide safe landings.

7. DevOps Guardrails

• Description: Uses DevOps tools to enforce architectural compliance through automatic checks.
• Benefits: Automates rule enforcement, avoids dangerous decisions, supports decentralized governance.
• Action: Implemented with Production Line to check code against architecture rules, including unit tests, quality gates, and coverage thresholds.

8. Low Code for Rapid Evaluation of Architecture Alternatives

• Description: Employs low-code platforms to test architecture options quickly.
• Benefits: Accelerates evaluation of alternatives, captures requirements faster, reduces costs.
• Action: Used Mendix low-code for an insurer to launch MVPs in weeks; supported rapid prototyping and market adaptation.

9. Design Systems

• Description: Consistent component libraries and practices ensuring reusable UI.
• Benefits: Speeds up development, reduces costs, improves brand consistency.
• Action: Developed for an energy company; audited components, standardized portal redesign, extended to all digital touchpoints.

10. Technology Radar for Your Company or Division

• Description: Categorizes technologies into Adopt/Trial/Assess/Hold rings for informed decisions.
• Benefits: Guides technology investments, manages risks, fosters communication.
• Action: Used by a water company to track trends; presented twice yearly to stakeholders for insights and governance.

Concluding Remarks

The report concludes that JIT-JEA principles enable agile and effective IT architecture practice, offering practical tools and techniques from real engagements. It highlights the journey's early stages but emphasizes continuous learning and democratization. The approach delivers significant value, combining conceptual and hands-on experiences.

Bibliography

• JIT-JEA Core Concepts: Capgemini Agile Architecture Point of View.
• Various sources: SAFe Enablers, Documentation as Code, etc. (Referenced documents and tools available online).

Authors

• Listed Capgemini experts contributing to the paper on agile architecture and JIT-JEA.