About Me
Certified Scrum Master
16 + Years in IT industry in which 8 Years in Agile
Specialized in
 Distributed Agile ...
Need for a Distributed Agile

Stakeholders are distributed
Skilled people are spread across
Round the clock support
Cost S...
Distributed Agile Team Patterns

Product Owner in One location
Team in different location
4
Distributed Agile Team Patterns

Multiple Vendor

in a Single Agile team

5
Distributed Agile Team Patterns

Multiple Cross functional teams
from different location
6
Distributed Agile Team Patterns

Single cross functional team in
Multiple Location
7
Distributed Agile Challenges
Communication
Issues

Time zone difference

Lack of Co-ordination

Cultural difference

Trans...
Best Practices

Decide on the Pattern and
Customize the framework

Integrated

Distributed

9
Best Practices

Implement it in Stages
1

Start with Co-Located team

Partially Distributed

2

Fully Distributed

3

10
Best Practices

Conduct Combined Planning
and develop Shared Vision
Utilize Overlap hours

Consider only good clarity User...
Best Practices

Continuous Backlog Grooming
and Story Estimation
In a scheduled interval entire team should collaborate an...
Best Practices

Look Ahead Planning to handle Dependency
Try to group
the dependent
user stories
and give it to
one team

...
Best Practices

It is not the Distance
but Time zone difference is a challenge
Overlap working
Hours

Introduce Additional...
Best Practices

Implement Community of Practice

15
Best Practices

Change the way you communicate
•Move towards synchronous media
phones instead of emails)

(messenger &

•M...
Best Practices

Conduct Scrum Of Scrum
Portfolio
Level

Program
Level

Team Level

17
Best Practices

Introduce Additional Meetings
Daily Catch-up meeting

Communities of Practice

Frequent Estimation meeting...
Best Practices

Develop ”One team” Mindset
Acknowledge cultural differences

Strengthen Functional Sub culture

Celebrate ...
Best Practices

Introduce Agile Engineering Practices

Continuous
Integration and Build

TDD/ ATDD/BDD

Test Automation/
B...
Best Practices

Invest on Travel
Bring everyone in one
location for
Release Planning
Team Rotation

Frequent travel by PO
...
Addressing SCRUM Ceremonies…
Daily Standup

In a Room/ Face to Face

Virtual Standup using “net
meeting”

Planning

One fu...
Finally…

Co Located

Or

Distributed

is immaterial

But

how we bring
Agile values are Important
23
ATC2013-Umadevi- Distributed Agile Challenges
ATC2013-Umadevi- Distributed Agile Challenges
ATC2013-Umadevi- Distributed Agile Challenges
Upcoming SlideShare
Loading in...5
×

ATC2013-Umadevi- Distributed Agile Challenges

438

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

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

No notes for slide

ATC2013-Umadevi- Distributed Agile Challenges

  1. 1. About Me Certified Scrum Master 16 + Years in IT industry in which 8 Years in Agile Specialized in  Distributed Agile Implementation  Large Scale Agile Transformation  Agile Training  SAFe implementation  Agile Assessment
  2. 2. Need for a Distributed Agile Stakeholders are distributed Skilled people are spread across Round the clock support Cost Savings 3
  3. 3. Distributed Agile Team Patterns Product Owner in One location Team in different location 4
  4. 4. Distributed Agile Team Patterns Multiple Vendor in a Single Agile team 5
  5. 5. Distributed Agile Team Patterns Multiple Cross functional teams from different location 6
  6. 6. Distributed Agile Team Patterns Single cross functional team in Multiple Location 7
  7. 7. Distributed Agile Challenges Communication Issues Time zone difference Lack of Co-ordination Cultural difference Transparency Building Trust 8
  8. 8. Best Practices Decide on the Pattern and Customize the framework Integrated Distributed 9
  9. 9. Best Practices Implement it in Stages 1 Start with Co-Located team Partially Distributed 2 Fully Distributed 3 10
  10. 10. Best Practices Conduct Combined Planning and develop Shared Vision Utilize Overlap hours Consider only good clarity User stories Prioritize and share the stories well in advance to all members Use visual tools for Planning meeting 11
  11. 11. Best Practices Continuous Backlog Grooming and Story Estimation In a scheduled interval entire team should collaborate and understand user stories & estimate frequently Architectural Changes identified and Prioritized by Architect well in advance Involve entire team for Estimation 12
  12. 12. Best Practices Look Ahead Planning to handle Dependency Try to group the dependent user stories and give it to one team Make sure all dependent team participate for the planning meeting Use feature team instead of Component team 13
  13. 13. Best Practices It is not the Distance but Time zone difference is a challenge Overlap working Hours Introduce Additional Roles Continuous Backlog grooming Iteration Planning done in 2 days 14
  14. 14. Best Practices Implement Community of Practice 15
  15. 15. Best Practices Change the way you communicate •Move towards synchronous media phones instead of emails) (messenger & •Move towards shared ie visible-to-all media (Yammer instead of emails) •Move towards collaborative systems (Wiki, SharePoint instead of individual documents) •Reduced documentation 16
  16. 16. Best Practices Conduct Scrum Of Scrum Portfolio Level Program Level Team Level 17
  17. 17. Best Practices Introduce Additional Meetings Daily Catch-up meeting Communities of Practice Frequent Estimation meetings Pre planning meeting Problem Solving meeting 18
  18. 18. Best Practices Develop ”One team” Mindset Acknowledge cultural differences Strengthen Functional Sub culture Celebrate Festivals, Birthdays etc Encourage informal communication Specialized team building exercises & games Cross cultural training 19
  19. 19. Best Practices Introduce Agile Engineering Practices Continuous Integration and Build TDD/ ATDD/BDD Test Automation/ Build Automation 20
  20. 20. Best Practices Invest on Travel Bring everyone in one location for Release Planning Team Rotation Frequent travel by PO 21
  21. 21. Addressing SCRUM Ceremonies… Daily Standup In a Room/ Face to Face Virtual Standup using “net meeting” Planning One full day planning meeting (8 Hours) 2 Day planning meeting Estimation Using Poker Cards Weekly Ones or Twice with entire team using VC or online tool Backlog Grooming No need for frequent grooming Multiple grooming sessions Demo Demo during regular hours Demo during overlap hours including all team members Retrospect In a meeting room During overlap hours using VC and online tool like “Group map” Story boarding Using Physical Board Using “Visual Story Board” User Story Can be written in a simple Card ALM tool is a must 22
  22. 22. Finally… Co Located Or Distributed is immaterial But how we bring Agile values are Important 23

×