LEARN. PRACTICE. GROW.The outcome includes failure behavior
In the fictional Breeze case, an operator queries a payment’s status. When the source does not respond, the prototype shows the last value as current. Before discussing the library used, clarify what the operator needs to know to decide: when the data was obtained, whether it is stale, and how unavailability is presented. Write observable outcomes while leaving Developers room to choose implementation. An additional criterion requires 95% of queries below two seconds. The mean of ten queries in a different environment does not demonstrate that proportion under agreed conditions. Define the population, measurement start and end points, load profile, and failure treatment with the team. This example establishes neither a sufficient sample nor a universal performance standard. A quiet-morning test also does not demonstrate capacity at month-end closing. Cost discussions should retain visibility of relevant performance and availability requirements.
Calculate transition and observe the bill
In the Amber exercise, the new service has distinct monthly costs of 800 euros for infrastructure, 200 for licenses, and 300 for incremental support: 1,300 euros total. The old service costs 900. During two complete months of coexistence, recurring cost is 2 × (1,300 + 900) = 4,400 euros. Add 2,000 euros of transition work once, yielding 6,400 for the period. These figures are invented for training, excluding taxes and other charges. The price difference is not the cost of coexistence. Record start, end, incremental costs, overlaps, and conditions for eliminating old charges. If shutting down an instance does not change the contractual commitment until December, communicate observed usage reduction and the still-pending financial effect. Also confirm whether support, licenses, and data retention remain necessary. FinOps provides a reference for discussing service cost and requirements; it does not approve this scenario’s budget.
Find consumers and prepare independence
In the Nexus case, all human users have entered the new portal, but an Autosys job still consumes the old CFT file. History still requires authorized access. Map automated consumers, responsible teams, the need served, and adaptation evidence. Coordinate communication and preparation time with those depending on the service. GOV.UK retirement guidance helps frame these questions, but its own deadlines and procedures are not banking obligations. Confirm data destination, ownership, protection, access, and retention with the applicable owners without inventing a legal period. For APS, a demonstration to one person does not ensure the rotation can operate: check access, practice, recovery, and transition support. The Google SRE reference emphasizes preparation and progressive transfer; the organization defines its controls. The Product Owner presents value and options, but a resilience exception assigned to another authority remains dependent on that decision.
Nexus rehearsal with a transition decision
Use 35 minutes with a Product Owner, APS, development, FinOps, and observer. In the first five, introduce the service and goal. Spend ten on the Amber budget, separating recurring costs and transition. During the next ten, reveal the Autosys consumer, historical data, and missing rotation access. Request transition options that keep conditions explicit, such as bounded coexistence with owners and a review date, or delay with its impact communicated. Use the final ten to prepare a note for the decision authority and debrief. The note should distinguish available evidence, gaps, who decides, and the next step. The observer records whether the team included automated consumers, avoided counting unrealized savings, and preserved risk authority. Use observation states without an aggregate score. The guide has not been executed with human participants and demonstrates neither readiness of a real service nor BNP Paribas internal policy.
NEXUS GUIDE | 35 min: 5 + 10 + 10 + 10
New: 800 + 200 + 300 euros/month; old: 900 euros/month.
Coexistence: 2 full months; transition: 2,000 euros once.
Period cost / assumptions:
Need / human or automated consumer / owner:
Observable criterion / measurement condition / evidence:
History: destination / access / protection / owner:
APS: rotation / access / training / recovery / support:
Charges to eliminate / condition / date / evidence:
Transition options and impact:
Gaps / decision authority / next step:
Observation: not observed | with help | in rehearsal without helpTwo months of coexistence cost 4,400 euros; with 2,000 for transition, the period costs 6,400. The old job and history remain in the plan.
Common pitfalls
Mean as percentile evidence; human login as full migration; a stopped resource as a reduced bill; one demonstration as rotation independence.
Related topics: Acceptance criteria · FinOps and coexistence · APS handover
Transition requires needs to be met, costs understood, operational evidence, and decisions made by the appropriate authority.
Reference: Retiring your service · Scrum Guide November2020; EBM May2024; primary product practice reviewed 2026-09-30