Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Harnessing Agile Development In Distributed Environment Dusan K Part

2,649 views

Published on

Harnessing the Power of Agile Development in a Distributed Environment

Part II

Webminar by SD Times, Dave West (Forrester) and Dusan Kocurek.

This presentation covers second part.

Published in: Business, Technology

Harnessing Agile Development In Distributed Environment Dusan K Part

  1. 1. Dusan Kocurek Software Lab Manager, Ness Software Product Labs<br />Part I by co-presenter Dave West not includedSenior Analyst, Forrester Research<br />Harnessing the Power of Agile Development in a Distributed EnvironmentPart II<br />1<br />
  2. 2. Most software development is done by distributed teams today<br />Why distributed development? Cost savings, availability, skills<br />2<br />Challenges<br />
  3. 3. 3<br />A Mix Of Agile And…<br />Reality? <br />Mix of methodologies<br />Adaptation <br />is key to success<br />
  4. 4. Why non-Agile<br />Customer is conservative<br />“Waterfall is good, proven, management style”<br />High risk project – no will and courage to implement Agile<br />Customer’s clients want non-Agile PM<br />Why Agile<br />Current methods aren’t working – late releases, over-budget, team burnout<br />Agile is a proven method<br />Agile encourages team communication<br />Customer is late adopter, but willing to consider if Agile can help<br />4<br />Reasons for more methodologies<br />
  5. 5. 5<br />Offshore and AdaptationClient not using Agile method<br />Adapt<br /><ul><li> Planning
  6. 6. Tracking
  7. 7. Delivery
  8. 8. Communication
  9. 9. Tools</li></ul>Offshore team<br />Customer’s<br />team<br />
  10. 10. 6<br />Offshore and AdaptationClient not using Agile method<br />Scrum<br />Adapt<br /><ul><li> Planning
  11. 11. Tracking
  12. 12. Delivery
  13. 13. Communication
  14. 14. Tools</li></ul>Many times Agile<br />leads to change<br />Offshore team<br />Customer’s<br />team<br />
  15. 15. Offshore and AdaptationClientusing Agile method<br />Adapt<br /><ul><li> Ceremonies
  16. 16. Scrum Style
  17. 17. Roles
  18. 18. Communication
  19. 19. Tools</li></ul>Hyper-productive<br />teams<br />Offshore team<br />Customer’s<br />team<br />7<br />
  20. 20. 8<br />“What are the challenges of geographically distributed development?”<br />Team’s<br />Communication<br />Tools<br />
  21. 21. Scrum of Scrum<br />Integrated Scrum<br />9<br />Styles – Isolated SCRUM<br />Coding<br />QA<br />Design<br />
  22. 22. 10<br />Styles –SCRUM of SCRUM<br />D+C+QA<br />D+C+QA<br />D+C+QA<br />
  23. 23. 11<br />Styles –Integrated SCRUM<br />Team B: D+C+Q<br />Team A: D+C+Q<br />Team C: D+C+Q<br />
  24. 24. Ness Technologies, UK client<br /><ul><li>3 locations (United Kingdom, Czech Republic, Slovak Republic)
  25. 25. One Product Owner based in UK
  26. 26. 2 ScrumMasters in UK and Slovakia
  27. 27. Teams are distributed
  28. 28. Developers at every location
  29. 29. QA in UK, Slovakia </li></ul>12<br />Scrum of Scrum style<br />
  30. 30. SprintForce company<br /><ul><li> 5 locations (Denmark, Romania, Ukraine, Uganda, Philippines)
  31. 31. One Product Owner per product
  32. 32. 3 ScrumMasters located at the same office in Romania
  33. 33. Teams are multi-disciplined and multi-located
  34. 34. Technical experts in different countries help teams to deliver </li></ul>www.sprintforce.com<br />13<br />Integrated Scrum style <br />
  35. 35. Roles and structure<br />Cross functional teams<br />ScrumMasters at all locations<br />Scrum of Scrum<br />Product owners<br />14<br />Teams<br />
  36. 36. Face to face<br />When?<br />Where?<br />15<br />Communication<br />
  37. 37. Meet online<br />IM, Email, Webcam<br />Common project space<br />When<br />Daily<br />At a regular time<br />16<br />Communication [Stay tuned]<br />
  38. 38. Time zones<br />Find core time<br />Representatives<br />17<br />Time Zones<br />
  39. 39. Agile and tools?<br />Physical board is the best!<br />I’m using Excel! <br />Is all that enough?<br />18<br />Tools<br />
  40. 40. 19<br />Radiators<br />
  41. 41. 20<br />Virtual Task Boards<br />
  42. 42. 21<br />PM<br />Microsoft Excel<br />Microsoft Project<br />VersionOne<br />ScrumDesk<br />GreenHopper<br />Bug trackers<br />BugZilla<br />Jira<br />Mantis<br />Mercury Quality Center<br />Document and collaboration<br />Microsoft SharePoint<br />Wiki<br />Mind map utilities<br />Screen sharing<br />Online meeting tools<br />Version control systems<br />CSV<br />Subversion<br />Visual Source Safe<br />Development support<br />Cruise Control<br />Team Central<br />Other tools<br />
  43. 43. 22<br />Focus on…<br />
  44. 44. Communication is a must<br />Visibility for everyone<br />Time zones could be advantage<br />23<br />Summary<br />
  45. 45. Q+A<br />24<br />Question and Answer Session<br />
  46. 46. Thank you for attending today’s webinar. Both speakers can be reached via email so that you can follow up with additional questions. Here is their contact information:<br />Dusan KocurekSoftware Lab Manager, Ness Software Product Labs<br />dusan.kocurek@ness.com<br />25<br />Thank you for attending!<br />

×