Structuring requirements
Analysing business requirements, writing them as user stories and aligning them with development.
Case study · Banking digitalisation
Bringing digital banking processes together on the business and technical side.
Acting as the link between product owner and development to clarify requirements, steer risks and support delivery through to go-live.
RoleBusiness Analyst
EnvironmentRegulated banking
ApproachUser stories and Kanban
ClientING
Starting point and challenge.
In regulated banking, business requirements, risk assessment, technical delivery and traceability have to be closely interlinked.
The assignment covered both ongoing interface work and testing, rollout and go-live in a changing environment.
My responsibility.
I worked as the link between product owner and development. This included requirements analysis, risk management, software testing and support for rollout and go-live.
Supporting risks and testing
Tracking open points, validation logic and business acceptance throughout delivery.
Developing business cases
Structuring business benefit, feasibility and decision bases for new digital processes.
Contribution and outcome
Specific digital banking functions delivered.
I translated regulatory requirements into business requirements, aligned them with the business unit and saw them through to go-live. For further digitalisation steps I produced assessed business cases as a basis for decisions. The tools used were Azure DevOps, Confluence and Microsoft Teams.
Are you facing a comparable initiative?
If regulatory requirements need to be turned into delivery: describe the initiative, the project phase and the role you have in mind. You will get an honest assessment.
Discuss your project