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.

Klaus Olsen - Agile Test Management Using Scrum

1,457 views

Published on

EuroSTAR Software Testing Conference 2008 presentation on Agile Test Management Using Scrum by Klaus Olsen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/

Published in: Software
  • Be the first to comment

  • Be the first to like this

Klaus Olsen - Agile Test Management Using Scrum

  1. 1. Agile Test Management Using SCRUM Presented by Klaus OlsenPresented by Klaus Olsen EuroSTAR conference 2008 The Hague, Netherlands
  2. 2. ©Softwaretest.dk&KlausOlsen2008. Agenda IntroductionIntroduction ScrumScrum Test ManagementTest Management Agile EstimationAgile Estimation
  3. 3. ©Softwaretest.dk&KlausOlsen2008. Klaus Olsen, biography  Founder and owner of the company Softwaretest.dk  Has used the past 16 years to focus on software testing, test process improvements and teaching  Author of “Softwaretest – how to get started” in Danish  Certified ScrumMaster  Trustee in TMMi Foundation  Member of ISTQB Board, representing Denmark  Co-author of ISTQB Foundation and Advanced Syllabus  Other presentations:  EuroSTAR´98 in Münich  Second World Congres on Software Quality 2000 in Yokohama, Japan  EuroSTAR´2001 in Stockholm  Quality Week 2001 in San Francisco, USA  EuroSTAR´2003 in Amsterdam.  ASTA 2007 in Seoul, South-Korea  Contact Klaus by mail klaus@softwaretest.dk
  4. 4. ©Softwaretest.dk&KlausOlsen2008. Introduction  This is a combined case study form my work with a client and an introduction to Scrum as a Test Management method.  The client was a large international phone company.  The project was a billing system for all mobile services offered by the company.  The test team consisted of between 8 to 10 people in a period of 12 months.  The billing system was a third party product enhanced/customized by a consultant company.  The task of the team was planning and execution of an acceptance test.
  5. 5. ©Softwaretest.dk&KlausOlsen2008. 3+1 key points of this presentation 1. You will see how you can create a Product Backlog where all the work you need to get done within your test team should be listed. 2. You will learn why Daily Meetings of 15 minutes are more valuable to you and your team than a once a week status meeting. 3. You will learn how to create a Burndown Chart of remaining work within each iteration. +1 And if we have time, you will learn how to use an Agile Estimation technique.
  6. 6. ©Softwaretest.dk&KlausOlsen2008. Agenda IntroductionIntroduction ScrumScrum Test ManagementTest Management Agile EstimationAgile Estimation
  7. 7. ©Softwaretest.dk&KlausOlsen2008. A part of a rugby game when players from both sides link themselves together in a group, with their heads down, and push against the other side. The ball is then thrown between them and each side tries to get it. Just before this, each team has agreed their tactics to be used in the next play. Scrum Metaphor
  8. 8. ©Softwaretest.dk&KlausOlsen2008. Product Backlog 24-hour Inspection Increment of product backlog Read more about Scrum on www.controlchaos.com Scrum Skeleton Iteration
  9. 9. ©Softwaretest.dk&KlausOlsen2008. Scrum 3 Roles 3 Meetings 3 Artifacts
  10. 10. ©Softwaretest.dk&KlausOlsen2008. Scrum Roles Product Owner ScrumMaster Team
  11. 11. ©Softwaretest.dk&KlausOlsen2008. Product Owner  One person  Sets development schedule by prioritizing backlog  Responsible for ensuring that the most important business value is developed first  Represents all stakeholders
  12. 12. ©Softwaretest.dk&KlausOlsen2008. ScrumMaster  Test (Project) Manager  Coach  Responsible for the process  Responsible for maximizing team productivity  Sets up meetings  Conducts meetings  Representative to management  Representative to team
  13. 13. ©Softwaretest.dk&KlausOlsen2008. Team  Self-organizing  Seven +/- 2 members  Best experts available  Has the business and technical domain skills to test an increment of functionality  Responsible for committing to work  Authority to do whatever is needed to meet commitment
  14. 14. ©Softwaretest.dk&KlausOlsen2008. Scrum Team Self Organization  Team decides who will do what  As more is known, team continues to adjust work and assignments  Team self-organizes at beginning of Sprint  Each team member self-organizes himself or herself every day  Team self-organized itself every Daily Scrum
  15. 15. ©Softwaretest.dk&KlausOlsen2008. Scrum 3 Roles 3 Meetings 3 Artifacts
  16. 16. ©Softwaretest.dk&KlausOlsen2008. Scrum Meetings Sprint Planning Workshop Daily Scrum Sprint Review Meeting
  17. 17. ©Softwaretest.dk&KlausOlsen2008. Product Backlog Daily Scrum Increment of product backlog Scrum Meetings Sprint Iteration Sprint Planning Workshop Sprint Review Meeting
  18. 18. ©Softwaretest.dk&KlausOlsen2008. Sprint Planning Meeting  1st . - 4 hours meeting max. for team to select Product Backlog and sets goal with Product Owner  Team selects as much Product Backlog as it believes it can handle during the next Sprint  2nd . - 4 hours meeting max. for team to define Sprint Backlog to agree functionality to be tested  Anyone can attend, but primary conversation and work is between team and Product Owner
  19. 19. ©Softwaretest.dk&KlausOlsen2008. Daily Scrum  Daily 15 minutes status meeting  Same place and time every day  Three questions: 1. What have you done since last meeting? 2. What will you do before the next meeting? 3. What is in your way?  Impediments  Decisions
  20. 20. ©Softwaretest.dk&KlausOlsen2008. Daily Scrum  First meeting take more time as team learns how to Scrum  Keep meetings crisp  Use “Stand Up Meetings”  Focus on answering the three questions  Let each person have 2 minutes to answer  Don´t allow discussions regarding what has been reported  Setup meetings following the Daily Scrum as needed
  21. 21. ©Softwaretest.dk&KlausOlsen2008. Scrum 3 Roles 3 Meetings 3 Artifacts
  22. 22. ©Softwaretest.dk&KlausOlsen2008. Scrum Artifacts Product Backlog Sprint Backlog Burndown Chart
  23. 23. ©Softwaretest.dk&KlausOlsen2008. Product Backlog: Everything included within testing, prioritized and estimated SCRUM 30 days Sprint Backlog: Tasks selected for a Sprint Tasks selected by each member Scrum: 15 minute daily meeting. Team members respond to: 1) What did you do since last Scrum Meeting? 2) Do you have any obstacles? 3) What will you do before next meeting? 24 hours Functionality ready to ship at end of Sprint Read more on www.controlchaos.com
  24. 24. ©Softwaretest.dk&KlausOlsen2008. Product Backlog  List of task that needs to be done  Issues are placeholders that are later defined as work  More detail on higher priority backlog  One list for multiple teams  Product owner responsible for priority  Anyone can contribute  Maintained and posted visibly
  25. 25. ©Softwaretest.dk&KlausOlsen2008. Product Backlog Example ID Description Estimate Priority 1 Define roles and responsibility within project 2 Define Test Levels in project 3 Define Goals for each Test Level in project 4 Write Test Plan for project 5 Review Requirement documentation 6 Structure System Test into Test Areas 7 Create and document test cases 8 Define requirement for test environment 9 Define requirement for test data 10 Investigate how test data can be created 11 Execute test 12 Create defect reports
  26. 26. ©Softwaretest.dk&KlausOlsen2008. Scrum Artifacts Product Backlog Sprint Backlog Burndown Chart
  27. 27. ©Softwaretest.dk&KlausOlsen2008. Sprint Backlog  List of highest priority task from Product Backlog  Tasks are estimated in hours, usually 1-16  Task with more than 16 hours are broken down later  Team members sign up for tasks, they aren´t assigned (be patient, just wait)  Estimate work remaining is updated daily  If work is unclear, define a Sprint Backlog with a larger amount of time … break it down later  Update work remaining as more is known, as items are worked
  28. 28. ©Softwaretest.dk&KlausOlsen2008. Sprint Backlog Example ID Description Estimate Priority 1 Define roles and responsibility within project 1 2 Define Test Levels in project 2 3 Define Goals for each Test Level in project 3 8 Define requirement for test environment 4 9 Define requirement for test data 5 4 Write Test Plan for project 6 5 Review Requirement documentation 7 6 Structure System Test into Test Areas 8 10 Investigate how test data can be created 9  The Sprint Backlog is an extract of the Product Backlog with estimated work for 30 calendar days / 22 workdays for a team 7 +/- 2
  29. 29. ©Softwaretest.dk&KlausOlsen2008. Sprint  The Scrum Team has decided what it will accomplish during the upcoming Scrum. It now Sprints to accomplish the Sprint Goal.  A Sprint is conducted in a vacuum, totally protected from outside noise and interference. This allows the team to get their collective minds around a problem and creatively solve it. 30 days Sprint Backlog: Tasks selected for a Sprint Tasks selected by each member
  30. 30. ©Softwaretest.dk&KlausOlsen2008. Scrum Artifacts Product Backlog Sprint Backlog Burndown Chart
  31. 31. ©Softwaretest.dk&KlausOlsen2008. Burndown Chart  Work remaining on each task is reported during the Daily Scrum meeting, and updated by the ScrumMaster  Notice that this is different than measuring how many hours have been spent on a task  Time reporting is not part of Scrum  Scrum is results oriented, not effort driven
  32. 32. ©Softwaretest.dk&KlausOlsen2008. Burndown Chart Example Burndown Chart Example
  33. 33. ©Softwaretest.dk&KlausOlsen2008. Agenda IntroductionIntroduction ScrumScrum Test ManagementTest Management Agile EstimationAgile Estimation
  34. 34. ©Softwaretest.dk&KlausOlsen2008. Test Management using Scrum  Use the parts of Scrum that are feasible in your organisation  Many parts are common sense, but through Scrum the have been put together, and they have proven to work  If not all, I suggest you use:  Product Backlog  Sprint Backlog  Agile Estimating  Daily Scrum meetings  Burndown Chart
  35. 35. ©Softwaretest.dk&KlausOlsen2008. Benefits of Daily Scrum Meetings  As a test manager, once every 24 hours you will know the status of your teams test progress.  Your team members will feel they are moving things forward, they will have a small success everyday when they are able to report their progress since the last meeting.  During the daily 15 minutes you will be able to measure the temperature of your team.  You will be able to notice team members who need support/coaching within a few days, instead of weeks. Instead of once a week status meeting of 1 or 1½ hour
  36. 36. ©Softwaretest.dk&KlausOlsen2008. Scrum – How to get started 1. Create a Product Backlog 2. Estimate each task the Agile way, with your team 3. Prioritize each task, together with you Product Owner, or together with your test team 4. Create a Sprint Backlog with work for an iteration of 30 calendar days 5. Start with a Daily Scrum meeting, and let each team member set there own goal for the next 24 hours 6. Update your Burndown Chart each day with remaining work
  37. 37. ©Softwaretest.dk&KlausOlsen2008. Agenda IntroductionIntroduction ScrumScrum Test ManagementTest Management Agile EstimationAgile Estimation
  38. 38. ©Softwaretest.dk&KlausOlsen2008. What is an Estimate  The most common view, an estimate is a number  An estimate is a prediction about the future which has an equal probability of being above or below the actually result  An estimate always has a level of uncertainty. Estimates should always be accompanied with an explanation of uncertainty.
  39. 39. ©Softwaretest.dk&KlausOlsen2008. Agile Estimation An Agile way to estimate is a technique with cards: 1. Each team member select sa set of cards (13) 2. Decide if estimate is in hours or days 3. The facilitator reads the task to be estimated 4. The task is discussed 5. Each person selects a card with a value they believe the task needs in order to be completed 6. All cards are turned over and put on the table with value facing up 7. If agreement on estimate this is the estimate 8. If values are diverse the person with the highest and lowest value explains the reason for their estimates 9. Repeat process from step 5 until agreement in step 7
  40. 40. ©Softwaretest.dk&KlausOlsen2008. Agile Estimation using Cards  Using the ”Fibonacci numbers” - each number is the sum of the two preceding numbers
  41. 41. ©Softwaretest.dk&KlausOlsen2008. Agile Estimation Example I  People with estimate of 5 and 55 hours explains the reason why they have the estimate they have  4 people / Scrum team members estimates a task, and Cards are turned over with value facing up
  42. 42. ©Softwaretest.dk&KlausOlsen2008. Agile Estimation Example II  People with estimate of 8 and 34 hours explains the reason why they have the estimate they have  A new game of estimating is played
  43. 43. ©Softwaretest.dk&KlausOlsen2008.  Consensus on Estimate, 21 hours is used as an estimate for this task Agile Estimation Example III  Once more a new game of estimating is played
  44. 44. ©Softwaretest.dk&KlausOlsen2008. More information - Links  www.controlchaos.com  www.scrumalliance.org  www.agilealliance.org  www.softwaretest.dk Ken Schwaber ISBN: 0-13-067634-9 ISBN: 0-7356-1993-x

×