Service · Define
Get the scope right before you build
We turn strategy into clear requirements, process maps and business cases, so you avoid costly rework later.
Fixed-scope sprint · 3–4 weeks
The offer
What you get, and how long it takes
- Format
- Fixed-scope sprint · 3–4 weeks
- You receive
- Stakeholder and requirements workshops · As-is and to-be process mapping · Business case development · UAT planning and coordination
- Method
- The Geminista Method: Map · Fix · Prove
- Team
- Consultants with globally recognised project, programme and PMO certifications
Signs
You need business analysis when…
- You're selecting or implementing a new system and the requirements are unclear
- Change requests pile up once the build starts
- User acceptance testing keeps failing or slipping
- Vendors deliver what was written, not what the business needed
What we deliver
What we deliver
Stakeholder and requirements workshops
Structured sessions that uncover real needs, not wish lists.
As-is and to-be process mapping
A clear picture of how work happens today and how it should work in future.
Business case development
Costs, benefits and risks set out so leadership can decide.
UAT planning and coordination
Test scenarios, schedules and sign-off that prove the solution works.
How it works
From interviews to signed-off requirements in four weeks
- Week 1
Understand
Interviews, document review and current-state process mapping.
- Week 2
Workshop
Requirements workshops and future-state design with key stakeholders.
- Week 3
Document
Requirements, user stories, acceptance criteria and the business case.
- Week 4
Sign off
Review, prioritisation and formal approval, ready for build or vendor selection.
What you gain
What you gain
Less rework
Problems are caught early, when they are cheapest to fix.
Aligned stakeholders
Business and IT agree on scope before money is spent.
A stronger vendor position
Clear requirements make proposals comparable and contracts enforceable.
Frequently asked questions
Do you write user stories or traditional requirements?
Both, depending on how you deliver: Agile user stories, a BRD/FRD, or a hybrid of the two.
Can you support vendor or software selection?
Yes. Clear requirements are the basis of a fair RFP and an objective comparison of vendors.
Which tools do you use?
Yours: for example Jira, Confluence, Azure DevOps, Visio or Excel, so nothing is lost at handover.
How much of our team's time is needed?
Usually a few hours a week per key stakeholder, mostly in workshops.
Can you stay on through the build?
Yes. A dedicated business analyst can support the build and UAT.
Starting a new system or project?
Let's make sure the requirements are right from day one.