Distributed Scrum for Dutch Railways Jan Vermeir, Xebia

Transcription

1 Distributed Scrum for Dutch Railways Jan Vermeir, Xebia

2

3 Scrum promises effective and efficient software development

4 Yes, it actually works

5 I will show you how we implement distributed Scrum for our customer

6 Classic outsourcing of software development often fails to meet customer demands

7 Xebia's customer, ProRail, builds and maintains railway infrastructure in the Netherlands

8 ProRail is a respectable organisation with a long history and a strong focus on reliability

9 The Netherlands has 6500 km of railway, 6000 trains and 1.2 million travelers daily. 85% of the trains leaves on time.

10 A program was started to improve information for travelers

11 The programs aim was to improve timeliness and accuracy of information presented to travelers

12 PUB is part of the larger InfoPlus program. The PUBlication system displays and broadcasts information

13 The outsourcing strategy that was selected fosters conflict

14 CONFLICT!

15 Xebia introduces distributed Scrum to develiver quality software on time

16 Xebia introduces Scrum to build the PUBlication system

17 Scrum helps you and your customer focus and prioritize

18 But it's hard to influence a waterfall-based environment

19 Distributed Scrum increases team size while avoiding classical offshoring pitfalls

20 Scaling up to larger teams is difficult in the Netherlands 150

21 The cost of developers in India is lower, availability is higher 30

22 Joint development with Xebia India allows us to scale

23 Our customer was unfamiliar with both Agile development and offshoring. We were facing a list of challenges

24 We had to help our customer to adopt Scrum

25 It is very important to choose your product owner carefully

26 Waterfall driven requirements are no substitute for user stories

27 Testing was based on requirements while development was based on user stories

28 Requirements written in Dutch cannot be used in India

29 How do I implement distributed Scrum?

30 Effective communication is one of the key success factors

31 Skype, wiki, mailinglist and VNC allow distributed teams to interact at low cost but with high quality

32 One backlog allows teams to coordinate their work

33 One version control system ensures we never lose track of each others work

34 Team members visited the other location during the project

35 Team composition is very important as well

36 We started with a small co-located team of Dutch and Indian colleagues

37 We applied the cell concept to scale up

38 We don't suffer 'us' and 'them' feelings because teams are mixed across locations

39 11 star players do not make a great soccer team

40 'Quality without compromise' pays off, even during the project

41 'The maintainability of the system is very good' 'The quality of the source code is very high'

42 PUB shows consistently less errors than other parts of the program

43 The nightly quality build fails if code quality is too low, based on Findbugs and PMD. Developers use Checkstyle for Eclipse.

44 Unit test coverage is high. 80%

45 Quality software requires extensive testing

46 We use Fitnesse to test user scenario's

47 We take testing very seriously... Test Pages: 497 right, 10 wrong, 0 ignored, 0 exceptions Assertions: right, 54 wrong, 0 ignored, 11 exceptions

48 User interface testing is still manual, which hurts every two weeks when we deliver a new iteration

49 Set up a separate team to handle exceptions

50 Team Green handles whatever doesn't fit in regular iteration work

51 Performance and stability were tested on a regular basis

52 The customer required us to provide answers to several lengthy check lists

53 Documentation was written by a technical writer

54 Scrum in distributed teams allowed Xebia to deliver quality software on time within budget

55 Scrum User Group Portugal Resources PT Scrum events Scrum Mail Group Scrum Alliance Mitch Lacey