QNB: requirements in 3 sessions, not 3 months
Together with QNB, WYnova redesigned the requirements definition process across IT, Business and Product, cutting it from up to 3 months of discussion to a maximum of 3 sessions.
- Client
- QNB
- Sector
- Banking
- Service
- Forward Deployed Engineering
- In production
- January 2025
requirements definition
in production
aligned: IT, Business and Product
The challenge
At QNB, discussing requirements with the business could take up to 3 months before development began, creating bottlenecks and delaying the entire delivery chain.
Key obstacles
-
Ambiguous requirements
Unclear communication between the teams involved.
-
Decisions made in silos
IT, Business and Product with no common decision-making process.
-
Reliance on consultants
Process knowledge concentrated outside the organisation.
The solution
WYnova redesigned the requirements process and the associated working culture on four fronts: research, incremental change, training and mentoring, and ongoing support.
-
01
Research
Diagnosis of the requirements process and its bottlenecks.
-
02
Incremental change
Gradual changes, introduced to maximise adoption.
-
03
Training and mentoring
Team formation under the new process.
-
04
Ongoing support
Support to sustain the change over time.
The decisive gain lay in the process design and the culture that sustains it, ahead of any technology.
Results
Requirements definition went from up to 3 months to a maximum of 3 sessions, sprints start earlier and alignment between Business and IT has improved. The new process has been in production since January 2025.
What we learned
Many delivery delays begin before development. A requirements process shared by IT, Business and Product shortens that path, and it lasts when it is backed by training and ongoing support.
Related cases and services
More cases and solutions in AI for banking and financial services.
