Tale of an off shore agile scrum implementation


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Tale of an off shore agile scrum implementation

  1. 1.   Joseph Vargheese CSM CSP
  2. 2.  Started with idea of extending onsite agile  Intention to reduce combined cost  Lot of surprises on the journey  New roles identified during the journey  Process extensions implemented.  At the end we are one happy family  And success continues….
  3. 3.  Identify a off-shore vendor with Scrum experience o Done  Selecting a team with agile knowledge o Done  SME came to Vendor location in India o Done  Team Training by SME o Done  KT session on client process o Done  KT session on client business and technology o Done
  4. 4.  Early Scrum Implementation Models o Joint Sprint Planning o Overlapping working hours o Daily combined status calls o Joint Sprint Review o Joint Sprint Retrospective o Joint KT sessions o Ad-hoc Instant messenger communication o Besides galore of emails....................  Result o Lot of issues o Off-shore team is not getting info they need on time o Onsite team is not getting the quality o Creativity and self organizing teams are far fetched
  5. 5.  Problems everywhere  For Off-shore to onsite team o No requirement clarification on time o No clear expectation setting from client  For Onsite Teams to off-shore team o Questions are not asked in time o Most of the story are dropped of sprint or rejected on review  Both sides are unhappy
  6. 6.  Heavy cultural conflict  Onsite team was not equipped to interact with off-shore team  Limited exposure of scrum process to off-shore team  Limited exposure to client functionality and thus questions came later  No Iteration zero or story pruning process  Beside phone line from off-shore has heavy noise…………………
  7. 7.  Solutions are everywhere…………..  Not sure which will be good and not time to experiment all  Off-shore team has given challenge to brainstorm and come up best idea(s) and they did  Here comes command and control o Some of the solution were not cost effective • Need more money (Oops…) • Reduce the delivery expectation (Oops………)
  8. 8.  Survival of the fittest (ideas) o Time will prove the worth  Change of process on onsite and offshore  Training on both ends (process and cultural)  More Open communication and feedback  Well defined resource on-boarding process  Efforts in Building trust on both ends
  9. 9.  Risk management  Ownership and accountability  Performance Metrics  Scrum of Scrums  Automated Continuous Integration  Quality o Test Automation o Review (Code, Test, Testing coverage) o Exploratory testing  Team came up checklist for different ceremonies  Some cases continuous delivery
  10. 10.  Onsite agile facilitator  Off-shore proxy product owner  Off-shore Scrum Lead
  11. 11.  Quality slowly started improving  Sprint review is seeing less and less gap  In-Sprint defects start reducing  Review rejection started reducing  Total defect outside of Sprint start reducing  Progress was slow, but steady
  12. 12.  Early Story Pruning, Iteration 0 (or Spikes)  Sprint planning split into three parts o Onsite Sprint Planning o Off-shore sprint planning without PO and SM o Off-shore sprint planning with PO and SM  Spike and key design decisions  Daily standup  Independent Sprint review and Retrospect.  Story ownership changes
  13. 13.  Quality o Production defects o Maintainability of code  Productivity o Velocity (Average story points)  Effectiveness of process  Earned Value  Predictability of the process  Number defects escaped to production/Story point  Employee satisfaction o Survey o One-on-One
  14. 14.  Dos o Evaluate the onsite team closely for off-shore team augmentation o Plan early and well defined KT o Build trust before productivity o Agile process training is very important for the team o Well defined resource selection process  Don’ts o Under estimating importance of cultural exchange o Running full sprints in beginning o Pointing errors to entire team
  15. 15.  Much better Off-shore scrum outputs  Periodic travel  Continuous training process o Process o Technology o Cultural  Reduced Resource attrition