📖 How to Read This Tracker — Overview for Sir Saleem
Click to Expand Overview
How does the document sequence work?
This tracker organizes all 77 pre-development documents into 6 weeks. Each document is placed in the week where it is logically required — not by ID number order. Think of it like building a house: you pour the foundation first, then the walls, then the roof. You cannot reverse the sequence.
The document ID numbers (DOC-60, 61, 62, 63) are simply catalogue reference numbers assigned during planning — they do NOT mean those documents belong in the same week. Each goes where its inputs are ready.
DOC-60 — Project Charter
📅 Week 1 · Completed June 5, 2026
✅ Placed in Week 1 because it is the founding document — it formally authorizes the project. Nothing can begin without this signed document.
DOC-61 — RACI Matrix
📅 Week 1 · Completed June 5, 2026
✅ Placed in Week 1 because it assigns responsibilities to every team member. Without this, the team cannot work efficiently.
DOC-63 — Risk Register
📅 Week 1 · Completed June 5, 2026
✅ Placed in Week 1 because risks must be identified before any major decision is made. Early risk awareness protects the project and the investment.
DOC-62 — Sprint Plan
📅 Week 4 · Begins June 23, 2026
⏳ Placed in Week 4 because a Sprint Plan requires the full feature list (PRD) AND all wireframes to be approved first. Creating it earlier would be guesswork.
Core Principle: Every document is created only when all its inputs exist. This disciplined sequencing is what separates a professional software project from a failed one.
🔄 Progress & Timeline Update (Reported to Sir Saleem on June 13): Project planning and document cataloging commenced on June 4, 2026. Week 1 (June 4–8) focused on setup and planning. Product discovery and core business/architecture decisions (including the recommendation to split the Captain and Customer applications, now updated to support motorcycle riders for the new Parcel Delivery service) were finalized in Week 2 (June 9–13). Week 3 (June 14–20) has been dedicated to mapping complex user journeys and flows for the PRD and Flow Diagrams (DOC-18) for all three services to ensure a bulletproof UX before wireframing. Development start date remains July 14, 2026.
📅 Updated Project Timeline (Click on any week to navigate)
✅
Week 1
June 8–14
COMPLETED
3
Docs Done
🔵
Week 2
June 15–21 · CURRENT
IN PROGRESS
10
Docs In Focus
3
Week 3
June 22–28
UPCOMING
11
Docs Planned
4
Week 4
June 29–July 5
UPCOMING
12
Docs Planned
5
Week 5
July 6–12
UPCOMING
18
Docs Planned
6
Week 6
July 13–19
UPCOMING
16
Docs Planned
🚀
Dev Start
July 20, 2026
Sprint 0
GO!
Development
Week 1 — Completed
✅ COMPLETED — Project set up and master document catalog finalized
📁 Project Setup & Governance (DOC-60, 61, 63)
DOC-60
Project Charter
Why here: Formally authorizes the project — the very first official document. No other work can start without this.
Owner: PM — Syed Nizam Uddin
P1✅ Done June 5
DOC-61
RACI Matrix
Why here: Defines who is Responsible for every task. Without this, no one knows their role.
Owner: PM
P1✅ Done June 5
DOC-63
Risk Register
Why here: Risks must be identified EARLY before decisions are made. Finding risks late is expensive.
Owner: PM
P1✅ Done June 5
Week 2 — Completed
✅ COMPLETED — Reported to Sir Saleem on June 13, 2026
📁 Product Discovery (DOC-01 to DOC-08) — Understanding the Problem & Users
DOC-01
Problem Statement
Why here: Defines the exact problem Pickia solves. EVERYONE must agree on this before designing anything.
Owner: PM
P1✅ Done June 10
DOC-03
User Personas (4 personas)
Why here: All UX and feature decisions refer back to these personas. Must exist before design starts.
Owner: PM
P1✅ Done June 11
DOC-04
Jobs To Be Done (JTBD)
Why here: Captures WHY users use Pickia — deeper than features. Essential for UX decisions.
Owner: PM
P1✅ Done June 11
DOC-05
Empathy Map
Why here: Helps team feel what users feel before designing. Prevents tone-deaf UX decisions.
Owner: PM + UX
P2✅ Done June 12
DOC-06
Customer Journey Map
Why here: Maps every touchpoint from problem to loyal user. Guides UX and marketing strategy.
Owner: PM + UX
P1✅ Done June 12
DOC-07
Pain Points & Opportunity Map
Why here: Shows exactly where current solutions fail and how Pickia wins. Great for Sir Saleem's review.
Owner: PM
P2✅ Done June 13
DOC-08
Value Proposition Canvas & Naming Report
Why here: Proves Pickia's features match user needs, and includes naming research for Pakistan & Middle East markets.
Owner: PM
P2✅ Done June 13
📁 Business Requirements & Architecture (DOC-09, DOC-N-A, DOC-N-E)
DOC-09
Business Requirements Document (BRD)
Why here: Defines business goals and KPIs. Must come before detailed feature requirements (PRD).
Owner: PM + CEO
P1✅ Done June 13
DOC-N-A
Driver Earnings Model (10% Commission) ⭐ NEW
Why here: Core business logic (10% commission model). Developers need this before building payment module. Now updated to include motorcycle riders.
Owner: CEO + PM
P1NEW✅ Done June 13
DOC-N-E
App Architecture Split Decision (Captain vs Customer App) ⭐ NEW
Why here: Strategic technical decision to build separate Driver (Captain) and Customer apps, validated against Uber/Careem models. Now updated to support motorcycle riders for the new Parcel Delivery service.
Owner: CTO + PM
P1NEW✅ Done June 13
Week 3 — In Progress · Current Week
🔵 IN PROGRESS — Market Research Finalized · Flow Diagrams & PRD Mapping Underway
📁 Requirements Documents (DOC-10 to DOC-16) — What Does the App Do?
DOC-02
Market Research Report
Why here: Validates market size, competitor analysis, and Pakistan transport behavior. Worked on in Week 2, finalized here.
Owner: PM + COO
P1✅ Done June 16
DOC-10
Product Requirements Document (PRD)
Why here: Full feature list with user stories and acceptance criteria. Currently mapping use cases and customer journeys for all three services (Goods, Family, and Parcel).
Owner: PM
P1🔵 In Progress
DOC-11
Functional Requirements Spec (FRS)
Why here: Detailed behavior of every feature — input, output, what happens. Developers cannot code without this.
Owner: PM + CTO
P1🔵 In Progress
DOC-12
Non-Functional Requirements (NFR)
Why here: Performance, security, and uptime targets. CTO needs this to design the correct architecture.
Owner: CTO
P1⏳ Pending
DOC-13
Feature Priority Matrix (MoSCoW)
Why here: Classifies every feature as Must/Should/Could/Won't. Prevents scope creep during development.
Owner: PM
P1⏳ Pending
DOC-14
Scope Document
Why here: Formal definition of what is IN and OUT of Phase 1. Prevents arguments later.
Owner: PM
P1⏳ Pending
DOC-15
Assumptions & Constraints Log
Why here: Documents what we assume to be true. Tracks constraints (budget, Android-only).
Owner: PM
P2⏳ Pending
DOC-16
Glossary of Terms
Why here: Common language for the whole team. Prevents misunderstandings between PM, developers, and designers (updated with Parcel terms).
Owner: PM
P2⏳ Pending
📁 UX Foundation & Logic (DOC-17, DOC-18, DOC-N-B)
DOC-17
Information Architecture (IA)
Why here: Shows ALL screens and how they connect. Must exist BEFORE wireframes.
Owner: UX + CTO
P1⏳ Pending
DOC-18
User Flow Diagrams — All Major Flows
Why here: Step-by-step visual of every user path (Goods, Family, and Parcel Delivery). Currently being created by team. ← CURRENT WORK IN PROGRESS
Owner: UX + PM
P1🔵 Currently Working
DOC-N-B
Pricing Calculator Logic ⭐ NEW
Why here: Exact fare formula (base fare + per km + floor charge for trucks, and base fare + per km for motorcycle parcels). Backend developers MUST have this before building the booking engine.
Owner: CEO + PM + CTO
P1NEW⏳ Pending
Week 4 — Upcoming
⏳ NOT YET STARTED — Begins June 23, 2026
📌 Why DOC-62 (Sprint Plan) is in THIS week: The Sprint Plan is created here because by Week 4, all requirements AND wireframes will be done. Now the PM and CTO can break down the work into 2-week sprints with confidence. Not before.
📁 UX Design — Visual Screens
DOC-19
Wireframes — Low Fidelity (All screens)
Why here: Simple black & white sketches of every screen — comes AFTER flow diagrams (DOC-18) are approved.
Owner: UX
P1⏳ Pending
DOC-20
Wireframes — Mid Fidelity
Why here: Detailed screens with button names and content — built on top of low-fi wireframes.
Owner: UX
P1⏳ Pending
DOC-21
Clickable Prototype (Figma)
Why here: Interactive mockup for user testing — created from mid-fi wireframes.
Owner: UX
P1⏳ Pending
DOC-22
User Testing Report (5–10 real users)
Why here: Test the prototype with real users BEFORE high-fidelity design — saves expensive redesign time.
Owner: PM + UX
P1⏳ Pending
DOC-23
High Fidelity UI Designs
Why here: Final pixel-perfect designs — created AFTER user testing confirms the wireframes are correct.
Owner: UX
P1⏳ Pending
DOC-24
Design System Document
Why here: Color palette, fonts, and reusable UI components — created alongside hi-fi designs.
Owner: UX + CTO
P1⏳ Pending
📁 Technical Architecture — How Is the System Built?
DOC-30
System Architecture Diagram
Why here: Visual map of all system components — CTO designs this AFTER knowing all features from PRD.
Owner: CTO
P1⏳ Pending
DOC-31
Technical Stack Document
Why here: Final technology decisions (Flutter/React Native, Node.js, AWS etc.) — confirmed after architecture is clear.
Owner: CTO
P1⏳ Pending
📁 Project Management (DOC-62, 66) — Now Ready Because Requirements Are Done
DOC-62
Sprint Plan (Week-by-week dev schedule)
Why here (NOT Week 1): Sprint Plan requires knowing ALL features (from PRD) AND all screens (from wireframes). Only now is it possible to break development into logical sprints.
Owner: PM + CTO
P1⏳ Pending
DOC-66
Definition of Done
Why here: Exact criteria for what "complete" means for each feature — defined before development starts.
Owner: PM + CTO
P1⏳ Pending
DOC-N-C
Onboarding Screen Flow ⭐ NEW
Why here: First-time user experience design — created alongside wireframes so onboarding is part of the app flow.
Owner: UX + PM
P1NEW⏳ Pending
DOC-N-D
Admin Panel Requirements ⭐ NEW
Why here: Defines what the admin dashboard shows — created alongside other requirements so developers know the full scope.
Owner: PM + CTO
P1NEW⏳ Pending
Week 5 — Upcoming
⏳ NOT YET STARTED — Begins June 30, 2026
📁 Technical Deep-Dive (DOC-32 to DOC-41)
DOC-32
Database Schema (ERD)
Owner: CTO + Backend
P1⏳ Pending
DOC-33
API Design Document
Owner: CTO + Backend
P1⏳ Pending
DOC-34
Data Flow Diagram (DFD)
Owner: CTO
P1⏳ Pending
DOC-35
Sequence Diagrams (Critical flows)
Owner: CTO
P1⏳ Pending
DOC-36
State Diagrams (Booking, Driver, Trip)
Owner: CTO
P1⏳ Pending
DOC-37
Third Party Integrations Document
Owner: CTO
P1⏳ Pending
📁 Process Flowcharts (DOC-42 to DOC-53)
DOC-42
Business Process Flow
Owner: PM + COO
P1⏳ Pending
DOC-43
Customer Booking Flow — Goods Transport
Owner: PM + UX
P1⏳ Pending
DOC-44
Customer Booking Flow — Family Transport
Owner: PM + UX
P1⏳ Pending
DOC-45
Driver Onboarding Flow
Owner: PM + COO
P1⏳ Pending
DOC-46
Driver Booking Acceptance Flow
Owner: CTO + PM
P1⏳ Pending
DOC-47
Payment Processing Flow
Owner: CTO
P1⏳ Pending
DOC-48
Cancellation & Refund Flow
Owner: PM + CTO
P1⏳ Pending
DOC-49
Dispute Resolution Flow
Owner: PM + COO
P2⏳ Pending
DOC-52
Pre-Booking Confirmation Flow
Owner: PM + CTO
P2⏳ Pending
DOC-53
Error & Edge Case Flows
Owner: CTO + PM
P2⏳ Pending
DOC-40–41
Performance Benchmarks + Scalability Plan
Owner: CTO
P2⏳ Pending
Week 6 — Upcoming
⏳ NOT YET STARTED — Begins July 7, 2026
📁 Security + Infrastructure (DOC-38, 39)
DOC-38
Security Architecture Document
Owner: CTO
P1⏳ Pending
DOC-39
Infrastructure & DevOps Plan (AWS)
Owner: CTO + DevOps
P1⏳ Pending
📁 Testing Plans (DOC-54 to DOC-59)
DOC-54–59
Test Plan, Test Cases, UAT Plan, Bug Matrix, Performance & Security Test Plans
Owner: QA + CTO + PM
P2⏳ Pending
📁 Legal & Operations (DOC-70 to DOC-77) — ⚠️ Start Legal Early!
DOC-70
Driver Terms & Conditions
Owner: Legal + CEO
P1⏳ Pending
DOC-71–72
Driver Onboarding Guide + Driver Training Manual (Urdu)
Owner: COO + UX
P1⏳ Pending
DOC-73–74
Customer Terms & Conditions + Privacy Policy (PECA 2016)
Owner: Legal + CEO + CTO
P1⏳ Pending
DOC-75–76
Pricing Policy + Refund & Cancellation Policy
Owner: CEO + PM
P1⏳ Pending
DOC-64–69
Comm. Plan, Change Mgmt, Release Plan, Rollback Plan, Post-Launch Monitoring
Owner: PM + CTO
P2⏳ Pending
After All 77 Documents Are Approved by Co-Founders
🚀 Sprint 0 — Development Officially Begins
Target Date: July 14, 2026 · All 77 documents signed off · Development team onboarded · First sprint commences