Project Manager
Biya
Runs Midwave AI engagements end to end, so clients always know exactly where things stand.
Remote · Pakistan
Taking on new engagements
Weekly
Written status, same day
Slice-based
Demoable work every sprint
Risk-first
Escalated early, in writing
Profile
About Biya
Biya turns a signed scope into a schedule the team can actually hold. She breaks work into slices with real acceptance criteria, protects the critical path, and surfaces risk while it is still cheap to solve. Clients tend to describe working with her as the first time a project felt calm.
She is also the translation layer between a client's language and an engineering backlog: what the business needs, written as work a developer can pick up without a meeting. Status arrives on the same day every week, whether the news is good or not.
Focus areas
A risk you raise in week two is a conversation. The same risk in week ten is a crisis.
Delivery playbook
How an engagement actually runs
01
Kickoff & discovery
Goals, constraints, and success metrics captured in one document everyone signs off on.
Scope document agreed
Success metrics defined
Comms plan and cadence set
02
Plan & sequence
Work sliced into demoable increments, ordered so the riskiest unknowns resolve first.
Milestone map with dates
Dependencies mapped
Risk register with owners
03
Build & demo
Sprints that end in working software, a written update, and a short list of decisions needed from you.
Sprint demo each cycle
Weekly written status
Change requests priced before they land
04
Harden & launch
Test passes, performance and accessibility checks, then a go-live with a rehearsed rollback.
QA pass signed off
Go-live checklist complete
Rollback path tested
05
Support & iterate
Post-launch monitoring, a retro that produces actual changes, and a plan for the next phase.
Retro actions assigned
Monitoring and alerts live
Next-phase backlog drafted
01
Kickoff & discovery
Goals, constraints, and success metrics captured in one document everyone signs off on.
Scope document agreed
Success metrics defined
Comms plan and cadence set
02
Plan & sequence
Work sliced into demoable increments, ordered so the riskiest unknowns resolve first.
Milestone map with dates
Dependencies mapped
Risk register with owners
03
Build & demo
Sprints that end in working software, a written update, and a short list of decisions needed from you.
Sprint demo each cycle
Weekly written status
Change requests priced before they land
04
Harden & launch
Test passes, performance and accessibility checks, then a go-live with a rehearsed rollback.
QA pass signed off
Go-live checklist complete
Rollback path tested
05
Support & iterate
Post-launch monitoring, a retro that produces actual changes, and a plan for the next phase.
Retro actions assigned
Monitoring and alerts live
Next-phase backlog drafted
Weekly written status
Progress, risks, and the decisions we need from you — the same day every week, good news or bad.
Sprint demo
Real software in a real browser at the end of every cycle. No slide-only progress.
Living milestone map
One shared plan that always reflects reality, so nobody is working from a stale document.
Capabilities
Where the depth is
The work Biya is trusted with on an engagement, and how confident we are handing each of them over.
Delivery planning
94%Slices, dependencies, and a critical path that is defended.
Requirements & backlog
92%Business intent rewritten as tickets with clear acceptance criteria.
Risk & issue management
93%Named owners, mitigation options, and dates — not a colour-coded register.
Stakeholder communication
95%One update, one channel, one predictable cadence.
QA coordination
88%Test passes planned into the sprint rather than bolted on at the end.
Way of working
How Biya works
01
Agree the definition of done
Each milestone gets written acceptance criteria before a ticket is opened against it.
02
Sequence for risk
The riskiest and most-coupled work goes first, so surprises land while there is still room to react.
03
Demo every slice
Working software at the end of every sprint. Feedback while it is still cheap to act on.
04
Release with a checklist
A written go-live checklist, a rollback path, and a named owner for every item on it.
Toolbox