Agile Development Practices at Sabre by Kiko Basilio at the Agile Executive Forum hosted by Orange and Bronze Software Labs. October 26, 2011

1. Agile Software Development
Kiko Basilio
Head of Web Development Group, Sabre
Confidential 1

2. Agile Software Development
Kiko Basilio
Confidential

3. Software Development Hurdles
Scope changes
Time to market
Changing Teams
Processes
Culture
Code Quality
Performance
Internal Politics
Confidential 3

4. What are you trying to fix improve?
Zone in on
the problem!
Confidential 4

5. Common Agile Flavors
Scrum XP Kanban
DSDM Crystal RUP
FDD Others
Confidential 5

6. There is NO silver bullet!
Confidential 6

7. It shouldn’t be all-or-nothing
Confidential 7

8. Anticipating yet being ready for changes
Confidential 8

9. Agile Planning View
Prioritized
Product Backlog
Release Planning Meeting
Release Plan
Sprint 1 Sprint 2 Sprint 3-7
Sprint backlog
Confidential 9

10. Revising the Plan
Revised Plan
Original Plan Using Team Velocity
Story A 5 ✓ Story A 5
Story B 3 ✓ Story B 3
• Each sprint provides new Story C 5
information and takes us closer ✓ Story C 5
to the product vision Story F 3 Story F 3
• Uncertainty remains, and the
Story D 5 Story D 5
shape of the cone is proportional Story E 5 Story E 5
Story G 3 Story G 3
Story I 3 Story I 3
Story H 5 Story H 5
Story J 2 Story J 2
Story K 5 Story K 5
Story L 3 Story L 3
Confidential 10

11. A good plan will look like this
• We will be done in Q1
• We will be done in February
• We will be done in February 18
Confidential 11

12. Sprint Execution
Sprint 1 Sprint 2 Sprint 3 Sprint 4
Demo u u u u
Retrospective u u u u
Planning u u u u
Mini Regression uu uu uu
Test
Refactor
Code
Daily Scrum Constant
Collaboration
Confidential 12

13. Release Burn Down / Burn Up
Confidential 13

14. Release Burn Down / Burn Up
Confidential 14

15. Cumulative Flow Diagram (Sprint)
Confidential 15

16. Kanban Boards (Sprint)
Confidential 16

17. What do you see?
Confidential 17

18. Kanban Board in Action
Confidential 18

19. Engineering Practices
• TDD (Test Driven Development)
• Unit Testing
• Refactoring
• Pair Programming
• Code Reviews
• Continuous Integration: Keeping it green
• Simple Design
• Collective Code Ownership
Confidential 19

20. Managing Technical Debt
Confidential 20

21. Tips (based on personal experience)
• Invest in good coaches
• Focus on the principle, not the practice
• Know your own corporate culture, avoid direct clashes
• Don’t bite off more than you can chew, pick the low hanging
fruits.
• Showcase your achievements but resist the temptation to impose
standards
Confidential 21

22. The blue and the red pill
Self Organizing
Teams
Continuous
Improvement
Take both pills, and watch your teams succeed!
Confidential 22