TY - GEN
T1 - Communication patterns of agile requirements engineering
AU - Abdullah, Nik Nailah Binti
AU - Honiden, Shinichi
AU - Sharp, Helen
AU - Nuseibeh, Bashar
AU - Notkin, David
PY - 2011/12/15
Y1 - 2011/12/15
N2 - An agile software development team relies on communication and collaboration to perform requirements engineering activities, rather than on dedicated analysis tools or documentation. Evidence from practice indicates that two simple physical artefacts (story cards and the wall), used in a particular and disciplined manner, and supported by appropriate social activity, are key to the success of co-located agile teams. However, little is known about this social activity or how communication and collaboration supports requirements activities in this setting. This paper reports an empirical study of a commercial agile team to investigate this issue. Using a combination of qualitative data collection and cognitive analysis techniques, we found evidence of gathering, evolving and clarifying requirements that are managed through patterns of communication. These patterns suggest that a form of situated conceptualization, which we have termed 'shared conceptualization', underpins the team's requirements engineering activities.
AB - An agile software development team relies on communication and collaboration to perform requirements engineering activities, rather than on dedicated analysis tools or documentation. Evidence from practice indicates that two simple physical artefacts (story cards and the wall), used in a particular and disciplined manner, and supported by appropriate social activity, are key to the success of co-located agile teams. However, little is known about this social activity or how communication and collaboration supports requirements activities in this setting. This paper reports an empirical study of a commercial agile team to investigate this issue. Using a combination of qualitative data collection and cognitive analysis techniques, we found evidence of gathering, evolving and clarifying requirements that are managed through patterns of communication. These patterns suggest that a form of situated conceptualization, which we have termed 'shared conceptualization', underpins the team's requirements engineering activities.
KW - Collaboration
KW - Communication
KW - Situated cognition
UR - http://www.scopus.com/inward/record.url?scp=83255170963&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=83255170963&partnerID=8YFLogxK
U2 - 10.1145/2068783.2068784
DO - 10.1145/2068783.2068784
M3 - Conference contribution
AN - SCOPUS:83255170963
SN - 9781450308908
T3 - Proceedings of the 1st Agile Requirements Engineering Workshop, AREW'11 - In Conjunction with ECOOP'11
BT - Proceedings of the 1st Agile Requirements Engineering Workshop, AREW'11 - In Conjunction with ECOOP'11
T2 - 1st Agile Requirements Engineering Workshop, AREW'11 - In Conjunction with ECOOP'11
Y2 - 26 July 2011 through 26 July 2011
ER -