OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 1 of 9 A first review of the SPI Manifesto BCS SPIN, 14 December 2009 C. C. Shelley OXFORD SOFTWARE ENGINEERING Ltd 9 Spinners Court, 53 West End, Witney, Oxfordshire OX28 1NH Tel. +44 (0)

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 2 of 9 Background from p2 of the manifesto... SPI experts met in September 2009 at Universidad de Alcalá 30 participants brainstormed 4 core values and 14 principles Used affinity analysis and group thinking exercises to draft the manifesto The participants say that: –Manifest[o] gives expression to state-of the-art knowledge on SPI –Use it for obtaining knowledge of SPI

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 3 of 9 Objectives of this workshop Gain an understanding of what the experts think is important Perhaps propose additions and revisions

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 4 of 9 Agenda Overview - (10 minutes prep) Walkthrough – seeking comments, corrections and improvements Decision –Good – wish to participate in the development of the manifesto –No good Action –Begin work to identify additions and revisions

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 5 of 9 Overview 4 Values –(edited to become 3 now) 14 principles – (11 now)

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 6 of 9 Values Value A: We truly believe that SPI must get people actively involved, and affect their daily activities Value B: We truly believe that SPI is what you do to make business succeed Value C: We truly believe that SPI is inherently linked with change

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 7 of 9 Principles Principle 1: You should know the culture of the organization and focus SPI on their needs Principle 2: You should motivate people – through empowerment, involvement, training, incentives, management support and commitment Principle 3:You should base process improvement on experience and measurements Principle 4: You should create a learning organization and share process experiences Principle 5: Your improvement effort must support the organization's vision, business objectives and measurement objectives Principle 6: Your improvement effort should use process descriptions to establish common agreements Principle 7: Your improvement effort can be supported by models but not restricted by them Models should be dynamic and adaptable to the environment Principle 8: Your improvement effort must apply risk management Principle 9: You should apply organizational change management to your improvement effort. Principle [#]10: You should support the people and blame the process Principle 11: You should be consequent or lose your focus

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 8 of 9 O X F O R D S O F T W A R E E N G I N E E R I N G L I M I T E D 9 Spinners Court, 53 West End, Witney, Oxfordshire OX28 1NH Tel. +44 (0)

OXFORD SOFTWARE ENGINEERING Consulting Software Engineers © OSEL 2009 Page 9 of 9