1 Agile Experience communication and collaboration in agile software development teams Elizabeth...
-
Upload
lambert-atkins -
Category
Documents
-
view
224 -
download
2
Transcript of 1 Agile Experience communication and collaboration in agile software development teams Elizabeth...
![Page 1: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/1.jpg)
1
Agile Experience
communication and collaboration in agile software development teams
Elizabeth Whitworth7th September, 2006
![Page 2: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/2.jpg)
2
Research quest?on
What is the experience of being in an agile software development team?
![Page 3: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/3.jpg)
3
Research quest?on
How do agile practices structure and mediate the experience of individuals developing software?
What are the socio-psychological characteristics surrounding agile practices and individuals within a software development team?
![Page 4: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/4.jpg)
4
Study data
18 one-on-one interviews
agile software development literature and community interaction
![Page 5: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/5.jpg)
5
Content of interviews
cohesive vs. non-cohesive teams
agile vs. non-agile teams
personal experiences and/or team activity
project characteristics
![Page 6: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/6.jpg)
6
Grounded theory
theory generation: line-by-line coding
memoing and analysis of data
results of study:high level understanding
confirmation from participants
![Page 7: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/7.jpg)
7
Cohesive teamwork
strong feelings of excitementteams that ‘clicked,’‘gelled,’‘really worked together’’
agile methodologies were seen to support team cohesiveness; more so than traditional software development methodologies
![Page 8: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/8.jpg)
8
Agile practices
the planning game
continuous integration
iterative development and delivery
![Page 9: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/9.jpg)
9
Agile practices
daily stand-ups
information radiators
shared team rooms
pairing
![Page 10: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/10.jpg)
10
Ease & speed
Agile culture:openness, honesty
transparent environment
trust, respect action-based culture
whole team involvement and availability frequent interaction and immersion
![Page 11: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/11.jpg)
11
Collective activity
Buy-in to shared team goals:
provide the most business value to the customer in the least amount of time
![Page 12: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/12.jpg)
12
Collective activity
prioritization & chunking of activitydevelopment around working software
reduce cognitive load
importance and immediacy discipline and rigor
clear measures of success
![Page 13: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/13.jpg)
13
holistic awareness& understanding
of team of project
of product
Context-rich information exchange and activity
![Page 14: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/14.jpg)
14
holistic awareness& understanding
team:familiarity and understanding
observe and refine working relationships
project:involvement and interesthelping and support
product:purpose and meaning
opportunistic action and collaboration
![Page 15: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/15.jpg)
15
Whole team awareness & feedback
constant feedback:whole team awareness and understanding
commitment towards team goalsfrequent and noticeable progress
for example: highly visible information radiators
daily or weekly team meetings
![Page 16: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/16.jpg)
16
Whole team awareness & feedback
whole team agreement, approval, and action
frequent and informal team interactions
social accountability and responsibility
recognition and appreciation
support and motivationshared team goals
self-regulating teams
![Page 17: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/17.jpg)
17
Conclusion detailed and transparent planning and activity
certainty in the project environmentsocial accountability and support
Holistic understanding and competence security and controlinvestment and involvementpride and ownership
balance of structure and freedomindividual freedom and initiative
ability to assess relative importance of goals
![Page 18: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/18.jpg)
18
Next stepsfurther investigation:
observational studiespsychological literature
areas for future study:critical success factorsnegative phenomenaagile practices
application:non-traditional contexts
![Page 19: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/19.jpg)
19
Quest?ons
![Page 20: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/20.jpg)
20
![Page 21: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/21.jpg)
21
![Page 22: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/22.jpg)
22
![Page 23: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/23.jpg)
23
Conceptual frameworkTeamworking‘Self-regulating’, ‘self-managing’, ‘high-performance’
sociotechnical systems theory“the study of the relationships and inter-relationships between the social and technical parts of any system.” - Coakes (2000)
systems thinkingholistic, emergent effects,
dynamics of regulation
![Page 24: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/24.jpg)
24
Study focus: the agile system
This study involved the agile system made up of individuals, agile technology, and the group as a whole
Particularly the relationships between system entities
interdependenciesemergent effects, such as flow
feedback and feedforward mechanismseffects of technology
![Page 25: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/25.jpg)
25
Interview data18 interviews:
five developers, three interaction designers, five project managers, two agile coaches, three developers/project managers
Recruited at conferences, and through contacts in the agile software development community
5 members of the same software development team
Software development community: agile software development conferences and
workshops practitioner literature (print and online ) online correspondence
![Page 26: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/26.jpg)
26
Conducting interviewsExample Questions (initial):
Could you pick a software development team that you found particularly enjoyable or exciting to work in and describe it to me?
Could you describe the physical space the team was in? What was the experience of working in such a team?
Did you feel that [being in the same room] effected your interactions with your team-mates? How so?
Example Questions (later):Did you feel like you were part of the team? Why/why not?
Did you feel that you were able to approach your team members to ask for help? Why/why not?
How was responsibility divided among team members? How did you ensure that everything that needed to get done got done?
![Page 27: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/27.jpg)
27
Coding
Coding occurred line-by-line and provided a means of comparison across diverse participant experiences
Common themes were extracted as categories and explored across situations/participants
![Page 28: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/28.jpg)
28
Theoretical categories
Theoretical categories and related properties and dimensions were developed based on codes and memos
Diversity of data in this study, and complex nature of interactions made it difficult to define a core category about which to construct a comprehensive theory
![Page 29: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/29.jpg)
29
![Page 30: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/30.jpg)
30
![Page 31: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/31.jpg)
31
extra notes - awareness
Details?
![Page 32: 1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.](https://reader035.fdocuments.net/reader035/viewer/2022062315/5697bfa41a28abf838c972ea/html5/thumbnails/32.jpg)
32
extra notes - conclusion
Success, progress and change