Product

Executive Summary¶

This 30/60/90-day plan sets out the Product Management team's priorities from Day 1 of the new CDO's tenure (14 April 2026). The team operates under Chief Product Officer Rizwan Zafar and is responsible for translating Simpaisa's commercial corridor strategy into engineered, compliant, and deliverable product requirements.

Three issues require immediate remediation: (1) inconsistent Business Requirements Documents (BRDs) across corridors and operators, (2) the absence of a formal Definition of Done (DoD) that satisfies SDLC v2.0 Phase 2, and (3) an informal roadmap that cannot be used for resourcing or board-level reporting. By Day 90 the team will have a published roadmap, measurable acceptance criteria on every active Story, CCQ (Coverage, Cost, Quality) targets embedded in all corridor Epics, and a live partner status API for Pay-In.

Team Overview¶

Role	Name
Chief Product Officer	Rizwan Zafar
Product Manager	Shaheer Javed
Product Manager	Muhammad Mubeen Anwar
Product Manager	Shayan Rasheed
Product Manager	Muhammad Taimoor Bhatti
Associate Product Manager	Munim Ur Rehman
Associate Product Manager	Simra Yousuf
Associate Product Manager	Shehzada Muhammad Shehryar

Simpaisa operates corridors across Pakistan, Bangladesh, Nepal, Canada, UAE, and Iraq, processing in excess of $1 billion annually across Pay-In, Pay-Out, and Remittance product lines. Product Managers are the single point of accountability for corridor requirements from Epic creation through to Engineering handoff at the G2 Gate (Corridor Design).

30-Day Plan: April 14 - May 14 2026¶

Objectives¶

Stabilise the product delivery foundation. Audit what exists, close the standards gap, and establish the working practices that SDLC v2.0 Phase 2 demands before any new corridor work enters the engineering backlog.

Story Lifecycle¶

All Stories created from 14 April 2026 must follow this lifecycle without exception. No Story enters the backlog without passing the Acceptance Criteria Review gate.

flowchart LR
    A[Idea] --> B[Epic]
    B --> C[Story Writing]
    C --> D{Acceptance Criteria\nReview}
    D -- Rejected --> C
    D -- Approved --> E[Backlog]
    E --> F[In Development]
    F --> G[QA]
    G --> H[Done]

Deliverables¶

#	Deliverable	Owner	Due	Success Metric
1	Backlog audit - review all open Epics and Stories; flag any Story missing acceptance criteria, fund flow diagrams, or business logic	Rizwan Zafar + all PMs	28 Apr 2026	100% of Stories assessed; audit report published to Confluence
2	BRD template v2 - a single, standardised BRD template replacing ad-hoc variants; includes fund flow diagram, business logic, edge cases, and CCQ placeholder	Shaheer Javed	25 Apr 2026	Template ratified by CPO and CSNO Bachir Njeim; adopted for all new work from 26 Apr
3	Definition of Done (DoD) - published - formal DoD aligned to SDLC v2.0 Phase 2; no Story enters backlog without: acceptance criteria, fund flow diagram, business logic, and CCQ target where applicable	Rizwan Zafar	30 Apr 2026	DoD published to Confluence; signed off by CDO and CSNO
4	Product roadmap 2026 - first draft - structured Epics by corridor and product line (Pay-In, Pay-Out, Remittance); sequenced by quarter; published to Confluence	Rizwan Zafar	9 May 2026	Roadmap visible to all senior stakeholders on Confluence; no undocumented Epics in flight
5	G2 Gate participation model - define Product's co-ownership responsibilities at G2 (Corridor Design); checklist of artefacts Product must produce before Engineering can proceed	Shayan Rasheed	14 May 2026	G2 checklist embedded in SDLC v2.0 process documentation
6	PM-to-APM pairing - each Product Manager formally mentors one Associate PM on BRD authoring and acceptance criteria standards	Rizwan Zafar	14 May 2026	All APMs have authored at least one complete Story with acceptance criteria by 14 May

60-Day Plan: May 15 - June 13 2026¶

Objectives¶

Move from standards adoption to product execution. Define the transaction state model per product line, design the partner status API, and produce full requirements for the Iraq and Saudi Arabia corridor expansion.

Deliverables¶

#	Deliverable	Owner	Due	Success Metric
1	Transaction state definitions - Pay-In - owner-authored state machine covering all states from initiation to settlement; agreed with Engineering and CSNO	Muhammad Mubeen Anwar	30 May 2026	State definitions published; no ambiguous states remain in the Pay-In flow
2	Transaction state definitions - Pay-Out and Remittance - same deliverable for Pay-Out and Remittance product lines	Shaheer Javed + Shayan Rasheed	6 Jun 2026	State definitions published for both product lines
3	Partner status API design - Pay-In - design document specifying 5-7 external-facing states, request/response schema, error codes, and versioning approach; input to OpenAPI spec	Muhammad Taimoor Bhatti	31 May 2026	Design reviewed and approved by Engineering lead; OpenAPI spec drafted
4	Iraq corridor BRD and fund flow - complete BRD using v2 template; fund flow diagram covering all operator integrations in scope; acceptance criteria on all associated Stories	Munim Ur Rehman (lead APM) + Rizwan Zafar	7 Jun 2026	BRD accepted at G2 Gate; all Stories enter backlog
5	Saudi Arabia corridor requirements - initiation - scope document, preliminary fund flow, identified operator integrations; CCQ targets set for the corridor Epic	Simra Yousuf (lead APM) + Shayan Rasheed	13 Jun 2026	Scope document approved by CPO; corridor Epic created with CCQ targets
6	Stories-with-acceptance-criteria rate - 60-day checkpoint - measure and report the percentage of Stories in the active backlog that meet the DoD	Rizwan Zafar	13 Jun 2026	Target: 80% of active Stories fully compliant with DoD

