logo

Liaison Officer in Agile Software Development

   

Added on  2020-05-04

4 Pages936 Words158 Views
Running head: ARTICLE REVIEWArticle Review: The Requirements Engineer as a Liaison Officer in Agile Software DevelopmentName of the Student:Name of the University:
Liaison Officer in Agile Software Development_1
1ARTICLE REVIEWArticle Review: “The Requirements Engineer as a Liaison Officer in Agile Software Development”Hochmuller (2011), in the article “The Requirements Engineer as a Liaison Officer in AgileSoftware Development”, focuses on to redefine the role of requirements engineer and customer insupportive onsite liaison based on the agile development paradigm. This article also provides of agilerequirements issues on customer’s perspective. The author stated that agile software development isinnovative software development process. This point fits with the ideas of our course as the agile methodprovides way to develop of quality software and allow of accommodation change requests at each stageof the software development processes. According to Abrahamsson et al., (2017), agile developmentmethods are emerged as an alternative to the phase driven process plan at short time to market. Thisarticle significantly discusses the issues of agile methods which help the users to understand thechallenges into agile requirement engineering into medium as well as large sized projects. The discussedchallenges are cost estimation, shifts into responsibility, quality of requirements and quality requirements.The purpose of this article is to perform a detailed discussion to improve the customer developercommunication into agile projects by means of the agile requirement engineer. The strength of this articleis that it performs a study on the agile requirement engineering practices. The weakness of this article isthat there is lack of analysis of the agile software development methods; therefore there is lack ofunderstanding of the requirement engineer about this method. However, due to lack of technical nature ofthe article analysis, the article is only the interest of the experts and researcher. After detailed backgroundreview on the agile requirement issues and agile software development studies, the author turns theattention to main focus of the study. After identifying the challenges, the role of requirement engineer asliaison officer is being discussed in this research context. Moran (2014) stated that the role of agilerequirement engineer is provided in detail based on the actual agile methods applied in the technicalprojects. The benefit of the agile project is to have skilled agile requirements engineer to bridge gapamong the customers as well as developers. In this particular article, the author discusses that the role of the agile requirement engineer is tosupport the agile customers in order to fulfill the project responsibilities. Hochmuller (2011) discussedthat the main idea of the agile method is that the development of system involves with different technicalvariables such as time frame, technology, resources to change the organizational process. It makes theprocess of development unpredictable, complex with requirement to flexible of the system developmentprocess to respond to the changes in the project. Smith (2001) argued that as the result of the agilesoftware development, the system is to be produced that becomes useful when it is delivered. In thisarticle, the author discusses the tasks of the agile requirement engineer as liaison officer. The requirement
Liaison Officer in Agile Software Development_2

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Managing Quality Requirements in Software Development
|10
|1875
|98

Agile Methods: A Fashion That Has Not Become Outdated
|8
|1943
|301

Article on Agile Software Development
|7
|1278
|158

Software Testing: Achievements, Challenges, Dreams
|12
|828
|55

Presentation on Moving from Waterfall to Agile.
|7
|300
|90

Review of Research Paper on Application of Software Methodologies for Designing Data Warehouse System
|7
|1872
|216