WEEKLY STATUS REPORT - PROVISIONI

Checklist V1.0

Project Name
Project Description
Project Planned Start Date
Client Name
Client Contact
Project ID
Offshore Project Manager

Project lead
Phase of the project
Overall Status* AM
Previous week's status

Delivery Director
Onsite Project Manager
PMO Contact

Executive Summary

Management Escalations

Issue/Risk Impact

Programme Governance Management Office (PMO)

Last Gate reviewed Gate status

Weekly Project Dash Board
Project
<Project Na
Previous Week

Scope
Schedule (from Metrics sheet)
Effort (from metrics sheet)
Quality (details in metrics sheet)

Resources
Risk Trend (from risk tracker sheet)
Budget (from cost in metrics sheet)
Invoice

Overall Project

In Good Shape. No Major Issues

Significant Issues or Risks
Major Issues/Risks require immediate action/decis

Indicative Trends towards next week's status

6. Customer Feedback
Feedback Who gave the feedback
ORT - PROVISIONING OF VDPS
st V1.0

Reporting period
Prepared by
Date

AMBER (from row 50 below)

GREEN

Phone
Phone
Phone

Impact Action Plan

t Office (PMO)

Pending action items

 <Project Name>
Current Week Trend

pe. No Major Issues

sues or Risks
Risks require immediate action/decision

ends towards next week's status

Who gave the feedback How did we respond?

<Enter Date>

dd-mm-yyyy to dd-mm-yyyy

dd/mm/yyyy

Status<New/Action
Date Reported
Defined/Completed>

Next gate review date

 Weekly progress and next week's plan (Sa
Key Project Milestones / Checkpoint

Achieved last week

BRD and SRD Sign-off
System Test strategy document
Draft SAD
Draft ISD
Walkthrough of FSD to Bank
Base Build for Testing Team
Test Scenarios preparation for two bundles

Not achieved so far

FSD Sign off
ISD Finalisation
Draft TSD
Draft Datamodel

Plan for next week

Finalising Test Strategy Document
Resolve the issues around iteratable
configuration and release a build to testing team

Install a release in tester machine and initiate

testing
Build and unit test a webservice
Test cases preparation for the remaing bundle

did we respond? Contact Point

 Version : 1.0
SCR NO:
Developed by:
Verified by:
Verified date:

Owner Remarks

Previous gate criterion met?

xt week's plan (Sample Datas)
Projected date of completion- Status # of Days Owner
discuss Delayed

