Requirements
Clarify vague needs into user stories, acceptance criteria, and requirements.
Acceptance criteria
Business Analyst / Functional Analyst
Nikita Goncharenko - Business Analyst
I translate messy business needs into clear requirements, user stories, workflows, and tested delivery.
5+ yearsDigital and project delivery
150+ ticketsStructured through JIRA / Odoo Project
What I Help With
From messy input to delivery-ready work
Process
Map workflows, find gaps, and make ownership visible before delivery starts.
Process analysis
Validation
Support test scenarios, UAT thinking, and delivered-solution validation.
UAT support
Data
Turn business questions into KPI logic, reporting needs, and measurable outputs.
KPI requirements
Case Studies
Proof of BA thinking
Migration
01Platform Migration & Process Alignment
Platform moves needed clear ownership, testing, and final workflows.
ProblemThree migrations had to move without breaking operational continuity.
My roleProcess clarification, stakeholder alignment, and testing support.
Actions
- Mapped ownership and delivery gaps.
- Documented the final workflow.
OutcomeClearer handoffs and fewer open assumptions before release.
Power BI
02Analytics Reporting & Business Decision Support
Fragmented data became usable KPI reporting for decisions.
ProblemReporting was fragmented, slow to use, and hard to trust.
My roleKPI clarification, data-source mapping, and output validation.
Actions
- Defined KPI and dashboard requirements.
- Validated outputs with business users.
OutcomeIdentifies fast performance changes each week, so budget shifts happen before losses scale.
Jira
03Website / Digital Workflow Delivery
Vague website requests were turned into scoped delivery tasks.
Problem150+ delivery tickets needed clearer scope and acceptance.
My roleBacklog clarification, acceptance criteria, and feedback coordination.
Actions
- Scoped backlog items and review checkpoints.
- Validated delivered website and integration work.
OutcomeLess rework and more predictable delivery.
Example Outputs
What I produce
User stories with acceptance criteriaRequirement documentsProcess mapsUAT checklists
How I Work
Problem first, feature second
I start with the real business problem. Then I map the current process, identify gaps, document requirements, and validate the solution with users before delivery is considered complete.
Fit and Tools
Where this profile matches
Especially useful in organizations with many stakeholders, legacy processes, and a need to modernize digital platforms.
Contexts
Digital transformation
Platform migrations and workflow modernization.
Marketing and growth teams
Acquisition, retention, budget, KPI, and reporting work.
Sports and entertainment
Football, betting, casino, and engagement-product contexts.
Operations-heavy companies
Many stakeholders, legacy processes, recurring requests, and delivery dependencies.
Tools
Delivery
JiraOdoo Project
Analytics
GA4 / certifiedPower BI / certified
Data and automation
Excel / advancedSQL basics / certified
Platforms
WordPressPlatform migrations
Professional contact
Get in touch.
For requirements, process improvement, platform delivery, or analytics work, use email as the primary contact channel.
Manual review notes
- GAP. REVIEW MANUALLY: {formal UAT ownership evidence}
- GAP. REVIEW MANUALLY: {actual user story and acceptance criteria samples}
- GAP. REVIEW MANUALLY: {functional and non-functional requirements examples}
- GAP. REVIEW MANUALLY: {current-state process map artifact}
- GAP. REVIEW MANUALLY: {migration testing evidence}
- GAP. REVIEW MANUALLY: {named user validation examples}
- GAP. REVIEW MANUALLY: {Trello, Confluence, Lovable, Supernova, Zapier, CRM interview-ready evidence}
- GAP. REVIEW MANUALLY: {ecommerce, SaaS, membership, community, and CRM context evidence}