Enterprise Scrum - Recife Summer School (English Version)

2,007 views

Published on

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

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,007
On SlideShare
0
From Embeds
0
Number of Embeds
135
Actions
Shares
0
Downloads
62
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Enterprise Scrum - Recife Summer School (English Version)

    1. 1. Enterprise Scrum Tips on what to do, and don't do, while adopting Scrum throughout the organization. Danilo Bardusco <bardusco@gmail.com>
    2. 2. History
    3. 3. 9 years ago... Globo.com was created, with the mission of be the Internet arm of Globo Organizations
    4. 4. 2000,March a team with just over 20 people, has bring to live the very first portal's version.
    5. 5. 2000,July ”Globo.com starring the biggest dot.com transaction in Latin America” Fonte: REUTERS
    6. 6. 2001,August Globo.com has hired me and Antonio Carlos Silveira to start the WebMedia division.
    7. 7. 2002,January Globo.com gets the 3° position on the brazilian online audience ranking.
    8. 8. 2006,June Hit a record of traffic generated by a single Internet portal in Brazil with the World Cup Soccer.
    9. 9. 400.000 subscribers
    10. 10. 15Gb/s Internet traffic
    11. 11. Leading: * News * Sports * Entertainment * Videos
    12. 12. 85 Millions of videos/month
    13. 13. but...
    14. 14. We can't delivery more than 1 big product per year.
    15. 15. We'd a long list of BUGs after releases.
    16. 16. A legacy code base, without tests, very hard to maintain.
    17. 17. so many failed projects
    18. 18. why?
    19. 19. 400+ employees
    20. 20. 15+ departments
    21. 21. 4 locations
    22. 22. to much beurocracy
    23. 24. 2007,May first Scrum pilot
    24. 25. Big Brother Brazil subscriptions
    25. 26. SUCCESS!
    26. 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.
    27. 28. 2008,January 4 multi-functional teams working with Scrum
    28. 29. Departments starting to loose power.
    29. 30. 100+ People trained by Boris Gloger
    30. 31. Scrum of Scrums SoS daily with Scrum Masters
    31. 32. Velocity++ Quality++
    32. 33. 7 dissolved departments
    33. 34. 16 Is the number of teams that make all Globo.com's product development.
    34. 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)
    35. 36. Hierarchy / Departments Organizational structure radically changed
    36. 37. Reward Reward model need to be changed
    37. 38. so?
    38. 39. stability?
    39. 40. why?
    40. 41. PUSH x PULL
    41. 42. Management way must change Trust
    42. 43. Kaizen Mind lack of a sense of urgency.
    43. 44. XP practices Agile engineering practices.
    44. 45. Meta-Scrum Portfolio management
    45. 46. Reuse 5 twitters like in less than one year.
    46. 47. New Platform <ul><li>Scalable
    47. 48. Distributed
    48. 49. Service Oriented Architecture
    49. 50. Easy to use
    50. 51. Fast to develop </li></ul>
    51. 52. Start 1 Team 12 Sprints
    52. 53. Making new teams
    53. 54. estimation?
    54. 55. Syncronizing <ul><li>All 6 teams started theirs Sprints together
    55. 56. Individual Sprint Plannings
    56. 57. Daily Meeting at 9:30h (each team)
    57. 58. Daily Scrum of Scrums at 9:50h
    58. 59. Collective Review at auditorium with everybody. </li></ul>
    59. 60. Colaboration tools <ul><li>Mailling list (no more emails)
    60. 61. IRC (no more IM)
    61. 62. GitHub
    62. 63. PasteBin
    63. 64. Live documentation on Wiki </li></ul>
    64. 65. 3 days of hands-on trainning
    65. 66. tips!
    66. 67. Do not parallelize - reduces the stock of unfinished products - help on self-management - regulate the team size - kick out of confort zone
    67. 68. In large scale, less is more - search for alternatives - Reuse solutions - Explore a lot of ideas
    68. 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
    69. 70. 2009,January We've got the top position in page views among the brazilian web portals. source: alexa.com
    70. 71. Thank you! It's possible to write quality software without beurocracy. Danilo Bardusco <bardusco@gmail.com> http://blog.bardusco.com

    ×