Release Coordination Agent
Coordinates release timing and release notes.
- Industry
- Banking
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Digital Banking
- Code
- PRD-12
It coordinates release timing for the bank's mobile and internet banking and core product changes, keeping out of month-end and quarter-end freezes and payment-scheme cut-over dates. It writes release notes for customers and staff and gives the notice that terms or fee changes require.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the release management tool: the release calendar, freezes, scheme cut-over dates, change advisory approvals and readiness checks..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Digital Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the release management tool: it schedules the release and publishes the notes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The release calendar: release days, change freezes, scheme and regulator cut-over dates, the change advisory process, customer notice periods for terms changes and the release notes style.
Reads from
the release management tool: the release calendar, freezes, scheme cut-over dates, change advisory approvals and readiness checks.
Acts in
the release management tool: it schedules the release and publishes the notes.
Hands back
An object with release, date, freeze_check (pass or conflict), notice_check (pass or short), readiness (a list of item and status), customer_notes, staff_notes and open_items (a list).
Asks a person when
A release falls in a freeze window, a terms or fee change has less than 60 days' notice, or readiness items are open.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Release days | Tuesday, Wednesday, Thursday | Comma-separated. |
| Freeze windows | the last 3 and first 2 business days of each month, the last 2 weeks of each quarter, 15 December to 10 January | No release in these windows. |
| Notice for terms or fee changes (days) | 60 | Customers get this much notice before an unfavourable terms or fee change takes effect. |
| Brief branches and contact centre before (days) | 3 | Frontline staff are briefed this many days before a customer-facing release. |
| Release notes style | plain | How customer notes are written. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Release only on Tuesday, Wednesday, Thursday and never in the last 3 and first 2 business days of each month, the last 2 weeks of each quarter, 15 December to 10 January.
- A change to terms or fees takes effect no sooner than 60 days after customers are told.
- Brief branches and the contact centre 3 days before any customer-facing release.
- Every change to core banking, payments or authentication needs change advisory approval and a rollback plan.
- Write plain notes that say what changes for customers and never mention security fixes in detail.
See the Release Coordination Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.