PERT & CPM · My Provision Store

PERT & CPM Analysis

Program Evaluation Review Technique · Critical Path Method for My Provision Store

Critical Path: 28.7 Days

PERT Estimation (Days)

Task	Optimistic	Most Likely	Pessimistic	Expected
A · Requirements	2	3	5	3.1
B · UI/UX Design	5	7	10	7.1
C · Frontend Development	8	10	15	10.5 ⚠️
D · Backend (DB)	7	8	12	8.5
E · Testing & QA	4	6	8	6.0 ⚠️
F · Deployment	1	2	3	2.0 ⚠️

Expected = (Optimistic + 4×Most Likely + Pessimistic) / 6

Critical Path Method

Path 1 (Critical): A → B → C → E → F

A → B → C → E → F 28.7 Days

Path 2 (Non-Critical): A → B → D → E → F (Float: 2 days)

Total Project Duration: 28.7 Days

Critical tasks are marked in yellow

PERT Timeline · Task Duration

A · Req.

3.1d

B · Design

7.1d

C · Frontend

10.5d ⚠️

D · Backend

8.5d

E · Testing

6.0d ⚠️

F · Deploy

2.0d ⚠️

Non-Critical Critical Path

Resource Allocation

Frontend Dev: 100%

Backend Dev: 100%

Tester: 50%

Server: 24/7

Project Manager: 100%

UI/UX Designer: 70%

Leveling: Shift UI/UX to Week 1 → reduce peak load on Frontend

Project Crashing

Scenario: Deadline moved up by 5 days. Options to reduce duration:

Option A: Add 1 more developer to Frontend
+₹10,000 · Saves 4 days

Option B (Recommended): Outsource Admin Panel
+₹8,000 · Saves 5 days

New Duration after Crashing: 23.7 Days

PERT Network Diagram

                A (3.1)
                
                B (7.1)
                
                C (10.5)
                
                E (6.0)
                
                F (2.0)
            
                ■ Critical Path  |  
                ■ Non-Critical
            
                 Total Expected Duration: 28.7 Days