0
Research ongloballydistributed software engineering<br />			Rini  van Solingen<br />
Who am I?<br />Rini van Solingen, 38 years old, married to Patricia, 2 kids (Bo en Bas), lives in Zoetermeer, The Netherla...
Scrum Management Book	January 2011 (expected)<br />The Power of Scrum<br />An inspiring story about a revolutionary projec...
The Delft Software Engineering Research Group (http://www.se.ewi.tudelft.nl/)<br />Group size:<br />~25 fte, including ~15...
5<br />
Adding a global perspective to SE<br />Source: Carmel & Agarwal, IEEE Software 2001<br />6<br />
Four Types of Distance<br />Geographical (Kilometers, or door-to-door travel time)<br />Temporal (Timezone-distance, or % ...
On Culture….<br />Geert Hofstede (www.geert-hofstede.com)<br />Power Distance Index (PDI) <br />Individualism (IDV)<br />M...
Allen Curve – 30 meter principle<br />Source: TJ Allen, The Organization and Architecture of Innovation, 2007<br />9<br />
The Research Challenge for GDSE<br />Our Quest for GDSE research:<br />“Creating the virtual 30 meters”<br />Deep understa...
Although: the Virtual 30-meters….<br />11<br />
Although: the Virtual 30-meters….<br />12<br />
…for Software Engineers<br />My tasks<br />Source code<br />Product features<br />Task status<br />13<br />
…Virtual 30-meters: Traceability<br />Requirements<br />Source code related to task<br />Task status<br />Test cases relat...
The TU-Delft GDSE Research Agenda<br />Successfully deploying GDSE in practice<br />Best-practices of companies, success-f...
Best-practicesforDistributed Scrum<br />16<br />
Best-practice 0:<br />If Single Roof is Possible: Do It!<br />Don’t distributed if not necessary<br />17<br />
Best-practice 1:<br />First deploy Scrum locally before working distributed<br />Deploy “by the book”: inspect and adapt e...
Best-practice 2:<br />Assign Scrum roles explicitly, define proxies and ensure alignment between these<br />PO-role even m...
Best-practice 3:<br />One team in one rhythm<br />Team members are located on all locations and work in same sprints<br />...
Best-practice 4:<br />Meet<br />Teams are not build up by themselves: actively establish personal relations<br />21<br />
Best-practice 5:<br />Impediment resolution and Retrospective effectiveness remains crucial<br />Meet for retrospectives<b...
Best-practice 6:<br />Work at customer location at least between 10-20% of the time<br />23<br />
Best-practice 7:<br />Personal mindset is crucial:<br />“what did I do wrong?”<br />“what can I do different?”<br />“what ...
Best-practice 8:<br />Don’t focus on tools: discussion and interaction is more important<br />25<br />
Best-practice 9:<br />Communication & Awareness is no Automatism<br />On this issue tools do help<br />26<br />
Best-practice 10:<br />Fail fast: improve empirically<br />Both successes andfailures are sources for learning<br />27<br />
The TU-Delft GDSE Research Agenda<br />Successfully deploying GDSE in practice<br />Best-practices of companies, success-f...
Example 1: Technological Support for distributed agile<br />July 13, 2010<br />29<br />
Example 2: experiment FtS development<br />July 13, 2010<br />30<br />
Example 3: Routing for FtS<br />Http://www.follow-the-sun.org<br />31<br />
Example 4: GDSE Game<br />Running GDSE company<br />Deciding Lab locations<br />Defining Strategy<br />Customer focus<br /...
The TU-Delft GDSE Research Agenda<br />Successfully deploying GDSE in practice<br />Technological support for distributed ...
Thank you for allowing me to talk about my passion!Questions?<br />D.M.vanSolingen@tudelft.nl<br />R.vanSolingen@prowarene...
Upcoming SlideShare
Loading in...5
×

Distributed Agile by Rini van Solingen

1,428

Published 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. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,428
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Distributed Agile by Rini van Solingen"

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

    Clipping is a handy way to collect important slides you want to go back to later.

×