Requirements Management Guidelines for an Organization
Fernandez Martinez, Patricia (2023)
2023
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2023061223583
https://urn.fi/URN:NBN:fi:amk-2023061223583
Tiivistelmä
This thesis project aimed to develop the necessary content for guidelines intended for employees of a Requirements Management (RM) service.
The project was structured as a qualitative case study, combining theoretical and practical knowledge to create the content for the proposed guidelines. Various sources were consulted to gather Requirements Management processes aligned with the Project Management Institute PMBOK guide and European ISO standards. Additionally, I provided summaries of methods for defining requirements and identified the essential competencies and skills required to become an expert in this field. The project also included a discussion on the digitalization and digital transformation of companies, highlighting the advantages of utilizing an ALM (Application Lifecycle Management) software tool for requirements management. Theoretical knowledge was further complemented by interviews conducted with actual requirement experts in Construction projects, as well as users of the Siemens Polarion ALM tool.
The main conclusions underscore the importance of establishing two primary approaches to work:
When requirements are documented and require review and alignment among stakeholders, it is crucial to establish streamlined processes and workflows that facilitate automation.
When requirements are being developed from scratch, an Agile mindset and appropriate tools for elicitation and analysis are necessary.
In terms of requirement specification, the preferred approach should be "use cases" whenever applicable.
The project was structured as a qualitative case study, combining theoretical and practical knowledge to create the content for the proposed guidelines. Various sources were consulted to gather Requirements Management processes aligned with the Project Management Institute PMBOK guide and European ISO standards. Additionally, I provided summaries of methods for defining requirements and identified the essential competencies and skills required to become an expert in this field. The project also included a discussion on the digitalization and digital transformation of companies, highlighting the advantages of utilizing an ALM (Application Lifecycle Management) software tool for requirements management. Theoretical knowledge was further complemented by interviews conducted with actual requirement experts in Construction projects, as well as users of the Siemens Polarion ALM tool.
The main conclusions underscore the importance of establishing two primary approaches to work:
When requirements are documented and require review and alignment among stakeholders, it is crucial to establish streamlined processes and workflows that facilitate automation.
When requirements are being developed from scratch, an Agile mindset and appropriate tools for elicitation and analysis are necessary.
In terms of requirement specification, the preferred approach should be "use cases" whenever applicable.