Organizing self-organizing teams
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Using grounded theory to study the human aspects of software engineering
Human Aspects of Software Engineering
The requirements engineer as a liaison officer in agile software development
Proceedings of the 1st Workshop on Agile Requirements Engineering
How much is just enough?: some documentation patterns on Agile projects
Proceedings of the 15th European Conference on Pattern Languages of Programs
Developing a grounded theory to explain the practices of self-organizing Agile teams
Empirical Software Engineering
Hi-index | 0.00 |
The initial definition of XP resulted in many people interpreting the on-site customer to be a single person. We have conducted extensive qualitative research studying XP teams, and one of our research questions was “who is the customer”? We found that, rather than a single person, a customer team always exists. In this paper we outline the different roles that were typically on the team, which range from the recognized “Acceptance Tester” role to the less recognized roles of “Political Advisor” and “Super-Secretary”.