Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Create a roadmap for ea using capability maturity models


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Create a roadmap for ea using capability maturity models

  1. 1. Create a Roadmap for EA Using CapabilityMaturity ModelsUniversity of Alaska - PM and EA Workshop – May 2008Leo de Sousa, Manager, Application Services and EnterpriseArchitectureBritish Columbia Institute of Technology
  2. 2. Agenda• Capability Maturity Models• Value and Benefits• Measurement• Now Build Your CMM• Future• Questions © 2007 BCIT IT Services
  3. 3. Capability Maturity Models• CMM was developed by the SEI at Carnegie Mellon University in Pittsburgh –• Five Level Model to guide and assess the maturity of a process• Now adapted as a model to describe incremental attributes of maturity for methodologies and disciplines © 2007 BCIT IT Services
  4. 4. CMM – Capability Maturity Models Level 4 + …… Level 3 + …… • Discipline is optimized for Level 2 + …… • Integrated into effectiveness broader areas Level 1 + …… and efficacy • Processes are of practice tested, tuned, • Definition of • Consistent AttributesValue and systemized • Recognized • General semantics and application of opportunities awareness of process Best Practices • Systemic to apply discipline &/or targets approach to discipline &/or methods • Operates as a discipline &/or methodology • Where you “Centre of methodology • Some early & want to be Excellence” isolated attemps Initial Process Process Process Process Descript. Awareness Defined Repeatable Managed Optimized Level # Level 1 Level 2 Level 3 Level 4 Level 5 Time © 2007 BCIT IT Services
  5. 5. Capability Maturity Model - Benefits • Level 5: Optimizing - Continuously targeting improvements required to meet business objectives • Level 4: Quantitatively Managed - Predictable results, knowledge of factors causing variance and reuse • Level 3: Defined - Meeting cost and functionality targets as well as improved quality • Level 2: Repeatable - Meeting schedule and reduced turnover resulting from less overtime • Level 1: Initial - No benefits: Inconsistency, schedule and budget overruns, and defective applications © 2007 BCIT IT Services
  6. 6. CMMs Five Maturity Levels for Software Processes1. At the initial level, processes are disorganized, even chaotic. – Success is likely to depend on individual efforts, and is not considered to be repeatable, because processes would not be sufficiently defined and documented to allow them to be replicated. © 2007 BCIT IT Services
  7. 7. CMMs Five Maturity Levels for Software Processes2. At the repeatable level, basic project management techniques are established – Successes could be repeated, because the requisite processes would have been made established, defined, and documented. © 2007 BCIT IT Services
  8. 8. CMMs Five Maturity Levels for Software Processes 3. At the defined level, an organization has developed its own standard software process through greater attention to documentation, standardization, and integration. © 2007 BCIT IT Services
  9. 9. CMMs Five Maturity Levels for Software Processes 4. At the managed level, an organization monitors and controls its own processes – through data collection and analysis. © 2007 BCIT IT Services
  10. 10. CMMs Five Maturity Levels for Software Processes 5. At the optimizing level, processes are constantly being improved – through monitoring feedback from current processes and introducing innovative processes to better serve the organizations particular needs. © 2007 BCIT IT Services
  11. 11. The Value of CMMs• You can use CMMs to: – Describe the maturity process of EA – Create a roadmap for maturing EA – Communicate with clients of EA• Use CMMs as roadmaps to maturing a methodology – “What should I do next?” – “Where should I focus next?”• Can be used as a performance development tool by managers• Useful Work Planning tool by the EA © 2007 BCIT IT Services
  12. 12. Measuring the Value – Use a CMM Roadmap• Maturing our EA Methodology – Introducing new EA practice required a plan and a roadmap – Enterprise Architect needed a way to communicate their EA’s process to stakeholders – Published the EA CMM within IT Services and to the BCIT client community• Measurement Attributes – Easy to assess if complete or not – Simple scoring system – no weighting for more complex attributes – Updated as attributes are complete – Reviewed annually to account for changes in strategy• Communication – The CMM is the roadmap – Clients (internally and externally) can see where the practice is going © 2007 BCIT IT Services
  13. 13. CMM – Enterprise Architecture Level 3 + …… Level 4 + …… • EA GP & Stds • EA integrated recognized in BCIT institutionally Level 2 + …… • EA Standards • BCIT Capital • EA Guiding & Waivers Plan adjusted Principles improve EA based on EA Published • EA metrics Level 1 + …… • Senior Mgmt • EA Roles Integ. support • Implements involved in • EA Process every decision Zachman EA review Communicate maker at BCIT • EA Guiding • Domain Arch. • EA Manages • Explicit Principles Manage docs AttributesValue • EA ad hoc Artifacts governance of • EA Roles • Explicit • EA docs & stds • Senior Mgmt IT purchases • Explicit links governance created locally support and using EA Stds to BCIT for managing • Tech Reqmts endorse EA & Waivers strategy IT purchase determine • Explicit EA • Technology • EA Artifact variances strategy governance Investments Development • All planned IT • No IT Service for BCIT IT Optimized • EA Docs purchases Culture purchases with EA Centralized governed by based on stds EA standards EA Process EA Process EA Process EA Process EA Process Descript. Informal Development Defined Managed Optimized Level # Level 1 Level 2 Level 3 Level 4 Level 5 Time © 2007 BCIT IT Services
  14. 14. EA CMM in Excel © 2007 BCIT IT Services
  15. 15. Measuring the Value – Level 1Level 1 – EA Process Informal Architecture planning/implementation doneEA ad hoc for architecture domains in silos Lack of an integrated architecture,EA documents and standards created locally standardizedTechnology requirements determine Technology decisions are based on existingimplementation strategy vendor requirementsLack of IT Service Culture Firefighting or reactive modeBusiness needs do not drive technologyadoption Minimal links to business strategy Possible Score:5 Actual Score:5 © 2007 BCIT IT Services
  16. 16. Measuring the Value – Level 2Level 2 – EA Process DevelopmentAdopt EA Framework Selected Zachman FrameworkEA Guiding Principles and Standards Create EA guiding principles for making Developed technology decisions Articulated roles in various governance groups and responsibilities forEA roles and responsibilities developed architecture changesExplicit links to BCIT Strategy IT Projects support a strategic initiative Create and publish documents and standardsEA Artifact Development based on guiding principles Created a web place with doc repository andEA documents centralized blog Possible Score: 6 Actual Score: 6 © 2007 BCIT IT Services
  17. 17. Measuring the Value – Level 3 Level 3 – EA Process Defined Publish EA guiding principles for making technologyEA Guiding Principles and Standards Published decisionsEA roles integrated into IT Services processes EA Approval in PM and ChgMEA Process Communicated Make EA presentations internally and externally Enterprise Architect responsible for evolvingEnterprise Architect Manages Documents documentsSenior Mgmt support and endorse EA Senior Mgmt make decisions using EA principlesExplicit EA governance for IT Services technology IT Services will ensure technology purchases frompurchases based on standards their budget meet EA standardsDefine and Capture EA Metrics Publish current EA metrics and identify target metricsBuild EA Documents Domain Architects develop current state documents Possible Score: 8 Actual Score: 5.5 © 2007 BCIT IT Services
  18. 18. Measuring the Value – Level 4 Level 4 – EA Process ManagedEA Guiding Principles and Standards Embedded into Clients leverage EA documents to plan and implementInstitutional Culture technologyBCIT Capital Plan adjusted based on EA principles Operational Planning and Budget Requests rely on EA Senior Mgmt present institutional strategy (internal &Senior Mgmt understand and use EA external) using EADomain Architects Manage Documents Domain Architects responsible for currency of documents IT Services Mgmt must approve a deviation from EADeviations from EA Standards require an Approved Waiver standardsExplicit EA governance for all BCIT technology purchases IT Services will ensure BCIT technology purchases meet EAbased on standards standardsConduct EA Metric Gap Analysis Generate projects that move EA to target metric Possible Score: 7 Actual Score: 1.5 © 2007 BCIT IT Services
  19. 19. Measuring the Value – Level 5Level 5 – EA Process OptimizedEA integrated into the education, research andbusiness of BCIT EA Documents used by every decision makerExplicit governance of technology purchases Senior Mgmt must approve a deviation from EAusing EA standards & waivers standardsEA metrics are the authoritative source to Senior Mgmt use EA dashboard to understandimprove BCIT using technology current and projected technology needsEA drives Strategic and Operational Budget Budgets are approved based on EA identifiedPlanning needs instead of a bidding processTechnology investments optimized by adhering No unplanned technology investments made atto Institutional EA process BCIT Possible Score: 5 Actual Score: 0.5 © 2007 BCIT IT Services
  20. 20. Measuring the Value – Where are we?Enterprise Total TotalArchitectureCMM Summary 1 2 3 4 5 Actual Actual Actual Actual Actual Actual Plan Plan Plan Plan Plan Planas of March 2008EnterpriseArchitecture 5 5 6 6 8 5.5 7 1.5 5 0.5 31 18.5 © 2007 BCIT IT Services
  21. 21. Time to Build Your CMM Building Your EA CMM Add activities Score your Identify 5 and completion levels of EA processes of each Maturity for each activity level © 2007 BCIT IT Services
  22. 22. Questions © 2007 BCIT IT Services