13
1 / 12 Lutz Prechelt, [email protected] Agile Offsharing: A software process idea Lutz Prechelt Freie Universität Berlin based on joint work with: Stephan Salinger, Julia Schenk, Franz Zieris, Holger Schmeisky, Christopher Oezbek, Laura Plonka, Danou Nauck, Karl Beecher, Edna Rosen, Björn Kahlert and ~50 Saros contributors ICSE 2014 "Ready – Set – Transfer" Contest Panel

How Agile Offsharing is ready for technology transfer

Embed Size (px)

DESCRIPTION

Agile Offsharing is an idea for improving knowledge transfer between sites in distributed software development.

Citation preview

Page 1: How Agile Offsharing is ready for technology transfer

1 / 12 Lutz Prechelt, [email protected]

Agile Offsharing:A software process idea

Lutz PrecheltFreie Universität Berlin

based on joint work with: Stephan Salinger, Julia Schenk, Franz Zieris, Holger Schmeisky, Christopher Oezbek, Laura Plonka, Danou Nauck, Karl Beecher, Edna Rosen, Björn Kahlert and ~50 Saros contributors

ICSE 2014 "Ready – Set – Transfer" Contest Panel

Page 2: How Agile Offsharing is ready for technology transfer

2 / 12

Our topics

1 Pair Programming (PP)

2 Saros, a distributed IDE Ingredients

3 Distributed Pair Programming (DPP)

4 Agile Offsharing idea to be transferred

Lutz Prechelt, [email protected]

Round 1

Round 2

Page 3: How Agile Offsharing is ready for technology transfer

3 / 12

Domain, Users &

Requirements

"Local"SW developers

Subsystem BSubsystem A

can understand

write write

communication by documents, visits, email, chat, phone, daily video standup, etc.

4 The Agile Offsharing idea

Lutz Prechelt, Freie Universität Berlin

Geographic & cultural distribution

"Remote"SW developers

Distributed Pair Programming

Joint system

*Works for othertypes of

knowledge asymmetry

as well

*

Page 4: How Agile Offsharing is ready for technology transfer

4 / 12

Agile Offsharing makes a radical step

Conventional approach:Minimize the need for

communication("Reduce coupling!")

Agile Offsharing approach:Actively increase the need for

communication("If it hurts, do it more often!")

Lutz Prechelt, [email protected]

Page 5: How Agile Offsharing is ready for technology transfer

5 / 12

Details

Agile Offsharing is not for everybody

Preconditions:

• Modest time zone difference

• Limited cultural difference• both national and

SW development culture

• Low-enough language barrier• for enough team members

• Volunteer team members

• Reliable, low-latency network connectivity

Steps for use:

• Setup & try out DPP tooling

• Find volunteers

• Select tasks & form pairs

• Do DPP

• Reflect on DPP sessions

Can only be worked outby technology transfer

Lutz Prechelt, [email protected]

Page 6: How Agile Offsharing is ready for technology transfer

6 / 12

Why is Agile Offsharing needed?

Lutz Prechelt, Freie Universität Berlin

We tend to under-estimate what needs explanation:

Page 7: How Agile Offsharing is ready for technology transfer

7 / 12

How is Agile Offsharingtransfer-ready?

1 Pair Programming (PP)

2 Saros, a distributed IDE Ingredients

3 Distributed Pair Programming (DPP)

4 Agile Offsharing trials

Lutz Prechelt, [email protected]

Page 8: How Agile Offsharing is ready for technology transfer

8 / 12

1 Knowledge about Pair Programming (PP)

• Research on conceptualizing the PP process since 2004• on real industrial sessions

• Goal: Find helpful behavioral patterns and antipatterns

• Results so far:• Base concepts

• Roles• e.g. Spokesperson, Watchman,

Guide/Robot, Task expert/Mentee

• Knowledge transfer mechanisms

• e.g. Clarification Cascade

Lutz Prechelt, [email protected]

time

Page 9: How Agile Offsharing is ready for technology transfer

9 / 12

2 The Saros DPP tool

• Distributed IDE• Plugin for Eclipse, soon also for IntelliJ IDEA• In development since 2006, Open Source• Industrial strength

• >1000 downloads per month

Lutz Prechelt, [email protected]

Page 10: How Agile Offsharing is ready for technology transfer

10 / 12

2 The Saros DPP tool

Page 11: How Agile Offsharing is ready for technology transfer

11 / 12

Knowledge about Distributed-Pair Programming (DPP)

• Research on conceptualizing the DPP process since 2010• builds on the PP research

• Goal 1: Find helpful behavioral patterns and antipatterns• Coping with

limited awareness• Making sensible use of

concurrent editing

• Goal 2: Validate usefulness

• Results so far:• Effortless awareness

bridging (Eclipse dialogs)• Prudent, limited use of

concurrent editing• DPP can be as efficient as

PP – or even slightly more

Lutz Prechelt, [email protected]

3

Page 12: How Agile Offsharing is ready for technology transfer

12 / 12

4 Agile Offsharing trials

• Just starting, with Lithuanian outsourcing provider NFQ• builds web applications

with long-term customers

• NFQ funds our full-time group member Holger Schmeisky• since 2014-04

• Also: In discussion with 2 large multinationals• we expect to start trials at

one of them later this year

Lutz Prechelt, [email protected]

Corporation D

Corporation S

Page 13: How Agile Offsharing is ready for technology transfer

13 / 12 Lutz Prechelt, [email protected]

Thank you!