90-Day Plan: June 14 - July 13 2026¶

Objectives¶

Embed CCQ thinking across all active Epics, demonstrate measurable improvement in delivery quality, and take the partner status API live for Pay-In. By Day 90 the Product team operates as a high-performance function with full traceability from corridor commercial case to delivered feature.

Deliverables¶

#	Deliverable	Owner	Due	Success Metric
1	CCQ targets in all active Epics - Coverage, Cost, and Quality targets defined and documented in every active corridor Epic; CCQ embedded as a mandatory field in the BRD template	Rizwan Zafar	28 Jun 2026	100% of active Epics contain CCQ targets; verified by audit
2	Partner status API - Pay-In - live - OpenAPI spec finalised, Engineering build complete, integration tested with at least one partner; external documentation published	Muhammad Taimoor Bhatti + Engineering	30 Jun 2026	API live in production; partner confirms receipt of status events
3	Product metrics dashboard - Confluence or BI dashboard tracking: % Stories with acceptance criteria, Epic-to-first-Story time, corridor launch time, and backlog health	Shehzada Muhammad Shehryar (lead APM) + Rizwan Zafar	7 Jul 2026	Dashboard live; reviewed in weekly product leadership meeting
4	Iraq corridor - Engineering handoff complete - all Stories accepted at G2, Engineering sprint-planned, first Sprint underway	Rizwan Zafar	30 Jun 2026	Iraq corridor in active development sprint
5	Saudi Arabia corridor BRD complete - full BRD, fund flow, and acceptance criteria for Saudi corridor; G2 Gate passed	Simra Yousuf + Shayan Rasheed	13 Jul 2026	BRD at G2; Saudi corridor Stories in backlog
6	90-day retrospective and roadmap refresh - retrospective on delivery against this plan; roadmap updated for Q3 2026; lessons from Iraq and Saudi Arabia corridor work incorporated	Rizwan Zafar	13 Jul 2026	Retrospective report published; roadmap updated on Confluence

Gantt Chart¶

gantt
    title Product Management - 30/60/90 Day Plan
    dateFormat  YYYY-MM-DD
    axisFormat  %d %b

    section 30-Day - Foundation
    Backlog audit                        :done,    p1,  2026-04-14, 2026-04-28
    BRD template v2                      :done,    p2,  2026-04-14, 2026-04-25
    Definition of Done - published       :done,    p3,  2026-04-14, 2026-04-30
    Product roadmap 2026 - first draft   :         p4,  2026-04-21, 2026-05-09
    G2 Gate participation model          :         p5,  2026-04-21, 2026-05-14
    PM-to-APM pairing                    :         p6,  2026-04-14, 2026-05-14

    section 60-Day - Execution
    State definitions - Pay-In           :         p7,  2026-05-15, 2026-05-30
    State definitions - Pay-Out and Remittance :   p8,  2026-05-15, 2026-06-06
    Partner status API design            :         p9,  2026-05-15, 2026-05-31
    Iraq corridor BRD and fund flow      :         p10, 2026-05-15, 2026-06-07
    Saudi Arabia - scope initiation      :         p11, 2026-05-20, 2026-06-13
    DoD compliance checkpoint            :milestone, p12, 2026-06-13, 1d

    section 90-Day - Embed and Launch
    CCQ targets in all active Epics      :         p13, 2026-06-14, 2026-06-28
    Partner status API - Pay-In - live   :         p14, 2026-06-01, 2026-06-30
    Product metrics dashboard            :         p15, 2026-06-14, 2026-07-07
    Iraq corridor - Engineering handoff  :milestone, p16, 2026-06-30, 1d
    Saudi Arabia BRD complete            :         p17, 2026-06-14, 2026-07-13
    90-day retrospective and roadmap refresh :milestone, p18, 2026-07-13, 1d

Success Metrics¶

The following metrics will be tracked from Day 1 and reported monthly to the CDO.

Metric	Baseline (Apr 2026)	30-Day Target	60-Day Target	90-Day Target
% Stories with acceptance criteria meeting DoD	To be established in backlog audit	50%	80%	95%
Time from Epic creation to first Story in backlog (days)	To be established	Measured	Measured	Reduction of 25% vs baseline
Time from G2 Gate pass to corridor launch (days)	To be established	Measured	Measured	Reduction of 20% vs baseline
% active Epics with CCQ targets defined	0%	0% (standards published)	50%	100%
Open BRDs using v2 template	0%	100% of new BRDs	100%	100%

Dependencies and Risks¶

Item	Detail
SDLC v2.0 Phase 2	Product's DoD and acceptance criteria standards must align to the published SDLC v2.0 Phase 2 gate definitions. Any changes to Phase 2 gates require a corresponding update to the Product DoD.
CSNO alignment	Bachir Njeim (CSNO) co-owns the G2 Gate. BRD template v2 and the DoD must be ratified by CSNO before adoption. Product and CSNO should hold a joint working session in Week 1.
Engineering capacity for Iraq and Saudi Arabia	Iraq corridor handoff (30 Jun) is contingent on Engineering sprint capacity. Rizwan Zafar to confirm Engineering resourcing with CDO by 30 April.
Partner availability for status API testing	At least one Pay-In partner must be available for integration testing of the status API by mid-June. Shaheer Javed to identify and confirm a partner by 31 May.
APM capability uplift	Three APMs are expected to produce BRD-standard artefacts by Day 90. If capability gaps are identified in the audit, targeted coaching or external training must be sourced by 30 April.