7.1 Current Status Report

This topic gives an overview on Current Status Report.

Current Status Report should be sent to the Head of Implementation every fortnight from the day you begin the project.

It should give the following information:

• Work completed during the fortnight
• Work scheduled for the next fortnight
• Problems encountered during the fortnight
• Billing details

Current Status Report Sample

The People:

Customer

• Ms. Annabel Smith (IT Head)
• Mr. Jim Hacker (Systems Manager)

Oracle Financial Services

• Sylvia John
• Ramkrishnan S

Reporting Period: 15/03/98 to 31/03/98

The Schedule:

Table 7-1 The Schedule

Activity	Planned Start and End Date	Actual Start and End Date	Responsibility	Remarks
S/W Installation	15/03 19/03	17/03 20/03	FCIS	Given below
User Training	22/03 25/04	23/03 In progress	FCIS	Given below
Database Set up	24/03 30/04	24/03 In progress	FCIS	Given below

Remarks: Software installation was delayed because hardware was not available. User training was delayed because a few key users were on leave. Database set-up has begun.

Action Items:

Table 7-2 Action Items

Activity	Planned Start and End Date	Actual Start and End Date	Responsibility	Remarks
Code Structures	08/04	NA	FCB	NA
General Ledger	08/04	NA	FCB	NA
List of Customers	08/04	NA	FCB	NA

Achievements during the period:

Software installation completed.

User training for Data Entry module completed.

Outstanding Issues: None

Plan for the Next Fortnight: User training for Foreign Exchange and Money Markets. Database set-up for Branch Parameters, Customers, General Ledger.

Billing details:

Professional working days: 10 working days + 1 Saturday

Milestone achieved for billing: S/W installation

Expenses to be billed to client: Airfare and incidental expenses to Melbourne.