Abstract
Agile software development methods suggest that sharing tasks between a pair of developers has advantages over letting them work as individuals. This effect has been observed in designing and coding tasks too. However, it is not yet known whether or not pairing on requirements engineering tasks could deliver a similar benefit at an early phase of software projects. Based on first-hand experience in pairing development of the OpenOME tool, we analyse the evolving stakeholder requirements using the i*/Tropos method. Our findings show that sharing tasks of different roles becomes more effective when those roles are played by one stakeholder, possibly due to smaller communication delay at a shorter distance. © 2011 ACM.
Author supplied keywords
Cite
CITATION STYLE
Yu, Y., & Sharp, H. (2011). Analysing requirements in a case study of pairing. In Proceedings of the 1st Agile Requirements Engineering Workshop, AREW’11 - In Conjunction with ECOOP’11. https://doi.org/10.1145/2068783.2068787
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.