1 / 26

Applying Portfolio Management Principles to Information Technology Projects

Applying Portfolio Management Principles to Information Technology Projects. Portfolio Management. Multiple Projects and / or Programs aligned to meet the strategic objectives of the organization. Information Management and Information Technology (IM-IT). No More IM-IT Projects!.

tovi
Télécharger la présentation

Applying Portfolio Management Principles to Information Technology Projects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Applying Portfolio Management Principles to Information Technology Projects

  2. Portfolio Management Multiple Projects and / or Programs aligned to meet the strategic objectives of the organization

  3. Information Management and Information Technology (IM-IT) No More IM-IT Projects! Just Business Projects with IM-IT components

  4. No IM-IT Projects!! • IM-IT should be an enabler to the business • No direct line-of-sight between the IM-IT project and the business objectives • IM-IT takes on a “mind of its own” • Placing the IM-IT as a component to a business project increases the likelihood that the business objectives remain paramount to the project success

  5. Large Application Development Projects • 9 per cent on time and on budget • 73 per cent never finish • 94 Restarts for every 100 starts • Major cost and time overruns • Lots of conflict Standish Group

  6. Dramatic Differences by Size

  7. Projects without Portfolio Management Strategic Objectives

  8. With Centralized Control Mandate

  9. With Portfolio Management Vision

  10. There is a difference! Portfolio of Projects A Large IT Project Hierarchical based Prescriptive approach Centralized command and Control “How” each sub-project is managed is controlled Feels onerous • Vision based • Alignment via strategic objectives • Project teams know where the alignment is • “Common services” provided by the Portfolio Office • Feels like a small project

  11. Enterprise Application Architecture?? • Sounds scary, usually is • Small Projects are completed on time, large projects are not (91% of the time) • Client Manager already knows what he/she wants • Don’t add centralized complexity to my project and cause it to fail South Saskatchewan Chapter

  12. The Portfolio = The Enterprise “Agile methodology and Enterprise Application Architecture Collide” Crystal Bydell

  13. Optimal Levels of Control Amount of Centralized Control Time to achieve objectives

  14. New Building Construction • Someone has to figure out how your house exists in relationship to your subdivision • Municipal developments are more mature than IT, so you would know that you need connections for: • Water • Sewer • Natural gas • Electricity • Road • IT has to figure out what those connections… Standardized Connections

  15. Three Enterprise Functions • A common Customer Management Application • Any Entity / Stakeholder with a set of Name, Address, and Demographic • A common Company-id and Individual-id • A common method of handling all types of Transactions • Audit Trail • Financial Integrity • A common method of identifying all of the Products and Services within the Enterprise South Saskatchewan Chapter

  16. One Application at a Time Application Application Application Application Application Application Product Definition Product Definition Product Definition Product Definition Business Trans Business Trans Business Trans Business Trans Customer Mgmt Customer Mgmt Customer Mgmt Customer Mgmt Business Trans Business Trans Product Definition Product Definition Customer Mgmt Customer Mgmt Integration Middleware Integration Middleware Integration Middleware Integration Middleware Integration Middleware Integration Middleware

  17. Enterprise Complexity Application Application Application Application Application Application Business Trans Product Definition Customer Mgmt Business Trans Product Definition Business Trans Product Definition Product Definition Business Trans Product Definition Business Trans Product Definition Business Trans Customer Mgmt Customer Mgmt Customer Mgmt Customer Mgmt Customer Mgmt Integration Middleware Integration Middleware Integration Middleware Integration Middleware Integration Middleware Integration Middleware

  18. Enterprise Chaos “70% of all code written today consists of interfaces, protocols and other procedures to establish linkages among various systems” - IBM

  19. Enterprise Application Architecture Business Application Business Application Business Application Business Application Business Application Business Application Customer Mgmt Application Business Transaction Product Definitions Corporate Data Model 1 1 1 Infrastructure, Network, Corporate Security, Imaging Systems, etc Start the enterprise migration towards simplicity

  20. Three Enterprise Functions • Exponentially less complex interfaces • Inherently higher quality data • Automation in support of the business reality • There really is only one: • Customer • One set of Buyers and Suppliers • One set of Facilities • One way to track who did what where and when • One set of product lines, products, and components

  21. Business Successes • Driver Programs at SGI • Common “Product Lines” only visible at the Enterprise (Portfolio) level • “Permits” system at the Ministry of Environment • Designed and developed once applied to enable the business many times over South Saskatchewan Chapter

  22. SGI Example • Independent Business programs • Multiple legacy systems in support of each program • Each Legacy system with its’ own Customer File, set of Products, and style for handling transaction (and Financials) • No apparent commonality of business function • No collaboration across business units Traffic Safety Workshops Graduated Driver Licence Driver Improvement Program Medical Programs

  23. Generic Driver Life Cycle New Driver <= 16? Provide Identification Yes No Perform IRE Check Drive, Live, in SasK Issue Licence No Course/Training Suspended? Action Req’d? Action Yes Monitor Driver Performance Determine Action No No Completion? Perform Close-out Set up Course Yes Suspension Transaction History Monitor for Completion Enroll Customer Issue SK Licence

  24. Departmental Focus Remains Traffic Safety Workshops Graduated Driver Licence Driver Improvement Program Medical Programs Custom Requirements Custom Requirements Custom Requirements Custom Requirements Common Application Design User interface Product Line Products Table Values User interface Product Line Products User interface Product Line Products Table Values Products Product Line User interface Table Values Table Values

  25. Enterprise Myths • You have to have all the vested parties in the same room at the same time (Joint Venture) • You need exponentially more communications when you have enterprise functions • IM-IT projects will solve business problems (“Systems” solve business problems. Systems are made up of Inputs, Processes and Outputs) • Buying it will reduce risk and increase chances of success

  26. Enterprise Application Architecture 27 Justice Applications 4 CJIMS Applications 100 + Applications Social Services 1000 + Applications Education Customer Mgmt Application Business Transaction Product Definitions Corporate Data Model 1 1 1 Infrastructure, Network, Corporate Security, Imaging Systems, etc Start the enterprise migration towards simplicity

More Related