Additional Comments
Remarks
`
WBS # GATE

2 GATE 0
3
3.1
3.2
3.3
3.4
3.5
4 GATE 1
5
5.1
5.2
5.2.1
5.2.2
5.2.3
6 GATE 2
7
7.1
7.1.1

7.1.2
7.1.3
7.2
8 GATE 3
9
9.1
9.2
9.3
9.4
10 GATE 4
11
11.1

11.1.1
11.1.2
11.1.3
11.2
11.2.1
11.2.2
11.3
11.4
11.4.1
11.4.2
12 GATE 5
13
13.1
13.2
13.3
13.4
13.5
13.5.1
13.5.2
13.6
13.6.1
13.6.2
13.7
13.7.1
13.7.2
13.8
13.9
13.10
14 GATE 6
15
15.1
15.1.1
15.1.2
15.1.3
15.1.4
15.1.5
15.1.6
15.1.7
15.1.8
15.1.9
15.1.10
15.2
15.2.1
15.2.2
15.2.3
15.3
15.3.1
15.3.2
15.4
16 GATE 7
17
17.1
17.2
17.3
17.4
17.5
17.6
17.7

18 GATE 8
19
19.1
19.1.1
19.1.2
19.1.3
19.2
19.2.1
19.2.2

20 GATE 9
21
21.1
21.2

21.3
21.4

GATE 10
22
23
23.1
23.2
23.3
23.4
23.5
23.6
24
24.1
24.2
24.3
24.4
24.5
24.6
2. Milestone summary

Milestones

Project Initiation
SOW - internal review and sign-off
Project Resource Model
Initial Risk Documentation Preparation
Project Estimation Preparation
Project Plan Template - AtTask

Requirements
Initial Requirement Discussion
BRD(Business Requirement Document)
BRD - Preparation
BRD - Internal review and Sign Off
BRD - Client review and Sign Off

Solution Design
FSD ( Functional Specification Document)
FSD - Preparation
FSD - Internal review & sign-off
FSD - Client review & sign-off
Walkthrough of the solution to CE/CMG

Planning
Baseline Project Plan
Baseline estimations
Prepare Test Strategy Plan
Traceability Matrix

Software Analysis and Design

ISD ( Interface Specification Document)

Softwares - Preparation ( Purchase / Existing Licenses Review / . )

Internal review and Sign off
Client review and Sign-off
SAD ( System Architecture Document)
SAD Preparation
SAD - Internal review & sign-off
Performance Test Strategy
TSD ( Technical Specification Document)
TSD - Preparation
TSD - Internal Review & Sign Off

Interface and Custom Development

Base Build for Configuration
Basic Metadata Creation
Rule Authoring
Batch Processing
UI Screens
UI Screens Development
Code review
Reports
Reports Development
Code review
Custom development
Custom development
Code review
Product designing & unit testing
Regression Test Suite Prep
Walkthrough of the solution to CE/CMG

Testing
Component Integration Testing (CIT)
Test Case Scenario Creation
Test Data Creation
Test Strategy - Review and Update
CIT - Test Case Execution ( Products and Policies)
CIT - Test Case Execution ( for Segmentation and PFA)
CIT - Test Case Execution ( Reports)
CIT - Test Case Execution (UI Screens)
Prepare Excel configuration files for user roles
Complete the configuration files for user roles
Defects
Regression Testing
Test case execution
Regression Testing sign-off
Defects
System Integration Testing (SIT)
SIT - Test environment set-up
SIT - Review & sign-off
Performance readiness report

Release
Regression test
Code review
Release Notes
Installation guide
Operational Manual
Product Manual
Training
SIT
SIT

UAT and PT
User Acceptance Testing (UAT)
UAT - Environment Setup - Support by Zafin
UAT Support
UAT Review and Sign-off
Performance testing
Performance testing execution
PT review and sign off
Data Migration/Conversion

Deployment
Operation Readiness
Deployment completion - sign-off
Parallel-Run(Pilot)
Support handover
Go-Live

Project Closure and Health Check

Performance Analysis
Skill Matrix updates
Lessons Learnt documentation
Closure Report Preparation
Conduct Closure Meeting
Closure sign off
Project Management
Project Tracking/Reporting/Review meetings (Internal)
Project Tracking/Reporting/Review meetings (External)
Scheduled project team meetings
Conflict resolution
Project issue resolution
General OH/Admin (anything but the above)
 Weekly Status Update

Planned Start Date Actual Start Date

view / . )
Status Update <Enter Date>

Planned End Date Actual End Date Milestone Owner

Status<New, In Planned Actual
Progress, Completed) & Hours(person Hours(person
RAG hours) hours)
 Reason for Slippage
Effort to Completion(estimate
( Variation Between Effort
by PM in person hours)
& Actuals )
Actions, Resolutions and Remarks
 CHANGE REQUEST TRACKER

Date of
CR # Requested by Request Description

UP Template Version: 11/30/06 Page 41 of 58

Estimated Cost Impact Summary Billable/Non-Billable

UP Template Version: 11/30/06 Page 42 of 58

Status Piority Planned delivery date

UP Template Version: 11/30/06 Page 43 of 58

Actual delivery date Comments

UP Template Version: 11/30/06 Page 44 of 58

RISK MANAGEMENT LOG

Risk
Current Corresponding Risk Probability of Map
ID Date identified
Status Issue ID Impact Occurrence <TBD : weighted impact of
the 3 preceeding factors>

Open High Low Yellow

Closed Medium Medium Closed

Low Low Green

UP Template Version: 11/30/06 Page 45 of 58

UP Template Version: 11/30/06 Page 46 of 58
 Description of project Risk
Risk
Risk Area Impact Response
Description
Strategy

EXAMPLE: Current project skill set may not be adequate to Design EXAMPLE: If required skills are not identified or obtained, project Mitigation
complete all project work. The current development team has schedule may slip and possibly restrict the accomplishment of
been working in a Windows 2k environment, and the current project goals.
requirements are for a LINUX environment. The project schedule
would require 1500 development hours of a skilled LINUX
operator, and approximately 1900 to 2200 if we retrain our
current resources.

UP Template Version: 11/30/06 Page 47 of 58

UP Template Version: 11/30/06 Page 48 of 58
Owner Mitigation Plan Planned due date/target closure date

EXAMPLE: Find internal resource that meets required skill

set or train existing resources on LINUX.

UP Template Version: 11/30/06 Page 49 of 58

UP Template Version: 11/30/06 Page 50 of 58
Planned Effort(in person hours) Actual Close date Actual Effort(in person hours)

UP Template Version: 11/30/06 Page 51 of 58

UP Template Version: 11/30/06 Page 52 of 58
Contingency Plan

EXAMPLE: Find resource that meets required skill set

through external hiring sources.

UP Template Version: 11/30/06 Page 53 of 58

UP Template Version: 11/30/06 Page 54 of 58
ISSUE TRACKING LOG

Issue type<Client
Current Issue Issue
ID Date identified identified/
Status Impact Description
internal>

28/02/2014 Closed EXAMPLE: NFR sign off delayed

High

Medium
Low

UP Template Version: 11/30/06 Page 55 of 58

Project
Impact Issue Area Owner
-Cost/Quality/Schedule

EXAMPLE: NFR is not yet signed off. It could impact the Schedule
technical design. Schedule impacted

Azeef

UP Template Version: 11/30/06 Page 56 of 58

Action Plan Planned due date Planned Effort(in person hours)

EXAMPLE: NFR has to be agreed with the bank

immediately as changes to the requirements could impact
the schedule. Especially, the section related to processing
100 million records in 3 hours has to be agreed

UP Template Version: 11/30/06 Page 57 of 58

Actual Close date Actual Effort(in person hours)

UP Template Version: 11/30/06 Page 58 of 58