The requirements engineer as a liaison officer in agile software development

Authors:
Elke Hochmüller
Affiliations:
Carinthia University of Applied Sciences, Klagenfurt, Austria
Venue:
Proceedings of the 1st Workshop on Agile Requirements Engineering
Year:
2011

Citing 9
Cited 2

The Art of Software Architecture: Design Methods and Techniques

The Art of Software Architecture: Design Methods and Techniques
Who Needs an Architect?

IEEE Software
Agile Requirements Engineering Practices: An Empirical Study

IEEE Software
Agile Process Myths

Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
Agile Requirements: Opportunity or Oxymoron?

IEEE Software
XP Customer Practices: A Grounded Theory

AGILE '09 Proceedings of the 2009 Agile Conference
The XP Customer Team: A Grounded Theory

AGILE '09 Proceedings of the 2009 Agile Conference
Architects as Service Providers

IEEE Software
Agile Requirements Can We Have Our Cake and Eat It Too?

IEEE Software

10 myths of software quality

REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Redefinition of the requirements engineer role in mjølner's software development process

REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality

Quantified Score

Hi-index	0.00

Visualization

Abstract

In agile development projects, customers are facing considerable challenges because of the substantial amount and depth of their responsibility for the overall progress and success of the project. This paper proposes to extend and redefine the role of a requirements engineer working together with the customer in a supportive on-site liaison in accordance with the agile paradigm. Based on a discussion of requirements-related customer issues, the profile of such an agile requirements engineer as liaison officer will be outlined and the prospected benefits will be stated.