Ali Zaman, Senior Business Analyst (PMO)From business problem to production release.
I turn complex business needs into requirements engineers can build and test, then see the work through to a stable release. Currently at ibex, on enterprise contact-center and customer engagement platforms.
- Experience
- 3+ years in product and delivery
- Focus
- Enterprise platforms, SaaS and AI products
- Based in
- Pakistan, open to remote
01: Profile
Most delivery problems start as unclear requirements.
I work where business intent has to become something a team can commit to. That takes the business context to ask the right questions, the product judgement to decide what matters first, enough technical depth to work it through with architects and engineers, and the delivery discipline to get it into production.
01
Business
Stakeholder elicitation, process mapping, scope and impact analysis.
02
Product
MVP definition, roadmaps, prioritisation and user stories with acceptance criteria.
03
Technology
A computer science foundation and working fluency in APIs, microservices and cloud delivery.
04
Delivery
Sprint planning, release tracking, risk and escalation, QA and UAT through to production.
02: Expertise
What I'm brought in to do.
Four areas I own end to end. Select one to see what it covers and what it produces.
Business analysis and requirements engineering
Eliciting requirements from business and client stakeholders and structuring them into documentation that engineering, QA and the client can all work from. When scope changes, I assess the impact before it reaches the sprint.
Typical deliverables
- BRD and SRS
- Functional and non-functional requirements
- Use cases and process flows
- User stories and acceptance criteria
- Requirement traceability
- Change request and impact analysis
Enterprise platform delivery
Requirements and delivery governance for large-scale contact-center and omnichannel customer engagement platforms, across multiple client implementations in a microservices environment. From scoping to release tracking and escalation, keeping production rollouts aligned with client SLAs.
Typical deliverables
- SOWs and scoped delivery plans
- Feature analysis documents
- Workflow mapping
- Release tracking
- Risk and escalation management
- UAT and post-deployment support
SaaS and AI product delivery
Discovery through launch for SaaS, web and mobile products in healthcare, education, FinTech, e-commerce and productivity, including AI-powered products built on third-party LLM APIs. Defining MVP scope, owning roadmaps and backlogs, and running the sprints that ship them.
Typical deliverables
- Product discovery
- MVP scoping (MoSCoW)
- Roadmaps and backlog management
- Wireframes and ERDs
- Subscription and payment workflows
- Release management
Project and team leadership
Running cross-functional delivery with design, engineering and QA, including distributed teams. Keeping a full view of each project through planning and status reporting, and helping junior team members grow.
Typical deliverables
- Project plans
- Scrum and Kanban ceremonies
- Project status reporting
- Stakeholder updates
- Risk management
- Team mentoring
03: Approach
How a requirement becomes a release.
Six stages, each with something concrete at the end of it. The documents are not the goal; they are how a team stays aligned on what is being built and why.
01
Understand
Business objectives, constraints and the current-state process, from the people who live it.
Outputs: Stakeholder map, AS-IS flows
02
Structure
Needs turned into scope the whole team can read the same way.
Outputs: BRD, SRS, user stories, acceptance criteria
03
Design
Solution approach worked through with architects and engineers.
Outputs: TO-BE workflows, use cases, wireframes, ERDs
04
Align
Estimates, sprint inputs and change control agreed before work starts.
Outputs: Delivery plan, impact analysis, risk log
05
Validate
QA coordination and UAT against the requirements that were agreed.
Outputs: UAT scenarios, traceability, sign-off
06
Deliver
Release tracking, communication and post-deployment support until it is stable.
Outputs: Release notes, issue resolution
04: Play
Prioritise the backlog.
A two-minute exercise in the work I do every sprint. You get a real-world brief at random. Sort the requirements using MoSCoW, then compare your call with mine and the reasoning behind it.
05: Experience
An engineering foundation, applied to product and delivery.
I studied computer science and moved from building software to shaping it: from project coordination into product and project management, and now enterprise business analysis.3+ years across product-company and enterprise environments, and the engineering background still shapes how I work with architects and developers.
ibex
Global customer experience (CX) outsourcing company · On-site
- Senior Business Analyst (PMO)
Requirements engineering and PMO governance for enterprise contact-center and digital engagement solutions. Working with enterprise clients, solution architects, engineering, QA and operations across multiple client implementations, from scope validation and change requests through UAT, release tracking and post-deployment support.
ZAPTA Technologies (Pvt.) Ltd
AI and custom software development company · On-site
- Project Manager / Team Lead
- Associate Project Manager
- Technical Project Coordinator
Delivered SaaS, web and mobile products for clients across the Middle East, US and UK, in healthcare, education, FinTech, e-commerce and productivity. Grew from coordinating technical delivery to leading projects and teams end to end: discovery, roadmaps, sprints, releases, status reporting and mentoring junior team members.
Education
BS Computer Science
University of Engineering and Technology, Peshawar
Certifications
- Foundations of Project ManagementGoogle
- Product Management BasicsPendo
- AI for Product ManagementPendo
- Project Management 101ibex
06: Toolkit
Technical fluency, used for decisions.
Enough depth to read an API contract, question an estimate and follow a deployment. The aim is better product and delivery decisions, not writing production code.
- Planning and delivery
- Jira · Confluence · Notion · ClickUp · NiftyPM · Asana · Trello
- Process and solution modelling
- Miro · FigJam · Draw.io · Boardmix · Microsoft Visio · ERDs · Use case and context diagrams
- APIs and engineering collaboration
- REST APIs · Postman · Swagger · GitHub · GitLab · Bitbucket
- Quality and acceptance
- UAT · Manual QA · Regression and sanity testing · Test case documentation · Bug reporting
- Cloud, release and monitoring
- AWS · Render · Supabase · Hetzner · Sentry
- Web and data foundations
- React · Next.js · Node.js · PostgreSQL · Firebase · Flutter
- CRM and analytics
- HubSpot · Salesforce · Perfex CRM · Zapier · Google Analytics · Hotjar
- AI in products
- OpenAI, Gemini and DeepSeek API integrations · AI-assisted development tools