This document discusses how to implement Scrum methodology for geographically distributed teams. It provides an overview of Scrum, including how the presenter's organization started using it in 2009. Their teams are organized by feature and divided among locations. They emphasize daily stand-ups, 2 day sprint tasks, retrospectives, and testing. The goal is to build trust through clear communications and constant process improvements.

1. Scrum for BOND.
How do we do this in a
geographically distributed
teams.
Dennis Popov
depo@berlingskemedia.dk
14 Mar. 2011

2. Gold Sponsor of
DrupalCamp Kyiv 2011

3. Silver Sponsors of
DrupalCamp Kyiv 2011

4. Agenda
• Where we are
• SCRUM What is it ?
• How did it start with us ?
• How our teams are organized ?
• How do we do this?
• Where should we aim at?
• Bonus: Kanban

5. Where we are
• From 1 to 35 within 12 months
• 3 Drupal teams 2 mobile teams 1 magento
• Procedures and processes
• B.DK, BT.DK, AOK.DK, sporten.dk
• Main dev power

6. SCRUM. What is it?
This is not a shortened
SCRUM course but... i will
tell you
• What is is SCRUM
about
• How do we use it
• Share our best
practices and tweaks

7. SCRUM. What is it?
• A methodology for software
project development
• Lets you focus on most important
business values
• Business sets the priorities. Self
organized team decides on the
best technical way.
• Each sprint all parties interested
can see real functioning product
so to decide either to release it or
continue improvements in the
next sprint

8. SCRUM. What is it?
• Define teams
• Divide products by features
• Define business value
• Do a release plan
• Constantly optimize your
process

9. SCRUM. What is it?

10. How did it start ?
• 2009 big company, dear colleagues
• 2010 path of transformation and savings
• 2010 Ukraine as the best combination for
price, quality, sales

11. How did it start ?
• Right thinking. Like - minded persons
• Right procedures. Adjustments
• Right people. Interview, July 2010 first sprint

12. How our teams are organized

13. How our teams are organized

14. How do we do this
• Releases
• Estimations
• Planning
• Retrospectives

15. How do we do this
• Daily scrum, sharp schedule
• Overtimes are illegal
• One task not more than 2 days (16 hours)
• Importance instead of priority (importance can be
500 instead of priority 1)
• Pool (15% of sprint time) for urgent issues
• If you are sick you are in the sprints as a task!
• One task one team member 1:1
• Pare programming and discussions, workshops
• New features and areas are documented
• Same rules for everybody

16. How do we do this
with testing
• Tester tries to reproduce issue before
estimation session starts

17. How do we do this
with retrospectives
• Retrospective for distributed team

18. Where to aim
• Trust. That's nearly everything
• Sense of Urgency
• Good communications
• Process understanding
• Think out of the box
what else can i do ?
• One change a a time
• Constant improvements

19. What next ?
• What can i improve
for the company i am working in?
• What out of that will i do first?
• When will i do it ?

20. Thank you for your
attention!
questions ?
Dennis Popov
depo@berlingskemedia.dk
denys.popov@gmail.com
skype: celenia_dep

21. Read, try, feel
Peopleware
Management 3.0
Agile Project Management with Scrum
Agile Software Development with Scrum
Kanban и Scrum: getting best of both (Ru)
SCRUM games
mikogo, planning poker online
version one
Kniberg's blog
http://www.controlchaos.com/
http://scrumalliance.org/
Scrum Cheat sheet

22. Bonus: Kanban in 3 min.
Scrum board but with - workflow visualized and
• WIP limits
• Buffers
• Throughput speed