Presented by 劉乃菀 Department of Computer Science & information Engineering May 30 th, 2011

Background A three-days observation in March, 2009 A large telecommunication and media company in the UK An agile development team with 2 customers and 5 developers, one of them is a project manager 2011/5/302

Physical Artefacts of the Team A cabinet (a wall) Index cards and story cards, which are based on user stories Acceptance tests, discussed in stand-up meeting and written at the back of the story cards A big whiteboard, in front of the cabinet Many small whiteboards 2011/5/303

Daily Practice of the Team Stand-up meeting Where: Next to the wall What to discuss: The work they did the day before Problems they have encountered The work / story cards for today The partners for today 2011/5/304

Daily Practice of the Team Pair-programming sessions Driver: The one who currently has control of the keyboard Navigator: The one who contributes to the task verbally and by other means 2011/5/305

Data Gathering Video recordings of the daily stand-up meeting Audio recordings of different pairs of each day 2011/5/306

Data Analyzing 2011/5/307

Findings ArtefactPrimary Usage Cabinet (Wall) Arrangement Story card Customer’s perspective System’s behavior Acceptance test The way to implement a user story Big whiteboard Data structure Algorithm Small whiteboard Logical steps 2011/5/308

Discussion The various artefacts influence the communication process in a mutually constraining relationship with the context. The collaboration among different participation role changed the relation of how the artefacts are used together. 2011/5/309