Tips on what to do, and don't do, while adopting Scrum throughout the organization. more at: http://blog.bardusco.com/

1. Enterprise Scrum Tips on what to do, and don't do, while adopting Scrum throughout the organization. Danilo Bardusco <bardusco@gmail.com>

2. History

3. 9 years ago... Globo.com was created, with the mission of be the Internet arm of Globo Organizations

4. 2000,March a team with just over 20 people, has bring to live the very first portal's version.

5. 2000,July ”Globo.com starring the biggest dot.com transaction in Latin America” Fonte: REUTERS

6. 2001,August Globo.com has hired me and Antonio Carlos Silveira to start the WebMedia division.

7. 2002,January Globo.com gets the 3° position on the brazilian online audience ranking.

8. 2006,June Hit a record of traffic generated by a single Internet portal in Brazil with the World Cup Soccer.

9. 400.000 subscribers

10. 15Gb/s Internet traffic

11. Leading: * News * Sports * Entertainment * Videos

12. 85 Millions of videos/month

13. but...

14. We can't delivery more than 1 big product per year.

15. We'd a long list of BUGs after releases.

16. A legacy code base, without tests, very hard to maintain.

17. so many failed projects

18. why?

19. 400+ employees

20. 15+ departments

21. 4 locations

22. to much beurocracy

24. 2007,May first Scrum pilot

25. Big Brother Brazil subscriptions

26. SUCCESS!

27. Oddities Main requirement was never delivered Despite that the client was very happy!(scope negotiation) Noise and Post-Its on the walls drew the attention of the entire company. Board requested a presentation to know what is this scrum is about.

28. 2008,January 4 multi-functional teams working with Scrum

29. Departments starting to loose power.

30. 100+ People trained by Boris Gloger

31. Scrum of Scrums SoS daily with Scrum Masters

32. Velocity++ Quality++

33. 7 dissolved departments

34. 16 Is the number of teams that make all Globo.com's product development.

35. Communities's Scrum of Scrums Agile Process Product portfolio, corporate backlog Web Design Standards Web Standards Information Architecture Testing tools, test automation, etc, Scrum of Scrums (developers)

36. Hierarchy / Departments Organizational structure radically changed

37. Reward Reward model need to be changed

38. so?

39. stability?

40. why?

41. PUSH x PULL

42. Management way must change Trust

43. Kaizen Mind lack of a sense of urgency.

44. XP practices Agile engineering practices.

45. Meta-Scrum Portfolio management

46. Reuse 5 twitters like in less than one year.

48. Distributed

49. Service Oriented Architecture

50. Easy to use

51. Fast to develop

52. Start 1 Team 12 Sprints

53. Making new teams

54. estimation?

56. Individual Sprint Plannings

57. Daily Meeting at 9:30h (each team)

58. Daily Scrum of Scrums at 9:50h

59. Collective Review at auditorium with everybody.

61. IRC (no more IM)

62. GitHub

63. PasteBin

64. Live documentation on Wiki

65. 3 days of hands-on trainning

66. tips!

67. Do not parallelize - reduces the stock of unfinished products - help on self-management - regulate the team size - kick out of confort zone

68. In large scale, less is more - search for alternatives - Reuse solutions - Explore a lot of ideas

69. Be a Lazy Boy 1. just do what is absolutely necessary to achieve the GOAL 2. don't reinvent the wheel 3. simplify 4. automate

70. 2009,January We've got the top position in page views among the brazilian web portals. source: alexa.com

71. Thank you! It's possible to write quality software without beurocracy. Danilo Bardusco <bardusco@gmail.com> http://blog.bardusco.com