The requirements engineer as a liaison officer in agile software development

Proceedings of the 1st Agile Requirements Engineering Workshop, AREW'11 - In Conjunction with ECOOP'11

Volumn , Issue , 2011, Pages

  Hochmüller, Elke ^a  

^a CARINTHIA UNIVERSITY OF APPLIED SCIENCES   (Austria)

Author keywords

Agile customer; Agile requirements engineer; Customer liaison

Indexed keywords

AGILE CUSTOMER; AGILE DEVELOPMENT; AGILE SOFTWARE DEVELOPMENT; CUSTOMER LIAISON; REQUIREMENTS ENGINEERS;

CUSTOMER SATISFACTION; ENGINEERS; REQUIREMENTS ENGINEERING; SALES; SOFTWARE DESIGN; TECHNICAL PRESENTATIONS;

ENGINEERING;

EID: 83255164805     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2068783.2068785     Document Type: Conference Paper

References (13)

1. Albin, S.T. 2003. The Art of Software Architecture: Design Methods and Techniques. Wiley, Indianapolis, Ind.
2. Cao, L., Ramesh, B. 2008 Agile Requirements Engineering Practices: An Empirical Study. IEEE Software. 25, 1 (Jan./Feb. 2008), 60-67. DOI=http://dx.doi.org/10.1109/MS.2008.1.
3. Eberlein, A., Leite, J.C.S.P. 2002. Agile Requirements Definition: A View from Requirements Engineering. In Proceedings of the International Workshop on Time-Constrained Requirements Engineering (Essen, Germany, September 09, 2002). TCRE'02. http://www-di.inf.puc-rio.br/~julio//tcre-site/p4.pdf
4. Faber, R. 2010. Architects as Service Providers. IEEE Software. 27, 2 (Mar./Apr. 2010), 33-40. DOI=http://dx.doi.org/10.1109/MS.2010.37
5. Fowler, M. 2003. Who Needs an Architect? IEEE Software. 20, 5 (Sep./Oct. 2003), 11-13. DOI=http://dx.doi.org/10.1109/MS.2003.1231144
6. Hazrati, V. 2008. The Shiny New Agile Architect. Agile Journal 3, 1, CMC Media (2008)
7. Hochmüller, E. 1999. Towards the Proper Integration of Extra-Functional Requirements. The Australian Journal of Information Systems. 6, 2, 98-117 (1999)
8. Hochmüller, E., Mittermeir, R.T. Agile Process Myths. In Scrutinizing Agile Practices (Leipzig, Germany May 2008). APSO'08. ACM, New York, NY, 5-8. DOI=http://doi.acm.org/10.1145/1370143.1370145
9. IEEE: IEEE Recommended Practice for Software Requirements Specifications. IEEE Std. 830-1993 (1993)
10. Maiden, N., Jones, S. 2010. Agile Requirements - Can We Have Our Cake and Eat It Too? IEEE Software. 27, 3 (May/June 2010), 87-88. DOI=http://dx.doi.org/ 10.1109/MS.2010.67.
11. Martin, A., Biddle, R., Noble, J. 2009. XP Customer Practices: A Grounded Theory. In Proceedings of the Agile Conference (Chicago, IL, Aug. 24-28, 2009). AGILE'09. 33-40. http://dx.doi.org/10.1109/AGILE.2009.68
12. Martin, A., Biddle, R., Noble, J. 2009. XP Customer Team: A Grounded Theory. In Proceedings of the Agile Conference (Chicago, IL, Aug. 24-28, 2009). AGILE'09. 57-64. http://dx.doi.org/10.1109/AGILE.2009.70
13. Orr, K. 2004. Agile Requirements: Opportunity or Oxymoron? IEEE Software. 21, 3 (May/June 2004), 71-73. DOI=http://dx.doi.org/10.1109/MS.2004.1293075.