Article Review: Requirements Engineer in Agile Software Development

This assignment is an article review that critically examines the role of the requirements engineer as a liaison officer within the context of agile software development. The review analyzes Hochmuller's (2011) article, which redefines the requirements engineer's role and emphasizes the importance of customer communication in agile projects. The review discusses the challenges in agile requirements engineering, such as cost estimation, responsibility shifts, and requirement quality. It also highlights the benefits of having a skilled requirements engineer to bridge the gap between customers and developers. The article review provides a comprehensive overview of the topic, exploring the agile software development methods and the role of the requirement engineer, while also acknowledging the limitations of the article and suggesting areas for future research. The review also references other relevant studies, such as those by Abrahamsson et al. (2017) and Moran (2014), to provide a broader understanding of the topic.

Running head: ARTICLE REVIEW
Article Review: The Requirements Engineer as a Liaison Officer in Agile Software Development
Name of the Student:
Name of the University:

1ARTICLE REVIEW
Article 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 Agile
Software Development”, focuses on to redefine the role of requirements engineer and customer in
supportive onsite liaison based on the agile development paradigm. This article also provides of agile
requirements issues on customer’s perspective. The author stated that agile software development is
innovative software development process. This point fits with the ideas of our course as the agile method
provides way to develop of quality software and allow of accommodation change requests at each stage
of the software development processes. According to Abrahamsson et al., (2017), agile development
methods are emerged as an alternative to the phase driven process plan at short time to market. This
article significantly discusses the issues of agile methods which help the users to understand the
challenges into agile requirement engineering into medium as well as large sized projects. The discussed
challenges 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 developer
communication into agile projects by means of the agile requirement engineer. The strength of this article
is that it performs a study on the agile requirement engineering practices. The weakness of this article is
that there is lack of analysis of the agile software development methods; therefore there is lack of
understanding of the requirement engineer about this method. However, due to lack of technical nature of
the article analysis, the article is only the interest of the experts and researcher. After detailed background
review on the agile requirement issues and agile software development studies, the author turns the
attention to main focus of the study. After identifying the challenges, the role of requirement engineer as
liaison officer is being discussed in this research context. Moran (2014) stated that the role of agile
requirement engineer is provided in detail based on the actual agile methods applied in the technical
projects. The benefit of the agile project is to have skilled agile requirements engineer to bridge gap
among the customers as well as developers.
In this particular article, the author discusses that the role of the agile requirement engineer is to
support the agile customers in order to fulfill the project responsibilities. Hochmuller (2011) discussed
that the main idea of the agile method is that the development of system involves with different technical
variables such as time frame, technology, resources to change the organizational process. It makes the
process of development unpredictable, complex with requirement to flexible of the system development
process to respond to the changes in the project. Smith (2001) argued that as the result of the agile
software development, the system is to be produced that becomes useful when it is delivered. In this
article, the author discusses the tasks of the agile requirement engineer as liaison officer. The requirement

2ARTICLE REVIEW
engineer plays the role of liaison officer as they are available at site of the customers. The new role is also
set into this research context to relate the roles into the agile projects followed by the benefit of the
customers along with the development teams into the agile projects.
In conclusion, Hochmulleris article provides with a comprehensive reviews of the role of
requirement engineer into agile software development projects and represents of findings from the own
study of the author. It is also observed that there is more research on the topic is required to discuss the
agile software development methods and the role of the requirement engineer. On the other hand, the
author fails to explain the findings into simple terms and provide with real world examples of this
research to put down the audiences interest into the research study. The relevance of this study is
inclusive along with existing study is therefore rather compromised by moderately limited accessibility.
It is also analyzed that the availability of the customer in the agile development process helps to reduce
the risks into the project by minimizing the errors and providing development. A large portion of the
project is shifted to reduce the development risks into the project work. Into the agile development, it is
the responsibility of customer liaison to bear any type of challenges.

3ARTICLE REVIEW
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods:
Review and analysis. arXiv preprint arXiv:1709.08439.
Hochmüller, E. (2011). The requirements engineer as a liaison officer in agile software development.
In Proceedings of the 1st workshop on agile requirements engineering (p. 2). ACM.
Moran, A. (2014). Agile Software Development. In Agile Risk Management (pp. 1-16). Springer
International Publishing.
Smith, J. (2001). “Missouri Butterflies.” Scientific Missourian, 36(2), 25-28.