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.
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.
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.
9.
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
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.
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
Glossary Of TermsPV = Planned ValueEV = Earned ValueAC = Actual CostEVA = Earned Value AnalysisEVM = Earned Value ManagementEVT = Earned Value Technique
SME = Subject Matter ExpertMPP = Microsoft Project 2003/2007WIP = Work In ProgressMSP = Microsoft Sharepoint ServicesWBS = Work Breakdown Structure - The WBS is aconsolidated group of chronological deliverables that will be used to understand the fundamental requirements tobuild the tasks within the MPP plan. The best way to produce a WBS is using a grouped consensus of SME’s whounderstand the final product and what it takes to produce it.
Glossary Of TermsMPP = Microsoft Project PlanMSP = Microsoft SharepointT24 = Temenos 24
For each component listed above there is a separate work stream and this is broken down into further products to produce actual deliverables.
Double Click To OpenMSP = Microsoft Sharepoint ServicesThis slide shows you how the lower level deliverables that are depicted and maintained in MSP You can clearly see here the DSF/DST’s and the quality reviews for each of the product deliverables that were assigned to resources who provided updates and progressive comments to each of the lower level deliverables as and when they are actively in progress, completed or just as an update. The owners also have the ability to setup alerts so that this makes it easier for them to track the tasks in project. Coupled with this it is also possible to build Gantt charts in Sharepoint so you can clearly see progress the next slide shows the a real definitive amount of detail to a particular area of the T24 project.
Double click to review in full screen.High level overview showing how a Temonos T24 project effectively making use of the functionality within Microsoft SharePoint to manage the lower level deliverables. This allows for clear visibility to the project and allows work stream leads/owners to take manage their phase of the project at a definitive level. This helps to maintain efficiency and productivity of all deliverables that have been specified.
High Level overview of the Microsoft plan showing Earned Value. The two values below are the main factors that contribute to schedule and cost performance and these are the values that are constantly measured against the tolerance margins and these are the measurements that are used to monitor cost and schedule overrunSPI = Schedule Performance Index CPI = Cost Performance Index
Double Click To OpenExample EV Showing AC =Actual CostEV =Earned ValuePV =Planned ValueThis graph shows that actual cost is over what has been planned and the Earned Value and Planned Value are at equal status.
Glossary Of TermsT24 = Name of the Temenos Product that is being implementedDouble click the slide because its an embedded document for a better view.This is a full analytical overview of Earned Value for the T24 project showing trend analysis over the course of the project.
Glossary Of TermsCPI = Cost Performance IndexSPI = Schedule Performance IndexT24 = Name of the Temenos Product that is being implemented
This is a high level overview defining the preferred solutions used to implement a Temenos T24 project for an example project for KBL bank for a £17.5m projectThis shows how four software solutions where used to successfully integrate Temenos T24 into the business. The following is a small breakdown of the above process:WBS structure segregated into phases and a financial budget proposed to each phase of the project providing distinction to where the budget is being spent When the financials are broken down the tasks can be estimated, planned and forecasted within the WBS of the project. There is a clear interaction and relationship of collaborating financials with Microsoft Project plans, which have an output of Earned Value that is fed into Microsoft Sharepoint for visualisation and project governance, control and reporting.Microsoft Access works interactively with Microsoft Sharepoint Reporting Services to provide clear and concise reporting for senior management.
Glossary Of TermsT24 = Name of the Temenos Product that is being implementedDouble Click To Open: Embedded Document
Glossary Of TermsMSP = Microsoft Sharepoint T24 = Name of the Temenos Product that is being implementedDouble Click To Open: Embedded DocumentProject DashboardThis dashboard has been designed and implemented and shows the following: Links to all Microsoft project plansLinks to all EV trend graphs for each phaseLinks to the lower level deliverables for each phaseOwners to each phaseWBS showed and maintainedPDF documents showing cost analysis to each plan and phase of the project.% complete