Fully Distributed Scrum - Need Right People & Best Practices

3,949 views
3,852 views

Published on

Fully Distributed Scrum - Need Right People & Best Practices

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

No Downloads
Views
Total views
3,949
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Fully Distributed Scrum - Need Right People & Best Practices

  1. 1. <ul><li>Fully Distributed Scrum: </li></ul><ul><li>N eed right people & best practices </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  2. 2. JAIBEER MALIK <ul><li>2004 B.Tech from IIT KGP </li></ul><ul><li>Total 5 years of IT Experience in software development </li></ul><ul><li>Former Employers: Sapient, Globallogic </li></ul><ul><li>Currently working as Senior Consultant with Xebia </li></ul><ul><li>Certified Scrum Master </li></ul><ul><li>Experienced in: Java, J2ee, Unix, Flex, Distributed Agile. </li></ul><ul><li>Thumb rule: Delivering Quality solution to all software problems </li></ul><ul><li>Hobbies: Swimming, Basketball, Volleyball, Cricket...Sports </li></ul><ul><li>Web: http://jaibeermalik.wordpress.com </li></ul><ul><li>Profile: http://www.linkedin.com/in/jaibeermalik </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  3. 3. Agenda <ul><li>Fully Distributed Scrum </li></ul><ul><li>Why right people? </li></ul><ul><li>Sprint in Action: Typical vs Distributed team </li></ul><ul><li>Distributed teams with overlapping time period (e.g. India & Europe) </li></ul><ul><li>Distributed teams with no overlapping time period (e.g. India & USA) </li></ul><ul><li>Conclusion (Do it right way!) & WARNING!!! (Fail early than be sorry!) </li></ul><ul><li>Questions </li></ul><ul><li>Feedback </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  4. 4. Distributed Scrum Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  5. 5. Fully Distributed Scrum <ul><li>World apart teams </li></ul><ul><li>Separated by timezone, culture </li></ul><ul><li>& language etc. </li></ul><ul><li>Brought together by the same set </li></ul><ul><li>of standards & principles </li></ul><ul><li>Still working as single team </li></ul><ul><li>Still following Scrum </li></ul><ul><li>Adopt as it suits best to the teams </li></ul><ul><li>on both the sides </li></ul><ul><li>Working together for the success!!! </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  6. 6. Why right people? <ul><li>Right people are ready to overcome </li></ul><ul><ul><li>Timezone, Cultural & Language issues </li></ul></ul><ul><ul><li>Process problems </li></ul></ul><ul><ul><li>Technical problems </li></ul></ul><ul><ul><li>Management problems </li></ul></ul><ul><ul><li>other similar impediments </li></ul></ul><ul><li>Right people are not afraid of </li></ul><ul><ul><li>Change </li></ul></ul><ul><ul><li>Failure </li></ul></ul><ul><ul><li>Visibility </li></ul></ul><ul><li>Right people make it happen </li></ul><ul><li>Agile teams: look for right people, not only experts </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  7. 7. Best Practices? <ul><li>That works well for the team on both the sides </li></ul><ul><li>Getting evolve over time </li></ul><ul><li>Same things not necessarily to work for another team </li></ul><ul><li>Adoption as per the requirements is the best approach </li></ul><ul><li>Decisions taken as a team </li></ul><ul><li>Keeping the team spirit up </li></ul><ul><li>Talk more, communicate more </li></ul><ul><li>Work towards builidng trust </li></ul><ul><li>Single goal to work towards the success </li></ul><ul><li>Communication backbone of distributed teams!!! </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  8. 8. Sprint in Action <ul><li>Scrum Meetings </li></ul><ul><ul><li>Sprint Planning </li></ul></ul><ul><ul><li>Daily standup </li></ul></ul><ul><ul><li>Sprint Restrospective </li></ul></ul><ul><ul><li>Sprint Review </li></ul></ul><ul><li>Collcated Teams </li></ul><ul><ul><li>Communication and collaboration with-in team easier </li></ul></ul><ul><ul><li>Executing typical sprint is easier comparatively </li></ul></ul><ul><li>Distributed Teams </li></ul><ul><ul><li>Teams with some overlapping time period </li></ul></ul><ul><ul><li>Teams with no overlapping time period </li></ul></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  9. 9. Some Overlapping Period (eg. IN & Europe) <ul><li>Good part is some overlapping period is there </li></ul><ul><li>Whole team can coomunicate to team on other side </li></ul><ul><li>Chances of mis-communication are less </li></ul><ul><li>Minimize waste in escalation and follow ups </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  10. 10. Overlapping Period: Sprint Planning <ul><li>Adopt the right approach which suits best to teams on both sides </li></ul><ul><li>First part of Planning Meeting </li></ul><ul><ul><li>Onsite/both team finishes the planning meeting with client </li></ul></ul><ul><li>Second part of Planning (Estimations) Meeting </li></ul><ul><ul><li>Part one : To get started for one team on next day </li></ul></ul><ul><ul><li>Part two: Finish the whole estimations meeting </li></ul></ul><ul><li>Knowledge Transfer </li></ul><ul><ul><li>On-site team having more insights </li></ul></ul><ul><li>Team Composition/Scaling </li></ul><ul><ul><li>Divide the team in vertical slices </li></ul></ul><ul><ul><li>All the teams on both sides working on all functionalities </li></ul></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  11. 11. Team Compostion & Scaling Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  12. 12. Overlapping Period: Daily Stand up <ul><li>Local stand up </li></ul><ul><li>Distributed stand up </li></ul><ul><li>Status mails </li></ul><ul><li>Query or impediment </li></ul><ul><li>resolution </li></ul><ul><li>Separate offline discussions </li></ul><ul><li>Separate design discussions </li></ul><ul><li>Live cams </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  13. 13. Overlapping Period: Sprint Retrospective <ul><li>Do it regularly, don't miss </li></ul><ul><li>Get everyone involved </li></ul><ul><li>Try different flavours </li></ul><ul><ul><li>Good points, deltas and action items </li></ul></ul><ul><ul><li>Template based </li></ul></ul><ul><ul><li>Free flow discussion </li></ul></ul><ul><li>Share MOM with team all the times, use wiki </li></ul><ul><li>Voting system </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  14. 14. Overlapping Period: Sprint Review <ul><li>Try to engage both sides </li></ul><ul><li>Prefer video conferencing </li></ul><ul><li>Share demo updates </li></ul><ul><li>Share demo feedback with whole team </li></ul><ul><li>Dropping mail with demo update or demo gadget is a good idea </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  15. 15. No Overlapping Period (eg. IN & USA) <ul><li>Biggest challenge is no overlapping period, Share the pain </li></ul><ul><li>Usually single person of contact, chances of mis-communication more </li></ul><ul><li>Less communication between team members, comparatively </li></ul><ul><li>Need to take pro-active approach to minimize waste </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  16. 16. No Overlapping Period: Sprint Planning <ul><li>First part of planning meeting </li></ul><ul><ul><li>Team plan user stories for next sprint in the current sprint only </li></ul></ul><ul><li>Second part of planning meeting </li></ul><ul><ul><li>Both teams together do the estimations meeting </li></ul></ul><ul><li>Task Break up </li></ul><ul><ul><li>Reduce dependency of taks between both sides </li></ul></ul><ul><li>Integration/Regression tests </li></ul><ul><ul><li>Tests plays much more important role here </li></ul></ul><ul><li>Code Freeze/Branching </li></ul><ul><ul><li>Plan properly and save time wastage between sprints </li></ul></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  17. 17. No Overlapping Period: Daily Standup <ul><li>Local stand up </li></ul><ul><li>Distributed stand up </li></ul><ul><li>Full team meeting </li></ul><ul><li>Status update, use mails or wiki </li></ul><ul><li>Offline discussions, use mails or wiki </li></ul><ul><li>Design discussions, use mails or wiki </li></ul><ul><li>Build breaks </li></ul><ul><li>Knowledge sharing, use wiki </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  18. 18. No Overlapping Period: Sprint Retrospective <ul><li>Fundamentals are same </li></ul><ul><ul><li>Do it regularly, don't miss </li></ul></ul><ul><ul><li>Get everyone involved </li></ul></ul><ul><ul><li>Try different flavors </li></ul></ul><ul><ul><li>Share MOM </li></ul></ul><ul><ul><li>Voting System </li></ul></ul><ul><li>Biggest challenge to discuss is commonly to overcome the communication gaps </li></ul><ul><li>Depends on team how to solve it the best way </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  19. 19. No Overlapping Period: Sprint Review <ul><li>Usually not possible for both teams to be present </li></ul><ul><li>Try to indulge both sides, if possible </li></ul><ul><li>Share the demo feedback </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  20. 20. Conclusion <ul><li>Easy and continuous access to resources </li></ul><ul><ul><li>Source code repository </li></ul></ul><ul><ul><li>Continuous integration server </li></ul></ul><ul><ul><li>Bug tracking tool </li></ul></ul><ul><ul><li>Wiki </li></ul></ul><ul><ul><li>Project Management tool </li></ul></ul><ul><li>Setup infrastructure to supprt team members communication </li></ul><ul><ul><li>Sprint meetings </li></ul></ul><ul><ul><li>Offline discussions </li></ul></ul><ul><ul><li>Knowledge sharing sessions </li></ul></ul><ul><li>Regular movement of people for short duration </li></ul><ul><ul><li>Mixing of people to overcome cultural issues etc. </li></ul></ul><ul><ul><li>One team feeling </li></ul></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  21. 21. WARNING!!! <ul><li>You don't need special skills to fail a project irrespective of location and process </li></ul><ul><li>Keep the above points as the backbone of the distributed agile development </li></ul><ul><li>Lack of communication will raise many more questions, in case missed or ignored </li></ul><ul><li>Keeping the single team feeling is also another big challenge </li></ul><ul><li>The best part is that it is up to the team to decide how to fix these problems and how to make it work </li></ul><ul><li>Have right people and follow best practices, SUCCESS IS YOURS!!! </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  22. 22. ? Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com
  23. 23. Feedback!!! <ul><li>[email_address] </li></ul><ul><li>[email_address] </li></ul><ul><li>Follow me @ </li></ul><ul><li>http://twitter.com/jaibeermalik </li></ul><ul><li>http://friendfeed.com/jaibeermalik </li></ul>Jaibeer Malik Fully Distributed Scrum: Sprint in Action http://jaibeermalik.wordpress.com

×