The Experts below are selected from a list of 8406 Experts worldwide ranked by ideXlab platform
Yves Wautelet - One of the best experts on this subject based on the ideXlab platform.
-
Agile manifesto and Practices selection for tailoring software development a systematic literature review
Product Focused Software Process Improvement, 2018Co-Authors: Soreangsey Kiv, Samedi Heng, Manuel Kolp, Yves WauteletAbstract:Agile methods have been largely used for many years to provide developers with a flexible software development process leading to software quality improvement. To get the best results and eliminate unnecessary efforts, the development team should select the most appropriate methods and techniques. The fundamental core of an Agile method has to be well-understood before deciding which parts of the method need to be adopted. We believe that the quickest way to do so is to understand the prescripts of the Agile Manifesto. Many researches have proposed different tailoring approaches based on the relation and straight-forward interpretation between each Agile Practice and Agile values or principles. We however have observed that Agile practitioners do not dedicate the necessary attention to the Agile Manifesto before adopting Agile methods or Practices and directly use them. It is because the importance of Agile Manifesto in tailoring context is not obvious enough to the community. This study aims at doing a systematic literature review on the existing case studies, to verify the relation between the Agile Manifesto and Agile Practice selection.
Soreangsey Kiv - One of the best experts on this subject based on the ideXlab platform.
-
Agile manifesto and Practices selection for tailoring software development a systematic literature review
Product Focused Software Process Improvement, 2018Co-Authors: Soreangsey Kiv, Samedi Heng, Manuel Kolp, Yves WauteletAbstract:Agile methods have been largely used for many years to provide developers with a flexible software development process leading to software quality improvement. To get the best results and eliminate unnecessary efforts, the development team should select the most appropriate methods and techniques. The fundamental core of an Agile method has to be well-understood before deciding which parts of the method need to be adopted. We believe that the quickest way to do so is to understand the prescripts of the Agile Manifesto. Many researches have proposed different tailoring approaches based on the relation and straight-forward interpretation between each Agile Practice and Agile values or principles. We however have observed that Agile practitioners do not dedicate the necessary attention to the Agile Manifesto before adopting Agile methods or Practices and directly use them. It is because the importance of Agile Manifesto in tailoring context is not obvious enough to the community. This study aims at doing a systematic literature review on the existing case studies, to verify the relation between the Agile Manifesto and Agile Practice selection.
Samedi Heng - One of the best experts on this subject based on the ideXlab platform.
-
Agile manifesto and Practices selection for tailoring software development a systematic literature review
Product Focused Software Process Improvement, 2018Co-Authors: Soreangsey Kiv, Samedi Heng, Manuel Kolp, Yves WauteletAbstract:Agile methods have been largely used for many years to provide developers with a flexible software development process leading to software quality improvement. To get the best results and eliminate unnecessary efforts, the development team should select the most appropriate methods and techniques. The fundamental core of an Agile method has to be well-understood before deciding which parts of the method need to be adopted. We believe that the quickest way to do so is to understand the prescripts of the Agile Manifesto. Many researches have proposed different tailoring approaches based on the relation and straight-forward interpretation between each Agile Practice and Agile values or principles. We however have observed that Agile practitioners do not dedicate the necessary attention to the Agile Manifesto before adopting Agile methods or Practices and directly use them. It is because the importance of Agile Manifesto in tailoring context is not obvious enough to the community. This study aims at doing a systematic literature review on the existing case studies, to verify the relation between the Agile Manifesto and Agile Practice selection.
Manuel Kolp - One of the best experts on this subject based on the ideXlab platform.
-
Agile manifesto and Practices selection for tailoring software development a systematic literature review
Product Focused Software Process Improvement, 2018Co-Authors: Soreangsey Kiv, Samedi Heng, Manuel Kolp, Yves WauteletAbstract:Agile methods have been largely used for many years to provide developers with a flexible software development process leading to software quality improvement. To get the best results and eliminate unnecessary efforts, the development team should select the most appropriate methods and techniques. The fundamental core of an Agile method has to be well-understood before deciding which parts of the method need to be adopted. We believe that the quickest way to do so is to understand the prescripts of the Agile Manifesto. Many researches have proposed different tailoring approaches based on the relation and straight-forward interpretation between each Agile Practice and Agile values or principles. We however have observed that Agile practitioners do not dedicate the necessary attention to the Agile Manifesto before adopting Agile methods or Practices and directly use them. It is because the importance of Agile Manifesto in tailoring context is not obvious enough to the community. This study aims at doing a systematic literature review on the existing case studies, to verify the relation between the Agile Manifesto and Agile Practice selection.
Engström Emelie - One of the best experts on this subject based on the ideXlab platform.
-
A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements
'Elsevier BV', 2018Co-Authors: Bjarnason Elizabeth, Unterkalmsteiner Michael, Borg Markus, Engström EmelieAbstract:[Context] It is an enigma that Agile projects can succeed ‘without requirements’ when weak requirementsengineering is a known cause for project failures. While Agile development projects often manage well withoutextensive requirements test cases are commonly viewed as requirements and detailed requirements are documented astest cases.[Objective] We have investigated this Agile Practice of using test cases as requirements to understand how test casescan support the main requirements activities, and how this Practice varies.[Method] We performed an iterative case study at three companies and collected data through 14 interviews and 2focus groups.[Results] The use of test cases as requirements poses both benefits and challenges when eliciting, validating,verifying, and managing requirements, and when used as a documented agreement. We have identified five variants ofthe test-cases-as-requirements Practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict andstand-alone manual for which the application of the Practice varies concerning the time frame of requirementsdocumentation, the requirements format, the extent to which the test cases are a machine executable specification andthe use of tools which provide specific support for the Practice of using test cases as requirements.[Conclusions] The findings provide empirical insight into how Agile development projects manage andcommunicate requirements. The identified variants of the Practice of using test cases as requirements can be used toperform in-depth investigations into Agile requirements engineering. Practitioners can use the providedrecommendations as a guide in designing and improving their Agile requirements Practices based on projectcharacteristics such as number of stakeholders and rate of change.EAS
-
A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements
'Elsevier BV', 2016Co-Authors: Bjarnason Elizabeth, Unterkalmsteiner Michael, Borg Markus, Engström EmelieAbstract:[Context] It is an enigma that Agile projects can succeed "without requirements" when weak requirements engineering is a known cause for project failures. While Agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. [Objective] We have investigated this Agile Practice of using test cases as requirements to understand how test cases can support the main requirements activities, and how this Practice varies. [Method] We performed an iterative case study at three companies and collected data through 14 interviews and 2 focus groups. [Results] The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. We have identified five variants of the test-cases-as-requirements Practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict and stand-alone manual for which the application of the Practice varies concerning the time frame of requirements documentation, the requirements format, the extent to which the test cases are a machine executable specification and the use of tools which provide specific support for the Practice of using test cases as requirements. [Conclusions] The findings provide empirical insight into how Agile development projects manage and communicate requirements. The identified variants of the Practice of using test cases as requirements can be used to perform in-depth investigations into Agile requirements engineering. Practitioners can use the provided recommendations as a guide in designing and improving their Agile requirements Practices based on project characteristics such as number of stakeholders and rate of change