Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introducing Scrum into Ibelis


Published on

Presentation by Alex Rosales made on June 11, 2011 at FPT-Greenwich
University in Hanoi, Vietnam

Published in: Sports, Technology
  • Be the first to comment

Introducing Scrum into Ibelis

  1. 1. Scrum - How we did it? Alex Rosales Chief Technology Officer
  2. 2. HEY, I’VE GOT NEWS!• We are “EVOLVING”, today you will learn SCRUM
  3. 3. “OK”, “We are listening…”
  4. 4. Mmm, Motivation…• Be Real and Honest• Have Faith, Trust and Respect• Remember, Team = People and Individuals• Remember, Team = All of Equal Value
  5. 5. HEY, I’VE GOT NEWS again!
  6. 6. Team Motivation• Set Realistic Goals• Provide the Tools• Sense of Purpose• Involve, Communicate, Smile
  7. 7. Motivation Matters, PERIOD!
  8. 8. Scrum Framework Day Training • Why Scrum Vs. what we were using? • Trust Vs. Controlling • Our Team: High Performance Individuals • Spirit of willingness • Able to do it
  9. 9. Setting up the EnvironmentCollaborative Team Effort
  10. 10. Use of Task BoardVirtual or Physical? Virtual Physical • Learning curve • Increase Visibility • Remove • Increase Communication Communication • Could get Expensive • Inexpensive • Boring • Exciting • Isolates People • Reconnects People
  11. 11. Our ChoiceSimple and Effective 40,000 VND Beautiful Task Board
  12. 12. Defining Scrum Roles
  13. 13. Choosing the First Project• Meaningful but not critical• Keep communication open• Work is FUN philosophy• Hybrid Model a +++ (i.e. Physical TB + TFS/JIRA,...)
  14. 14. First Project: Mini-SprintDuration: 4 Days (ASK ME WHY?)
  15. 15. Mini-Sprint• Keep it Simple, Exciting and Interactive• Promote Communication• Embrace Positive Thinking• Have Always Candy
  16. 16. Real Practice – Mini-Sprint
  17. 17. The Results I• First Ask Me if we finish the Sprint• The Estimation Wall• Daily Stand-up Meeting – Hiding lessons?• Once the Sprint starts, “Nothing Else Matters”
  18. 18. The Results II Done = 100% Done Did we forget about the meaning of Done?
  19. 19. Our First Lesson• Bug Fixing - Allocate Time per Sprint• Plan for the Unexpected ALWAYS• The Team Should be Cross-Functional “Do not confuse Specialty with Cross- Functional”
  20. 20. Scrum RetrospectiveAka Beer Retrospective
  21. 21. What Worked Well?
  22. 22. Sprint Retrospective• Short Daily Stand-Ups• In-and-Out Pair Programming• Team Commitment• We Did It!
  23. 23. What didn’t work well?
  24. 24. Sprint Retrospective• Poor Estimations• Poor Testing• Clear Understanding of DONE• The Unexpected
  25. 25. What should we start doing?
  26. 26. Sprint Retrospective• Individual QA/QC Before Done• Review Done Tasks Sooner• REMEMBER Update Task Status• Q & A and Suggestions Board
  27. 27. Ok Folks, I am DONE