Corporate Competencies – When Individual Competencies Only Do a Little Difference
Training of individuals in requirements engineering has been done for decades all over the world, but still, it is the most problematic process area in the industry. This paper argues that there are many reasons for this and focuses on one that is clearly at the root of causes. Requirements engineer...
Saved in:
Published in | Systems, Software and Services Process Improvement pp. 309 - 316 |
---|---|
Main Authors | , |
Format | Book Chapter |
Language | English |
Published |
Cham
Springer International Publishing
|
Series | Communications in Computer and Information Science |
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | Training of individuals in requirements engineering has been done for decades all over the world, but still, it is the most problematic process area in the industry. This paper argues that there are many reasons for this and focuses on one that is clearly at the root of causes. Requirements engineering, as defined by INCOSE [3], is a team discipline, not an individual discipline. Only when a development team and key stakeholders are cooperating on establishing the best possible input to technical engineering, it will become a success. There is nothing wrong with the teachings in the requirements engineering classes, but as a discipline, requirements engineering needs to be reframed in an organizational context. This paper suggests a practical approach to establishing corporate competencies in Expectations Engineering (EE) by applying all the principles in the SPI Manifesto. |
---|---|
ISBN: | 9783031155581 3031155580 |
ISSN: | 1865-0929 1865-0937 |
DOI: | 10.1007/978-3-031-15559-8_22 |