Architecture umbrella
A top-level index of architecture activities, findings, and design artifacts covering both current and future state analysis for product modernization.
Umbrella index
The index provides a top-level view of findings, artifacts and future state architecture developed during working sessions.
| Document | Purpose / Findings | Links |
|---|---|---|
| Project Playbook | Top-level project information page: project scope, product vision & strategy, and links to the team and decision templates below. | Project playbook |
| Team Roster | Team composition and responsibilities, led by the product trio, plus other key stakeholders. | Team roster |
| Team Activity Matrix | Team rituals, communication cadence and the attendance matrix. | Team activity matrix |
| Decision Rights | Who decides what: one decision, one owner, consulted parties named — plus the supporting RACI matrix. | Decision rights |
| Exception Log | Standing record of deviations from the team’s own rules: off-table decisions, readiness waivers and risk overrides. | Exception log |
| Current State Discovery | Provides detailed information regarding the current state product or system. | Current state technical discovery |
| Gap Analysis | Documents the gap between current and target state, and the work implied by closing it. | Gap analysis |
| Guiding Principles | Establishes product vision and guiding principles (strategic goals) for the project. | Product vision |
| Stakeholder Mapping | Map of existing and potential stakeholders. Documents stakeholder interest in the project and desired outcome from their involvement and actions. | Stakeholder mapping |
| User Personas | Defines the product’s user personas — who the users are, what they need and how they behave. | User personas |
| Business capabilities & functions | Establishes product features or business functions and connects them with user journeys (customer-facing use cases). | Business capabilities & functions |
| Strategic Event Storming | Facilitation guide and capture template for strategic event storming workshops. | Strategic event storming |
| Domain Detail | Domain-driven design detail: bounded contexts, aggregates and domain documentation. | Domain detail |
| Roadmap, OKRs and KPIs | Identify specific Objectives and Key Results (OKRs) along with quantitative, measurable Key Performance Indicators. Includes specifics on what will be measured to achieve success. | Roadmaps & OKRs |
| Feature Specifications | Features expressed in Gherkin “Given-When-Then” style and user journeys, providing clear and unambiguous objectives expressed in ubiquitous business language. | Feature Specifications |
| Target State Architecture | Target state architecture service catalog. Approved and in-process architecture choices and state designs documenting the North Star Architecture. | Service Catalog |
| DevSecOps Pipeline | Decide on DSO pipeline goals, including: DSO build standards, automation, security, promotion to higher environments, continuous integration and continuous delivery objectives, and technology stack. | Delivery processes |
| Hypothesis Log | Assumptions about customers and value, written falsifiably, with the cheapest test that can settle each one and its verdict. The working surface for continuous discovery. | Hypothesis log |
| Risk Log | Itemized and prioritized risks, documenting mitigation strategy and risk owner. | Risk log |
| Security & Compliance Concerns | Lists security, compliance and governance needs, and tactical steps linking to concrete features on the product roadmap. | Security & compliance cross reference |
Work product index
This index provides links to work product from analysis, workshops and design sessions.
| Workshop | Purpose / Findings | Links |
|---|---|---|
| Areas of Improvement | Workshop to focus on discovering areas of improvement across technology, organization, ways of working, product delivery, execution. | LINK |
| People Organization | Establish any changes to people organization, such as team enablement, team alignment, growth or improvements that will enhance delivery. For example, organizing teams around a product mindset. | LINK |
| Ways of Working | Establish specific “ways of working,” including: Methodology (e.g., agile), rituals (e.g., “daily syncs, increment reviews”), team prerequisites, stage gates and procedures, roles, and responsibilities. | LINK |
| Cloud Cost Analysis | Preliminary investigation into costs “in the cloud,” and feasibility study regarding cost reduction objectives. | LINK |
| Migration Plan | Create 30, 60, 120 day plan with measurable outcomes, immediate actions, and goals, including actions for: Roles & responsibilities, policy, escalation, tooling and technology adoption, team enablement. | LINK |