Pyramidion Solution Project Management
Official Project Initiation to Development Workflow (Internal SOP)
Phase 1: Post Sign-Off – Client Onboarding
Once the project is initiated, schedule a kickoff call with the client team
Participants to be Included in the Kick-Off Call
- Project Manager / BA
- CTO / Management Representative
- Designer (if the project has design works included)
- Assigned Developers (optional but recommended)
Design Discussion (If Included)
- Brand understanding
- Target audience clarity
- Competitor references
- Color scheme & typography
- Layout preferences
- Post call share the moodboard to the client
Logo Condition: If client does not have logo → Quote additional cost based on Iteration or Discuss with Sales team.
If Figma Exists (Client already has the Design Ready)
- Map Figma screens vs agreed scope
- Identify out-of-scope features
- Mark as Within Scope OR CR
- Document in PM Sheet
- Discuss with Product Owner/CTO - confirm the CR's Efforts and share it with client as email
Phase 2: Scope Writing (Parallel Process)
OThe Scope Writing (or Scope Grooming) phase typically requires 3–7 working days, depending on project complexity. This timeline will be communicated to the client in advance.
| Scope Discussion | 3 / 5 / 7 Working Days |
| Internal Draft Preparation | The first half of the scope document will be prepared and reviewed internally. |
| Client Scope Review Call | A review call will be scheduled with the client to walk them through the drafted scope in detail. |
| Change Request Identification | Any additional requirements or modifications identified during the discussion will be immediately classified as Change Requests (CRs) and communicated clearly on the spot. |
| Scope Completion | Once alignment is achieved, the remaining portion of the scope will be completed and finalized. |
| Formal Scope Approval | The consolidated scope document will then be shared for formal approval before proceeding to the next phase. |
Phase 3: Story & Scope Confirmation
- Final scope document emailed.
- Written confirmation mandatory.
- CRs documented with cost & timeline impact.
- CRs discussed internally with CTO before confirming to client.
- Take up a call with client and CTO and discuss on the CRs and finilize the items
UI Work officially starts only after full written approval.
If any Change Request (CR) item is mutually agreed upon for inclusion, it will be scheduled under Post-Delivery execution and will be undertaken only after project completion and milestone clearance.
Phase 4: UI Design Phase
- Weekly progress design update to be displayed in the client call
- Weekly report shared via email.
- Internal review before client presentation.
- Mention Client to drop comments directly in Figma.
- Review the UI completely if that alligns with the given scope then share it to client
- IF CRs are mentioned by the client - document it & approved before execution.
After UI confirmation → Development officially begins.
- CRs that client agreed, should be documented and shared to the client before Commencement
- CRs that Our company accpected as complementry service, should be document and shared to the client before Commencement
- Client confirmed design and Story Scope document must be shared to the client before deevlopment Commencement
Phase 5: Sprint Planning
| Sprint | Objective | Duration |
|---|---|---|
| Sprint 1 | Base setup, onboarding, dashboard (lightweight) | 2 Weeks |
| Sprint 2-3-4.. | Core functional modules - but still lightwithted (But Should give Shock Value) | 2 Weeks Each |
| Final Sprint | Complete deliverals, Optimization, Notifications, Integrations pending from the previous sprints | 2 Weeks |
- 1 Sprint = 2 Weeks (10 Working Days)
- Under 4 weeks → 1 Sprint = 1 Milestone
- Above 4 weeks → 2 Sprints = 1 Milestone
- Discuss milestone plan with management before sharing.
Phase 6: Development Start & Reporting
-
Requirement document to be shared with the client - this can be done during the Scope or UI stage View Sample
-
Third-party dependencies listed.
-
Weekly/Bi-weekly email report (What was done / What will be done next) View Sample
-
App Store & Play Store account setup with client. View Process
-
If Company → DUNS required. View Sample
-
If Individual → Listed in personal name. View Sample
Phase 7: SCRUM Execution
| Activity | Description |
|---|---|
| Daily Standup | Schedule when all developers are available (morning & mid-day check-ins recommended). |
| Issue Resolution | Address dependencies or blockers immediately. |
| SCRUM Format | a. What was done yesterday b. What's planned for today |
| Sprint Reviews | Sprint explained every Monday. Weekend: Sprint progress review. |
| Pre-Demo Check | BA reviews all completed modules one day before sprint end. |
| Client Demo | Conducted on day 11 of the sprint (10 working days + 1 demo day). |
| Monitoring | Ensure all devs fill daily timesheets and tasks are meaningful. |
Final Project Flow Summary
Sign Off → Initiation Call → Scope Finalization → UI Confirmation → DB Schema → Sprint Planning → Development → Weekly Reports → Client Demo → Completion