Enterprise Spice Kickoff Overview

570 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
570
On SlideShare
0
From Embeds
0
Number of Embeds
27
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Enterprise Spice Kickoff Overview

  1. 1. Enterprise SPICE Overview Linda Ibrahim Enterprise SPICE Kick-off October 2007
  2. 2. Topics <ul><li>Enterprise SPICE Introduction </li></ul><ul><ul><li>Need, Background, Objectives </li></ul></ul><ul><li>Benefits to Stakeholders </li></ul><ul><li>Approach </li></ul><ul><li>Governance Structure, Roles, Responsibilities </li></ul>Enterprise SPICE Kick-off October 2007
  3. 3. Introduction <ul><li>Need: The process community has recognized the need for an integrated standards-based enterprise model and has requested an international activity to develop such an assessment model. </li></ul><ul><li>Background: The SPICE User Group has endorsed the initiative to establish an Enterprise Integrated Standards-Based model (Enterprise SPICE) for use with international standard ISO/IEC 15504 (SPICE). Enterprise SPICE was formally launched at the SPICE2007 conference in Seoul, Korea </li></ul><ul><li>Objectives: Enterprise SPICE will integrate and harmonize existing standards as determined by the project stakeholders to provide a single process reference model and process assessment model that addresses broad enterprise processes. Enterprise SPICE will provide an efficient and effective mechanism for assessing and improving processes deployed across an enterprise. </li></ul>Enterprise SPICE Kick-off October 2007
  4. 4. Benefits to Stakeholders <ul><li>Single Unified Model: the model integrates practices from the widely recognized standards and sources of best practice; no need to use many separate standards and models concurrently - they are consolidated into a single unified model </li></ul><ul><li>Pick and Choose: select from the model those areas relevant to your business needs </li></ul><ul><li>Authoritative: provides best guidance available drawn from widely recognized standards and sources, with detailed mapping tables tracing each practice to sources if further information desired/required </li></ul><ul><li>Comprehensive: addresses a broad, and expanding, range of disciplines </li></ul><ul><li>Synergized: sources integrated, harmonized, and synergized; each source contributes important perspectives </li></ul>Enterprise SPICE Kick-off October 2007
  5. 5. Benefits to Stakeholders (continued) <ul><li>Reduced Costs: </li></ul><ul><li>• Training on one model, not several </li></ul><ul><li>• Improvement using one model, not several, leading to simultaneous improvement vs. all sources; compliant processes address best practice from multiple standards </li></ul><ul><li>• Avoids duplication of effort </li></ul><ul><li>• Appraisals vs. one model, not several, leading to simultaneous multiple ratings/ certification if desired/required </li></ul><ul><li>Enhanced Effectiveness via Integrated Guidance: • For all levels from enterprise to team processes • For large or small business units • Across disciplines for multidisciplinary teams • Aligns business and technical processes • Across all product and service life cycle phases/activities • Improvement initiatives can be aligned across the enterprise </li></ul><ul><li>Certification: certification services from (accredited) bodies </li></ul>Enterprise SPICE Kick-off October 2007
  6. 6. Approach <ul><li>General approach to realizing Enterprise SPICE entails: </li></ul><ul><li>the foundation of a Governance and Oversight structure </li></ul><ul><li>formulation of the project team and plan </li></ul><ul><li>developing and deploying the work products </li></ul><ul><li>Baseline: Enterprise SPICE will have as major input the Federal Aviation Administration's (FAA) integrated Capability Maturity Model (iCMM) plus extensions, and will consider/analyze related standards integration efforts to establish an initial baseline model. </li></ul><ul><li>Evolution of Enterprise SPICE will be under the sponsorship, guidance, and oversight of collaborators and contributing partners. </li></ul>Enterprise SPICE Kick-off October 2007
  7. 7. Approach (continued) <ul><li>Website </li></ul><ul><li>The official web site is administered by the SPICE User Group. </li></ul><ul><li>An intranet and collaboration infrastructure will be established for project communications and work product repository. A small fee will be charged (to non governmental organizations) for the project collaboration facilities. </li></ul><ul><li>Trademark and Copyright </li></ul><ul><li>All contributors will recognize trademarks and copyright through the SPICE User Group. </li></ul>Enterprise SPICE Kick-off October 2007
  8. 8. Discussion <ul><li>What objectives are you hoping to achieve from Enterprise SPICE? </li></ul><ul><li>What are your general expectations regarding this project? </li></ul>Enterprise SPICE Kick-off October 2007
  9. 9. Governance, Oversight, and Responsibilities <ul><li>The SPICE User Group is an Executive Sponsor of the initiative. </li></ul><ul><ul><li>Alec Dorling is the SPICE User Group Sponsor </li></ul></ul><ul><li>The Federal Aviation Administration (FAA) is the coordinator of the international activity. </li></ul><ul><ul><li>Linda Ibrahim is the International Coordinator. </li></ul></ul><ul><li>Proposed structure, roles and responsibilities … </li></ul>Enterprise SPICE Kick-off October 2007
  10. 10. Structure, Roles and Responsibilities <ul><li>Sponsors/Partners: Senior Executives with Strong Stake in Enterprise Process Improvement </li></ul><ul><li>Co-lead the Advisory Board </li></ul><ul><li>Advisory Board/Board of Directors: Senior Executives and Advocates with Strong Stakes/Interests in Enterprise Process Improvement; may include representatives of various standards/ models being integrated </li></ul><ul><li>Establishes operating and decision-making procedures for the Board </li></ul><ul><li>Approves criteria for disciplines and standards to be integrated </li></ul><ul><li>Approves recommended disciplines and standards </li></ul><ul><li>Elicits requests from stakeholders for disciplines and standards, as well as change requests and comments on existing content </li></ul><ul><li>Approves project plans for baseline model and further evolution </li></ul><ul><li>Approves initial baseline model and other final work products </li></ul><ul><li>Provides/recommends subject matter experts to participate on Technical (Author) Team </li></ul><ul><li>Provides feedback to regarding progress, status, issues, etc. </li></ul>Enterprise SPICE Kick-off October 2007
  11. 11. Board Operating Procedures <ul><li>How will the board operate? </li></ul><ul><li>Leadership (co-leads, rotating, ?) </li></ul><ul><li>Decision-making (consensus, quorum, ?) </li></ul><ul><li>Meetings (frequency, mode, ?) </li></ul>Enterprise SPICE Kick-off October 2007
  12. 12. Structure, Roles and Responsibilities (continued) <ul><li>Technical (Author) Team: Very experienced model writers and standards integrators for the small core author team; several subject matter experts (buddies) called upon to assist authors in particular areas (extended author team) </li></ul><ul><li>Establishes project plan for initial model, and further evolution </li></ul><ul><li>Establishes criteria for new disciplines and standards </li></ul><ul><li>Analyzes new discipline and standards requests vs. criteria and makes recommendations to Advisory Board </li></ul><ul><li>Discusses and decides on technical issues </li></ul><ul><li>Develops work products </li></ul><ul><li>Resolves and addresses approved review comments </li></ul><ul><li>Provides status updates to Advisory Board </li></ul><ul><li>Leadership: Need to decide co-leads for Technical Author Team </li></ul>Enterprise SPICE Kick-off October 2007
  13. 13. Structure, Roles and Responsibilities (continued) <ul><li>Assessment Team: ISO/IEC 15504 qualified lead assessors </li></ul><ul><li>Conduct trial assessments using Enterprise SPICE work products and report any problems/issues </li></ul><ul><li>Leadership: Need to decide co-leads for Assessment Team </li></ul><ul><li>Stakeholders/reviewers </li></ul><ul><li>Provide inputs to product development </li></ul><ul><li>Review and comment on interim work products </li></ul>Enterprise SPICE Kick-off October 2007

×