Distributed Agile by Rini van Solingen
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Distributed Agile by Rini van Solingen

  • 1,790 views
Uploaded on

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI.......

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,790
On Slideshare
1,790
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
29
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Research ongloballydistributed software engineering
    Rini van Solingen
  • 2. Who am I?
    Rini van Solingen, 38 years old, married to Patricia, 2 kids (Bo en Bas), lives in Zoetermeer, The Netherlands
    Technical informatics – TU-Delft (MSc)Technology Management – TU-Eindhoven (PhD)
    Head in the clouds, feet in the dirt (industry-science)
    Schlumberger, Fraunhofer IESE, CMG/Logica, Mavim, iSenseProwareness, TUDelft, TUEindhoven, Stenden University
    Loves to lead, investigate, teach, publish and coach
    20% TU-Delft, 80% iSenseProwareness
    July 13, 2010
    2
  • 3. Scrum Management Book January 2011 (expected)
    The Power of Scrum
    An inspiring story about a revolutionary project management approach
    Authors:
    Jeff Sutherland
    Rini van Solingen
    Eelco Rustenburg
    July 13, 2010
    3
  • 4. The Delft Software Engineering Research Group (http://www.se.ewi.tudelft.nl/)
    Group size:
    ~25 fte, including ~15 full time researchers (PhD candidates, postdocs).
    Teaching:
    Programming and project skills of Delft computer science students
    ~20 MSc projects p/y in software engineering
    Research:
    Software evolution
    Reverse engineering
    Software testing
    Services
    Model-driven engineering
    Web engineering
    Embedded systems
    Globally distributed SE
    Close collaboration with industry
    4
  • 5. 5
  • 6. Adding a global perspective to SE
    Source: Carmel & Agarwal, IEEE Software 2001
    6
  • 7. Four Types of Distance
    Geographical (Kilometers, or door-to-door travel time)
    Temporal (Timezone-distance, or % overlapping hours)
    Language (Language distance, native vs. non-native)
    Cultural (Cultural distance e.g. Hofstede dimensions)
    July 13, 2010
    7
  • 8. On Culture….
    Geert Hofstede (www.geert-hofstede.com)
    Power Distance Index (PDI)
    Individualism (IDV)
    Masculinity (MAS)
    Uncertainty Avoidance Index (UAI)
    Long-Term Orientation (LTO)
    8
  • 9. Allen Curve – 30 meter principle
    Source: TJ Allen, The Organization and Architecture of Innovation, 2007
    9
  • 10. The Research Challenge for GDSE
    Our Quest for GDSE research:
    “Creating the virtual 30 meters”
    Deep understanding of GDSE issues
    Both theoretical and practical
    Real versus perceived distance
    Technological solutions are available and still sufficient additions feasible and required
    The virtual project space as “dot-on-the-horizon”
    10
  • 11. Although: the Virtual 30-meters….
    11
  • 12. Although: the Virtual 30-meters….
    12
  • 13. …for Software Engineers
    My tasks
    Source code
    Product features
    Task status
    13
  • 14. …Virtual 30-meters: Traceability
    Requirements
    Source code related to task
    Task status
    Test cases related to requirements
    14
  • 15. The TU-Delft GDSE Research Agenda
    Successfully deploying GDSE in practice
    Best-practices of companies, success-factors and fail-factors from practice are an important focus in my research
    Technological support for distributed sw-development
    Technology to support a decreased perception of distance and increased transparency
    Distributed agile development
    Agile methods increase the level of informal communication, coordination and control; Agile might solve many issues in distributed development
    Follow-the-Sun software development
    The GDSE ‘stress-test’; if tools and technology work for FtS, they are likely to be applicable elsewhere too
    Teaching GDSE dynamics
    Prepare our current student population for a career in which GDSE plays a role
    July 13, 2010
    15
    15
  • 16. Best-practicesforDistributed Scrum
    16
  • 17. Best-practice 0:
    If Single Roof is Possible: Do It!
    Don’t distributed if not necessary
    17
  • 18. Best-practice 1:
    First deploy Scrum locally before working distributed
    Deploy “by the book”: inspect and adapt empirically
    18
  • 19. Best-practice 2:
    Assign Scrum roles explicitly, define proxies and ensure alignment between these
    PO-role even more critical and crucial
    19
  • 20. Best-practice 3:
    One team in one rhythm
    Team members are located on all locations and work in same sprints
    20
  • 21. Best-practice 4:
    Meet
    Teams are not build up by themselves: actively establish personal relations
    21
  • 22. Best-practice 5:
    Impediment resolution and Retrospective effectiveness remains crucial
    Meet for retrospectives
    22
  • 23. Best-practice 6:
    Work at customer location at least between 10-20% of the time
    23
  • 24. Best-practice 7:
    Personal mindset is crucial:
    “what did I do wrong?”
    “what can I do different?”
    “what can I do to help?”
    24
  • 25. Best-practice 8:
    Don’t focus on tools: discussion and interaction is more important
    25
  • 26. Best-practice 9:
    Communication & Awareness is no Automatism
    On this issue tools do help
    26
  • 27. Best-practice 10:
    Fail fast: improve empirically
    Both successes andfailures are sources for learning
    27
  • 28. The TU-Delft GDSE Research Agenda
    Successfully deploying GDSE in practice
    Best-practices of companies, success-factors and fail-factors from practice are an important focus in my research
    Technological support for distributed sw-development
    Technology to support a decreased perception of distance and increased transparency
    Distributed agile development
    Agile methods increase the level of informal communication, coordination and control; Agile might solve many issues in distributed development
    Follow-the-Sun software development
    The GDSE ‘stress-test’; if tools and technology work for FtS, they are likely to be applicable elsewhere too
    Teaching GDSE dynamics
    Prepare our current student population for a career in which GDSE plays a role
    July 13, 2010
    28
    28
  • 29. Example 1: Technological Support for distributed agile
    July 13, 2010
    29
  • 30. Example 2: experiment FtS development
    July 13, 2010
    30
  • 31. Example 3: Routing for FtS
    Http://www.follow-the-sun.org
    31
  • 32. Example 4: GDSE Game
    Running GDSE company
    Deciding Lab locations
    Defining Strategy
    Customer focus
    Projects vs Products
    Advance decision making
    Teaching GDSE dynamics
    32
  • 33. The TU-Delft GDSE Research Agenda
    Successfully deploying GDSE in practice
    Technological support for distributed sw-development
    Distributed agile development
    Follow-the-Sun software development
    Teaching GDSE dynamics
    July 13, 2010
    33
    33
  • 34. Thank you for allowing me to talk about my passion!Questions?
    D.M.vanSolingen@tudelft.nl
    R.vanSolingen@prowareness.nl
    www.rinivansolingen.nl
    34