The document provides an overview of project planning and earned value management for a T24 project. It discusses defining deliverables, creating a work breakdown structure and project plan in Microsoft Project, tracking progress to calculate earned value, and using earned value trends and reports for project control. Graphics from Microsoft SharePoint and Project are shown as examples of how lower deliverables, the project schedule, and earned value metrics were managed for the T24 project.

1. Project Planning and Earned Value Management

2. Contents Objective Fact about Earned Value Management Earned Value definitions & descriptions How to Produce Earned Value Introduction to the “Project Planning Approach” utilizing the top level down & bottom level up mechanism for planning a T24 project. - Two screenshots showing how the lower deliverables can be managed more effectively in Microsoft Sharepoint - Microsoft Project and how Earned Value is derived. - Weekly Earned Value analytical graph. - Earned Value trend analysis across the T24 project. Introduction to the planning process and how it was integrated into the T24 project. - Example of a High Level Work Breakdown Structure For a T24 Methodology - The planning process - The control process Overview of Microsoft Sharepoint T24 Project Dashboard

3. Objective The objective of this slideshow is to provide the audience with the following: A high level overview of Earned Value Analysis and the benefits of using this analytical method to measure a projects progress. How Earned Value Management enhances project performance by allowing the project audience to exhume levels of detail from any project and retrieve statistics that can be measured against the baseline under project control. A detailed overview of one specific phase from the project which will define how to approach project planning for this type of project, using combined solutions of both Microsoft Sharepoint Services and Microsoft Project 2007. Define and show how the iterative project planning process works within the Hub T24 project and how the best practice of maintaining and enforcing this process within a project of this magnitude. Review of the project dashboard – Implemented a one stop solution for visual knowledge about the project for senior management.

4. Facts About Earned Value Organisations often want to know some of the following questions when Considering using the Earned Value Technique What is EVM? It’s a metric devised to achieve meaningful comparisons between planned and completed work. Earned Value allows projects to show early indications of cost and schedule overruns within a project by using controlled mechanisms that are enforced before the baseline of the project. The three basic main elements of EVT are PV, EV, and AC. These are the core analytical acronyms that are used to produce the statistics for EVA. Why should we adopt the EVT within our organisation and what are the benefits to using EVA within a project? The EVM technique integrates the triple constraints of scope, time and cost and is becoming a wide spread form of tracking mechanism for projects. It evaluates progress analytically and this been known for its proven and established efficiencies it brings to any project. EVT allows you to have more control and management of the project. Coupled with good planning and effective use of EVM will reduce the impact to a significant number of project issues which are due to schedule and cost overrun. EVM also aids in negotiations with the end customers about scope increase, because cost and schedule increases nearly always occur due to scope creep and this will be quite evident to stakeholders. EVM also provides statistics to stakeholders when reporting on project performance because EVM can show past, current and predicted forecast performance and this shows a greater level of detail.

5. EV Definitions & Descriptions

7. The dependencies are built upon the independency relationships that is scaled out from the WBS and these are done in either the project plan itself or in a integrated solution that has been designed within MSP.

8. You also need a list of assumed or available resources including their costs and the designated tasks they have been delegated to own.

10. Project Planning Approach A combination of a top level down and a bottom level up approach was used to track and measure the deliverables of the project. This provides senior management with the ability to view the project from a high level financially and at the lower level products. Products like MPP and MSP where used to store, maintain and effectively manage the project and to provide advanced dynamic reporting to the stakeholders. The following slides are document outputs from MSP and MPP showing the planning solutions that were used for the T24 project at KBL bank, which includes an example of a T24 WBS methodology.

11. High Level WBS For A T24 Project Including the Methodology START Gap Analysis Functional Design DST based Development System Testing Functional Catalogue Local Code Conversion Migration Testing Migration Design Technical Design Non Functional Testing Architecture Unit Testing Build Team UAT Testing Business Process Testing Dress Rehearsal Implementation Migration Cutover Training END BPT & UAT Testing Team Implementation Team

12. MSP Lower Level Deliverables

13. MSP With Gantt Chart

14. Microsoft Project With Earned Value The below example is a screen shot showing the high level deliverables of the securities areasituated within the design & analysis phase of the project. This report allows seniormanagement to view the project at phase level. The below screenshot shows how we retrievethe Earned Value statistics.

15. Analytical Earned Value Graph

16. Overall T24 Project EV Report

18. The Control ProcessThe Planning Processis a high level overview that provides a detailed analysis and breakdown of each work stream in the T24 program. The goal of the planning phase is to have clear timeframes driven by concrete milestones, by which the project can be measured against. The Control Process is where you should monitor the progress and constantly review the SPI and CPI for the project, so that the tolerance thresholds are controlled. If you exceed a project tolerance then actions are invoked to allow senior management to review the relevant work stream and implement corrective action to reduce or eradicate the issue at an early stage. The breakdown of the high level solutions for the planning and control processes can be seen in the next slides.

19. Plan Tasks Resources Re-Forecast Budget T24 High Level Planning Process High Level Planning Process Solution Earned Value Reporting WBS By Phase Access Reports Financial Reporting

20. T24 Control Process

21. T24 MSP Project Dashboard

22. The End