jazoon'13 - martin kropp - agile collaboration

24
Successful Collaboration in Agile Software Teams Martin Kropp & Magdalena Mateescu University of Applied Sciences Northwestern Switzerland School of Engineering & School of Applied Psychology

Upload: jazoon13

Post on 17-Jan-2015

422 views

Category:

Technology


2 download

DESCRIPTION

http://guide13.jazoon.com/#/submissions/149

TRANSCRIPT

Page 1: JAZOON'13 - Martin Kropp - Agile Collaboration

Successful Collaboration in

Agile Software Teams

Martin Kropp & Magdalena Mateescu University of Applied Sciences Northwestern Switzerland

School of Engineering & School of Applied Psychology

Page 2: JAZOON'13 - Martin Kropp - Agile Collaboration

|

A Study Report

• Interviews in 11 agile IT companies

• 10 two-hour group interviews - group size of 3 to 5

• 3 one-hour individual interviews

• Total of 44 interviewed people

Page 3: JAZOON'13 - Martin Kropp - Agile Collaboration

|

Interview Methodology

• Development of interview guide

• Semi-structured interviews

• 10 Group interviews, 3 individual interviews - Two

interviewers

• All interviews were recorded and transcribed

• A coding system was developed accordingly to research

questions and the interviews were coded using

MAXQDA

Page 4: JAZOON'13 - Martin Kropp - Agile Collaboration

|

No successful agile project

without agile collaboration

|

Page 5: JAZOON'13 - Martin Kropp - Agile Collaboration

|

What is Agile Collaboration?

Page 6: JAZOON'13 - Martin Kropp - Agile Collaboration

• Face-to-face

• Regular

• Often

• Informal

• Openly

• Under equals

• Focused

• Transparent

• Respectful

• Flexible

Agile Collaboration is …

Page 7: JAZOON'13 - Martin Kropp - Agile Collaboration

|

1. Put People Together

• Open work place

• not only for work

Page 8: JAZOON'13 - Martin Kropp - Agile Collaboration

|

… and distributed teams?

• Always a compromise

• Generates extra effort – think about if it’s worth it

Page 9: JAZOON'13 - Martin Kropp - Agile Collaboration

|

What you can do…

• Integrate into daily stand-up

• Use video-conferencing, skype, chat …

• Organize face-to-face work phases (3-5 days)

• fly them in or fly to them

Page 10: JAZOON'13 - Martin Kropp - Agile Collaboration

|

2. Make Team Self-Organized

• No “hidden” leader

• Can be difficult if the team leader is part of the agile

team

Page 11: JAZOON'13 - Martin Kropp - Agile Collaboration

|

3. Establish Continuity

• Apply “Standard” meetings – all

• Iteration planning, stand-ups, review, retro

• Keep them focused

• Keep them short

• Adapt as necessary

• Keep on with Retrospectives

• Also in long lasting projects

• Introduce variations (different locations, thematic retros)

Page 12: JAZOON'13 - Martin Kropp - Agile Collaboration

|

4. Foster Informal Meetings

• Technical meetings

• As needed architecture, design meetings

• Pair programming

• See 1.

• Others

• User Story Groomings

• Code Reviews (Git)

• Test competitions

Page 13: JAZOON'13 - Martin Kropp - Agile Collaboration

|

5. Make Information Transparent

• Use Boards

• Physical or digital

• Instant availability

• All-in-one view

Page 15: JAZOON'13 - Martin Kropp - Agile Collaboration

|

The Agile Tool Set is more … General development Tools

Communication and collaboration

tools

Physical Tools

Agile Tools

Page 16: JAZOON'13 - Martin Kropp - Agile Collaboration

|

Role of Email

“…. however it is similar with the Email, frankly

spoken, you cannot sent any assignments per

email, it simply does not work. I must construe

it (the meaning of the message), there is no

feedback possible as to what and about the

accuracy. This is similar to Daily, one has to

interpret assets. I have to look the others in the

eye. This is extremely important.” I11:362

Page 17: JAZOON'13 - Martin Kropp - Agile Collaboration

|

The Agile Tool Set is more …

• Automation Infrastructure

CI, VCS, Automation, Test (unit and acceptance),

Deployment

• Collaboration Infrastructure

Issue Tracker, Collaboration Platforms (wiki, forums),

Instant messenger

Page 18: JAZOON'13 - Martin Kropp - Agile Collaboration

In some things unbeatable

• Flexible

• Touchable

• Transparent

• All-in-one view

• Usually in the office

But…

• Not revisable

• Not persistent

• Not distributable

• No links to the digital

information

Physical boards

Page 19: JAZOON'13 - Martin Kropp - Agile Collaboration

|

How about Agile PM Tools?

• Used in combination with physical boards

• Always extra effort

• Think about benefit

• E.g. for accounting, needed persistency

• Master-Slave problem

• All variations applied

• Just make clear which way you go

Page 20: JAZOON'13 - Martin Kropp - Agile Collaboration

|

Digital Master

• Meetings with Beamer

• One “writer”

• Print out new US, tasks for physical board

• Print customized overviews

• Physical task board for detailed task planning

Page 21: JAZOON'13 - Martin Kropp - Agile Collaboration

|

Physical Master

• Team works with the physical board

• Changes are added to digital tools afterwards by one

person (mostly PO)

Page 22: JAZOON'13 - Martin Kropp - Agile Collaboration

Pros

• Persistence

• Historization

• Distributed

• Traceability

• Concurrent editing

Cons

• Lack flexibility

• Lack haptic experience

• Not suited for team work

• Lack visibility

• Lack instant availability

• Lack easy overview

Pro- and Cons of digital Agile PM Tools