Software Delivery Concept
Maula, Marjo (2014)
Metropolia Ammattikorkeakoulu
2014
All rights reserved
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2014052910964
https://urn.fi/URN:NBN:fi:amk-2014052910964
Tiivistelmä
The purpose of this study was to create a software delivery concept for ERP in IT-project, comparable metrics for the project management and make a improvement list of the future actions.
Both qualitative and quantitative research methodology was utilized in this study. The qualitative research data consists of six in-depth interviews. The interviews were done with project people and people who are working in global projects. Quantitative data research data was gathered with a questionnaire. Six questionnaires were sent for IT-project pro-fessionals in international companies.
The results from both the research indicate similar type of challenges faced in the projects: requirements are unclear, scope creep happens, communication is insufficient, full tracea-bility is not visible and test automation is not fully implemented. Test automation is seen as a key opportunity to speed up release cycle times and manual testing is useful in explora-tory and e2e (end-to-end) testing.
The author recommends that a couple of focus areas in scope will be improved in the next release, for example communication, scheduling and measuring, traceability from require-ments to deployment and automation in testing and in configuration.
Both qualitative and quantitative research methodology was utilized in this study. The qualitative research data consists of six in-depth interviews. The interviews were done with project people and people who are working in global projects. Quantitative data research data was gathered with a questionnaire. Six questionnaires were sent for IT-project pro-fessionals in international companies.
The results from both the research indicate similar type of challenges faced in the projects: requirements are unclear, scope creep happens, communication is insufficient, full tracea-bility is not visible and test automation is not fully implemented. Test automation is seen as a key opportunity to speed up release cycle times and manual testing is useful in explora-tory and e2e (end-to-end) testing.
The author recommends that a couple of focus areas in scope will be improved in the next release, for example communication, scheduling and measuring, traceability from require-ments to deployment and automation in testing and in configuration.