From RUP to Scrum in an Internet company - UOL

2,202 views
2,182 views

Published on

This was my presentation in Scrum Gathering in Stockolm, Orlando and Sao Paulo. Actually my great partner Andres Schliep made the most part of the work.

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

No Downloads
Views
Total views
2,202
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
170
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • We develop internet products such as webmail, authentication systems, biding systems, sponsored links applications. These applications must suport some hundreds of requests per second. We use mainly Java and Linux.
  • In July of 2007 we ‘ve noticed it was time to look for something different than RUP. We had trouble with the project customers, we were not increasing the deliveries as long as we are increasing investments. So we’ve decided to try agile processes. We chose Scrum because it looked more prepared to deal with business people. Besides Yahoo and Google were using it, at least partially. And this was very important to us.
  • I’ve decided to show to the upper management what it could be improved after some time studying scrum. I took care to say to them that scrum was not a silver bullet. Besides I told them if scrum did not work, we would have to continue using RUP. Any process is better than nothing.
  • The first row is more likely rup projects. The second one is more lilkely agile projects.
    That was the picture that was more successful during the presentation. Business people said : OW!! I got it. That’s the thing we need. The president and CEO accepted.
  • The first row is more likely rup projects. The second one is more lilkely agile projects.
    That was the picture that was more successful during the presentation. Business people said : OW!! I got it. That’s the thing we need. The president and CEO accepted.
  • We decided to contract a consultancy, after the upper management accepted the idea of change. Experience is very important to change a big ship journey. The ship is already sailing. You need to take care of the ongoing operations and projects.
    We’ve discussed the proposal with Sprint-IT and it seemed that they were the right guys. Then we’ve picked up 3 projects to start. Each one having a differente type. Besides we’ve chosen between already deployed produtcts and new ones too. These choices made us to face different problems at the same time.
  • Of course, you can’t forget reading books. They were very important to me to justify the framwework the way it is, without being a ruler. You know, people start to refuse and ask changes in scrum after some time. It was very good to me knowing the basics and say why not to change the framework.
    I started talking with focused groups presenting scrum and discussing the problems that the scrum change would bring to them.
  • We decided to contract a consultancy, after the upper management accepted the idea of change. Experience is very important to change a big ship journey. The ship is already sailing. You need to take care of the ongoing operations and projects.
    We’ve discussed the proposal with Sprint-IT and it seemed that they were the right guys. Then we’ve picked up 3 projects to start. Each one having a differente type. Besides we’ve chosen between already deployed produtcts and new ones too. These choices made us to face different problems at the same time.
  • We decided to contract a consultancy, after the upper management accepted the idea of change. Experience is very important to change a big ship journey. The ship is already sailing. You need to take care of the ongoing operations and projects.
    We’ve discussed the proposal with Sprint-IT and it seemed that they were the right guys. Then we’ve picked up 3 projects to start. Each one having a differente type. Besides we’ve chosen between already deployed produtcts and new ones too. These choices made us to face different problems at the same time.
  • Of course, you can’t forget reading books. They were very important to me to justify the framwework the way it is, without being a ruler. You know, people start to refuse and ask changes in scrum after some time. It was very good to me knowing the basics and say why not to change the framework.
    I started talking with focused groups presenting scrum and discussing the problems that the scrum change would bring to them.
  • Besides scrum master training, we organized scrum introduction with different roles inside each group. Andreas will explain this more detailed.
  • From RUP to Scrum in an Internet company - UOL

    1. 1. UOL Transition of development teams from RUP to Scrum May, 2009
    2. 2. UOL – www.uol.com.br • Brazilian portal created in 1996 – news, e-commerce, Internet access, e-mail and advertising • UOL is the largest portal written in Portuguese • The most visited portal in Latin America • About 300 IT people creating and operating Internet products
    3. 3. What is UOL? • 1.7 million of subscribers • 7 million of active mailboxes • 1.7 billion of page views • 67% reach of Brazilian Internet • About 30 scrum teams
    4. 4. Why should we change from RUP to something else? • Do the business departments have a good relationship with you? • How much energy is wasted discussing requirements change instead of producing value? • Can you see the products being delivered easier as long as company invests more money to do them?
    5. 5. Why Scrum? • I didn’t believe firstly • Mike Cohn session – SDWest • Book • Qcon nov/07 – Scrum master Training
    6. 6. How the upper management was convinced to use scrum? • Giving examples in the same kind of business – Yahoo!, Google • Explaining the reasons why Scrum is considered business driven – Functional development – Short iterations – Product backlog prioritization
    7. 7. How the upper management was convinced to use scrum? • Showing good pictures • Thks to gojko.net for the picture
    8. 8. How the upper management was convinced to use scrum? Work Demo release Roadmap Planning Tasks Work Inspection Retro 2 weeks
    9. 9. How the upper management was convinced to use scrum?
    10. 10. How the upper management was convinced to use scrum?
    11. 11. How Scrum was implemented? • Introduce people from other areas – Operation – Database – QA – Functional Manager – Financial, HR and Law
    12. 12. How Scrum was implemented? • Start deep discussions with different groups separately before start – Operations – Developers – QA – Eligible scrum masters – Functional managers
    13. 13. How Scrum was implemented? • Selection of consultancy – choose people that want to discuss real problems • SPRiNT iT (Andreas Schliep)
    14. 14. How Scrum was implemented? • One of each project type in your company – UOL has 3 types • Choose between new systems and existing systems – Existing systems revealed more problems at UOL
    15. 15. Know how to explain Read
    16. 16. How Scrum was implemented? • Introductory training 1 day - 21 people – Different skills and roles • Eligible ScrumMasters • Business People • Developers • Webmasters • QA • Database Administrators and Developers • Operations
    17. 17. Scrum Team Training
    18. 18. Session with QA • QA part of team • User stories • Acceptance Tests • Automation • Agile test plan
    19. 19. How Scrum was implemented? • Start as soon as possible – Prioritized Backlog (at least themes) – Vision – It’s not possible to resolve all the problems before starting – sometimes people don’t know they have problems • Scrum will demand improvements naturally – Better user stories – More efficiency in testing and delivering
    20. 20. Sprint Planning todaOferta
    21. 21. How Scrum was implemented? • Weekly meetings with upper management (ETC) • Scrum master group • List of common impediments • Scrum master of scrum masters
    22. 22. Coaching Goals • Better communication • Focused development • Frequent value generation • Increased transparency • Productivity improvement
    23. 23. Proposed Activities • Train all team members in Scrum basics • Work with the teams to create agile project plans • Coach the respective teams • Provide Certified ScrumMaster training
    24. 24. Schedule Phase I -March Phase II - April Phase III - May
    25. 25. Phase I - Results • Started PagSeguro, Atenas, todaOferta • Prepared RadioUOL, UOLHost • Discussed QA, usability and database development issues • Initiated ScrumMaster group • Performed 2 team trainings
    26. 26. Phase I - Impediments • Backlog creation and prioritization • Missing automated acceptance tests • ITIL protocols slow down deployment
    27. 27. Phase I - Impediments • People not 100% dedicated to team • Missing Company Backlog • Required ScrumMaster training • Collaborative work space setup
    28. 28. Time for Deployment
    29. 29. Phase II - Results • Started RadioUOL, Babel, PagSeguro • Prepared 5 others • Continued ScrumMaster group • Performed 2 team trainings • Scrum master training
    30. 30. Sprint Planning RadioUOL
    31. 31. Daily Scrum todaOferta
    32. 32. Phase II - Impediments • Team not ready to start • Meeting room availability • Quality of backlog items • Controlling of Scrum projects unclear • Performance appraisals
    33. 33. Phase III - Results • 2 Scrum for Executives sessions • 1 Agile Quality Management session • Continued ScrumMaster group • Prepared other project
    34. 34. Phase III - Results • Started 3 others • Refined running teams • 2 Scrum Team Trainings
    35. 35. Daily Scrums
    36. 36. Sprint Retrospective uolMais
    37. 37. Sprint Planning uolMais
    38. 38. Scrum Team Training
    39. 39. Task Board Babel • Evolution of practice • Vertical arrangement • Different colours for different types • Team calendar • Sprint Burndown
    40. 40. Changes and Results • 29 teams using scrum • Dedicated people to each team – most of times – Decrease of functional management – Keep the functional managers mentoring and defining standards • Better communication/relationship with business departments • ITIL Change Management Optimization – About 30 changes/week • Release Planning and Reporting • 2 or 3-week sprints
    41. 41. Advices Get empowerment to change
    42. 42. Advices Understand the whole product environment
    43. 43. Advices Don’t accept excuses • No scrumbut • Empathy yes, complacence no • Know How to convince people
    44. 44. Advices Keeping improving • SMG (one hour/week) • Agile engineering • Let everybody know that we can do it better
    45. 45. Advices Announce Rules and Container (Mike Cohn) • best practices • don’t confuse them with micro management
    46. 46. Advices Watch and protect the change • Anonymous poll • Ask the team, scrum masters and product owners – dont’t let the bad networking coming up • Start fast, but few environments (teams +contexts) • dodge already promised dates
    47. 47. Thanks • Gabrielle Benefield • Andreas Schliep • Yahoo! people • UOL board of directors • UOL – courageous people
    48. 48. Muito obrigado! Alexandre dos Santos, (alexst@uol.com.br) Andreas Schliep, (andreas.schliep@googlemail.com)

    ×