
π Business Analysis & Process Β· Swimlane
How a change to a production system is requested, assessed, approved by the change board, built, tested and released.
Drawing diagramβ¦
Swimlane map of a software change request: a business user raises a change request, the business analyst writes requirements and an impact assessment, the change advisory board approves or rejects it, developers build it, QA tests it and sends defects back to development, and the release manager deploys it to production.
flowchart LR
subgraph Biz["π€ Business User"]
direction LR
S(["Start"]) --> A1["Raise change request"]
E(["Change live"])
X(["Change rejected"])
end
subgraph BA["π Business Analyst"]
direction LR
B1["Write requirements"] --> B2["Assess impact"]
end
subgraph CAB["ποΈ Change Advisory Board"]
direction LR
C1{"Approve change?"}
end
subgraph Dev["π» Development"]
direction LR
D1["Build change"]
end
subgraph QA["π§ͺ QA"]
direction LR
F1{"Tests pass?"}
end
subgraph Rel["π Release Manager"]
direction LR
G1["Deploy to production"]
end
A1 --> B1
B2 --> C1
C1 -->|No| X
C1 -->|Yes| D1
D1 --> F1
F1 -->|No| D1
F1 -->|Yes| G1
G1 --> EWho does what when a bank approves a personal loan: the customer, the loan officer, the credit team and operations, with the rework loop for missing documents.
The purchase cycle from an employee's request to paying the vendor, across the requester, the manager, procurement, the vendor and accounts payable.
How a new joiner is onboarded across HR, the hiring manager, IT and the employee, from signed offer to a productive first week.
A car insurance claim from accident to settlement, across the policyholder, the insurer's claims desk, the surveyor and the garage.
From a customer's order to cash in the bank, across sales, credit control, the warehouse, logistics and finance.
An ITIL-style incident flow across the user, the service desk, the support team and the problem manager, with escalation for major incidents.