TRANSFORM
Methodology
The curated methodology mix of the TRANSFORM delivery model
TRANSFORM combines established, scientifically grounded methods and standards with ReqPOOL's own agentic procedures per phase. The matrix shows the complete methodology mix; each phase links to the detailed description with purpose and references.
Methodology matrix
| Phase | Methodology mix | Normative & scientific anchors |
|---|---|---|
| 01 Strategy | ReqPOOL agentic readiness maturity modelEnterprise Architecture as StrategyBalanced Scorecard & strategy mapsWardley MappingBusiness Model Canvas / Value Proposition DesignLeading Change (8-step model) | Kaplan & Norton (1992); Kotter (2007); Osterwalder & Pigneur (2010); Ross, Weill & Robertson (2006); Wardley (2016); inspired by the acatech Maturity Index |
| 02 Plan | Scaled Agile Framework (SAFe) — elementsWSJF / cost of delayOKR (Objectives & Key Results)ISO 31000 risk managementReference class forecastingPMBOK Guide — tailoring | Doerr (2018); Flyvbjerg (2014); ISO 31000:2018; PMI (2021); Reinertsen (2009); Scaled Agile Inc. |
| 03 Analyse | Reverse engineering taxonomyHorseshoe model (architecture reconstruction)Process miningBABOK v3 — business analysis techniquesIREB CPRE / requirements engineeringISO/IEC/IEEE 29148 | Chikofsky & Cross (1990); IIBA (2015); ISO/IEC/IEEE 29148:2018; Kazman, Woods & Carrière (1998); Pohl (2010); IREB; van der Aalst (2016) |
| 04 Design | Domain-driven design (strategic)arc42 & C4 modelAttribute-driven design (ADD 3.0)ISO/IEC/IEEE 42010ISO/IEC 25010 quality modelReqPOOL Agentic Reference Architecture | Bass, Clements & Kazman (SEI); Evans (2003); ISO/IEC 25010:2023; ISO/IEC/IEEE 42010:2022; ReqPOOL (internal); cf. Anthropic (2024); arc42; Brown |
| 05 Build | Trunk-based developmentContinuous deliveryTest-driven developmentDORA metricsClean code & SWEBOKReqPOOL Agentic Engineering Playbook | Beck (2002); Forsgren, Humble & Kim (2018); Humble & Farley (2010); IEEE CS (SWEBOK v4); ReqPOOL (internal); cf. Anthropic (2024); trunkbaseddevelopment.com |
| 06 Test | ISTQB test processISO/IEC/IEEE 29119Test pyramidRisk-based testingMutation testingLLM/agent evaluation | ISO/IEC/IEEE 29119-1:2022; ISTQB; ISTQB Advanced; Jia & Harman (2011); Liang et al. (2022), HELM; Vocke / Fowler (2018) |
| 07 Deploy | Continuous deployment & deployment pipelineGitOpsProgressive delivery (canary, blue-green)Infrastructure as codeStrangler fig migrationDORA change management | DORA / Forsgren et al.; Fowler (2004); Google SRE; Humble & Farley (2010); Morris (2020); OpenGitOps / CNCF |
| 08 Operate | Site reliability engineering (SRE)ITIL 4 — service value systemAIOpsEU AI Act & NIST AI RMFFinOpsContinuous improvement (PDCA/Kaizen) | Beyer et al. (Google, 2016); Deming; ITIL CSI; EU 2024/1689; NIST; FinOps Foundation; Notaro et al. (2021); PeopleCert/Axelos |
Principles of method application
- Methods serve the artifact, not vice versa: a method is only applied if it produces a gate-relevant result.
- Standards before invention: where a norm or established body of knowledge exists (IREB, BABOK, ISTQB, ITIL), it is the binding reference frame.
- Agentically operationalized: wherever possible, a ReqPOOL Suite tool carries the method — method knowledge is executed, not merely documented.
- Scientific anchoring: the primary source is stated for every method; consultants deepen their knowledge via the linked literature.
- Tailoring requires documentation: deviations from the standard mix are justified in the gate review and approved by the engagement lead.
Deep dive per phase
The full method descriptions with purpose and references live on the phase pages; compact checklists in the best-practice PDFs.
Best-practice PDFs