What is the Manifesto?
In September 2009 a group of experts in Software Process Improvement (SPI) from all over the world gathered in connection with the EuroSPI Conference for a work
shop at Universidad de Alcalá in Spain. EuroAsiaSPI²'s mission is to develop an experience and knowledge exchange platform for Europe where SPI practices
can be discussed and exchanged and knowledge can be gathered and shared.
The Manifesto defines values and principles for making SPI work.
In early 2010 the SPI Manifesto has been published the first time.
Below are pictures from the SPI Manifesto editorial team at the historical college in Alcala and the Cervantez room in that college (the birth place of the SPI Manifesto).
SPI Manifesto Ambassadors
The experience shows that not all assessments lead to a sustainable improvement. Capability assessments are used to analyse the current status and with a status information which is valid only a certain period. However, the findings of such assessments are not considered in internal improvement programs, or in case of improvement assessments the proposed solutions are not implemented due to missing practical solutions or missing support from management. Also, too often companies achieve a good result in one project instead of trying to achieve an improvement that can help to improve all projects in the organisation. Additionally, not all assessments result in a list of practical improvement actions and the latter are not tracked until closure.
This is why in 2009 the SPI Manifesto has been created to emphasize the key success factors to make improvement work and publish principles and values as a guidance. Every year EuroSPI as a workshop about this improvement topic and the SPI manifesto. SPI Manifesto Ambassadors are experts who are willing to support an SPI (System, Software, Service Process Improvement ) Manifesto.
How did the term SPI evolve over time?
In the 90s EuroAsiaSPI² defined the term as Software Process Improvement. In 2001 - 2010 the SPI term was extended to System Software Process Improvement and Innovation. In 2012 the SPI term interpretation was further enhanced to System, Software, Services Process and Product Improvement and Innovation. In 2016 the conference talked about the connected systems (e.g. vehicle in the cloud) so that the terms safety, security, and infrastructure got included. Therefore the most recent interpretation of the SPI term is System, Software, Services, Safety, and Security Process and Product Improvement, Innovation, and Infrastructure.
This means that over the last 25 years the SPI term developed from a plain definition to a multi-sectoral understanding S(5)P(2)I(3). This extended understanding of the term SPI allows to use it in modern engineering of complex systems.
When the SPI Manifesto was developed in 2009 still the traditional term Software Process Improvement was used as an underlying paradigm. Since the SPI term developed in the community to a concept of S(5)P(2)I(3) we expect a further development of the SPI Manifesto in the next years.
How do we plan to further develop the SPI Manifesto?
The current version of the SPI Manifesto describes three values and 10 principles. Each value is described with a context, a value, and hints how to achieve it. Each principle is described with an explanation and an example. The SPI Manifesto shall be referenced in future by all papers and each paper shall contain a section about how a SPI manifesto value or principle can be mapped. If the paper addresses aspects that are not covered by the SPI Manifesto so far the authors shall write new ideas of values and principles to be included.
