fpt software internal use 1 project name post-mortem meeting date: 10-03-2014 author:

FPT Software

Internal use 1

Project NamePOST-MORTEM MEETING

Date: 10-03-2014Author:

Post mortem agenda

2

Project Overview1

Metric result vs. plan2

Causal Analysis3

Risk/Issue4

Lessons & Practices5

1. Project Overview

• Project scope & objectives SRS;Design;Coding;Unit Test;

Maintain Voice tools: VStarlite, VCM, ClipLibraryTool, Voice Monitor, Voice Health.

• Project Duration & Effort

# Items Actual Planned

1 Start Date 05-Aug-13 05-Aug-13

2 End Date 31-Dec-13

3 Duration 148 217

4 Effort 494 540.6

1. Project Overview

• Project organization

FSOFT

1. Project overview

• Deliverables & Milestones

• Schedule Achievement

No.

DeliverableCommitted

delivery dateActual

delivery dateDeviatio

n    

1. Project Overview

• Achievements

2. Metric result vs. plan

# Metrics Unit Actual Project Target

Formula

QUALITY (Q)

1 Customer Satisfaction

Point 100 93 = Total point of customer survey pointNote: Max is 100, Min = 0

2 Leakage Wdef/MM 0 0.2 = No of Wdef Defects detected after delivery for acceptance test of a product/Product size

3 Process compliance rate

% 92 95 = SUMPRODUCT(checked items,assessment results)/SUM(checked items). Note: only include checked items with assessment results = 0, 50, 100.

COST (C)

4 Effort Efficiency % 98.04 95 = (Billable effort/Calendar effort)*100%

5 Correction Cost % 7 4 = (Effort Usage on Technical Rework/Total Effort Usage)*100%where- Effort Usage on Technical rework is effort spent on "Engineering processes" with Type = Correct- Engineering processes are: Requirement, Design, Coding, Deployment, Customer Support, Testing

DELIVERY (D)

6 Timeliness % 100 100 = (No of deliverable delivered on time/ Total # of deliverables delivered)*100%

Note: Just count for the formal deliverables which are committed in Delivery Schedule in WO

3. Causal Analysis

4. Risk/Issue

9

No Description Mitigation Action Contingency Action

1

2

No Description Category Solution

• Risk

• Issue

5. Lessons & Practices

<Discuss/brainstorm to identify what has been learned about project approach, structure, communication, technical and other aspects of the project by answering the following questions for each aspect:

+ What went right (practices)

+ What went wrong (lessons), and How it could be made better the next time

+ Identify areas for improving project performance, customer satisfaction, and quality.>

• Lessons• Practices

THANK YOU

Question and Answer

12