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.

Lessons learned from scaling Agile to distributed, offshore teams

5,911 views

Published on

Published in: Technology
  • If you are looking for trusted essay writing service I highly recommend ⇒⇒⇒WRITE-MY-PAPER.net ⇐⇐⇐ The service I received was great. I got an A on my final paper which really helped my grade. Knowing that I can count on them in the future has really helped relieve the stress, anxiety and workload. I recommend everyone to give them a try. You'll be glad you did.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • There is a useful site for you that will help you to write a perfect and valuable essay and so on. Check out, please ⇒ www.HelpWriting.net ⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I like this service ⇒ www.HelpWriting.net ⇐ from Academic Writers. I don't have enough time write it by myself.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating for everyone is here: ❤❤❤ http://bit.ly/2u6xbL5 ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Follow the link, new dating source: ❶❶❶ http://bit.ly/2u6xbL5 ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Lessons learned from scaling Agile to distributed, offshore teams

  1. Distributed AgileLessons Learned Working with Offshore Teams
  2. About Stephane• Consultant for banks, insurances, European institutions & SMEs• Java Architect (16+) & Agile Practionner (7+)• Co-founder of Arexo Consulting stephane.rondal@arexo.be @stephanerondal
  3. • Context• Problems• Solutions• Q&A
  4. The Project Confidential
  5. Architecture Confidential
  6. Geographical Dispersion
  7. Differences: Language & Religion
  8. Differences: Time
  9. Management’s Fear
  10. Problems
  11. Bad Comprehension of Requirements
  12. Slipping Planning
  13. Teams Blaming Each Other
  14. Overall Low Quality
  15. Dissatisfaction of Management
  16. Build Respect In
  17. Send Ambassadors Out
  18. Alignment
  19. Align Iteration Boundaries
  20. Iteration Plan is a Contract Agreed upon by developers
  21. Align Estimation Techniques
  22. Multi-disciplined Teams
  23. No Server Team/GUI Team
  24. Smart Slicing of Work
  25. Being eXtreme
  26. How to Improve Communication
  27. Communicating Requirements & Vision
  28. Scrum of Scrums
  29. But sometimes you just need to adapt
  30. RUP Use Cases
  31. UC-SC-xx – LoginDescription Basic FlowThe user shall • The user requests to openauthenticate himself in a console (supervision,order to be able to use the configuration,system. administration) • The SC requests the userActors to provide his usernameUser (initiator) and his password.Supervision Console (SC) • …Flow of EventsThis use case beginswhen…
  32. Wireframes
  33. Relentless Push
  34. Relentless Push
  35. Review Code Often
  36. Integrate Often
  37. Invaluable Tools
  38. It’s All About• Smoothing (cultural) differences• Reducing inter-team dependencies• Increasing cross-team awareness / syntony
  39. Conclusion It’s just common sensebut common sense is not that common

×