Project
Planning
4/25/2025 Malik Waqar Ahmed Aziz 1
Objectives
Where to start?
4/25/2025 Malik Waqar Ahmed Aziz 2
Timeline
(Phases & Deadlines) Time Management
Start End
Phase Time Milestones
Date Date
10 % 10 %
Planning 10% YYYY-MM-DD YYYY-MM-DD Requirements gathered
10 % Planning
Design 15% YYYY-MM-DD YYYY-MM-DD Mockups reviewed
15 %
Design
Development 40% YYYY-MM-DD YYYY-MM-DD Core features built
Dev
15 % Testing
Testing & QA 15% YYYY-MM-DD YYYY-MM-DD UAT passed
Deployment
Deployment 10% YYYY-MM-DD YYYY-MM-DD Live version deployed Maintenance
Maintenance &
Review 10% YYYY-MM-DD Ongoing Bugs tracked & patches released
40 %
4/25/2025 Malik Waqar Ahmed Aziz 3
Time is money
Plan and maintain balance
PROJECT MANAGER
Good Bad
UI/UX Designer
40
35
30
25
20
15
Stakeholders Frontend Dev
10
5
0
QA Engineer Backend Dev
4/25/2025 Malik Waqar Ahmed Aziz 4
Good vs Bad
Time management
Role Suggested % Rationale Role Misguided % Why This Is a Problem
Coordinates timelines, meetings,
Too low — project coordination will suffer,
Project Manager 15% communication, and keeps everything on Project Manager 5% leading to missed deadlines and chaos.
track.
Critical during the planning and design Overweight — spending too much time
UI/UX Designer 15% phases; sets the foundation for UI/UX Designer 40% polishing designs instead of progressing the
development. build.
Responsible for building the user-facing
Too little — results in rushed or incomplete
Frontend Developer 25% side of the app, a large and visible Frontend Developer 10% interfaces.
component.
Manages core logic, databases, APIs— Same issue — backend won't be robust or
Backend Developer 25% typically equal in weight to frontend.
Backend Developer 10% scalable.
Involved during and after development to Not enough time to test thoroughly, leading
QA Engineer 10% ensure everything works as intended.
QA Engineer 5% to bugs in production.
Excessive involvement can cause
Provide direction, feedback, approvals—but
Stakeholders 10% less hands-on in day-to-day execution.
Stakeholders 30% micromanagement, constant scope creep,
and decision delays.
4/25/2025 Malik Waqar Ahmed Aziz 5
SOP
Standard Operating Procedure for Projects
1. 2. 3. 4. 5. 6. 7. 8.
Project Initiation Design Process Development Testing & QA Deployment Post- Documentation Closure
Deployment
10% 15% 30% 20% 5% 10% 5% 5%
Stakeholder Wireframes approval Version control setup Unit tests coverage Pre-deployment Monitor logs for 72 Maintain living Lessons learned
identification from stakeholders (e.g., Git) minimum 80% checklist (e.g., backups, hours post-release documentation document
DB migrations) (Confluence, Notion, or
GitHub Wiki)
Requirement gathering UI/UX best practices Branching model: Automated tests for Approval from QA & Gather user feedback Update every time Final report to
checklist checklist main, dev, feature/*, critical features stakeholders before go- there’s a feature release stakeholders
hotfix/* live or critical fix
Define scope using Design-to-dev handoff Code review policy (min. Manual testing checklist Rollback plan Maintenance plan Archive all artifacts
MoSCoW protocol (Figma → Dev 1 peer review before (patch cycles, (repos, docs, user
(Must/Should/Could/W links) merging) monitoring tools) feedback)
on’t)
Risk identification & CI/CD pipeline setup Regression test
mitigation plan protocols
Local dev, staging, and Bug severity definitions
production environment & triage flow
config
4/25/2025 Malik Waqar Ahmed Aziz 6
4/25/2025 Malik Waqar Ahmed Aziz 7
Consider
Take it a step further
1. Retrospective Plan
2. Change Request Document
3. Risk Register
4. Meeting Agenda & Notes Template
5. Release Notes Template
4/25/2025 Malik Waqar Ahmed Aziz 8