1. w w w. n e s s. c o m Introduction to SCRUM

2. w w w. n e s s. c o m “The problem we face has nothing to do with process and technology, but with people. Scrum and Agile are based on the hypothesis that there is no meta-solution for software development. Just a framework within which we will be empirical – inspect and adapt. This is very frustrating to those looking for procedures and final answers.” - Ken Schwaber

3. w w w. n e s s. c o m Agile Manifesto A Statement of Values Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Source : www.agilemanifesto.org

4. w w w. n e s s. c o m Iterative development

5. w w w. n e s s. c o m SCRUM A play in Rugby in which the two sets of forwards mass together around the ball and, with their heads down, struggle to gain possession of the ball.

6. w w w. n e s s. c o m Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. SCRUM in 100 Words

7. w w w. n e s s. c o m History The approach first described by Takeuchi and Nonaka in "The New Product Development Game" (Harvard Business Review, Jan-Feb 1986). “The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach— where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.” Wicked Problems, Righteous Solutions by DeGrace and Stahl, 1990. First mention of Scrum in a software context

8. w w w. n e s s. c o m Evolution Jeff Sutherland Initial Scrums at Easel Corp in 1993 IDX and nearly 600 people doing Scrum Not just for trivial projects FDA-approved, life-critical software for x-rays and MRIs Ken Schwaber ADM Initial definitions of Scrum at OOPSLA 96 with Sutherland Mike Beedle Scrum patterns in PLOPD4

9. w w w. n e s s. c o m New product class No proven models Incremental model with rapid feedback a necessity Hyper-productive development environment Development far out-paced planning and testing Solution: Apply an empirical process Apply lean value chain analysis methods to optimize test and planning functions Create cross-functional team to optimize communication and collaboration The First Scrum

10. w w w. n e s s. c o m What is Scrum used for? US FDA-approved software for X-Rays, MRIs High availability systems (99.9999% uptime) Enterprise workflow systems Financial payment applications Large database applications Embedded systems ISO 9001 organizations CMMi Level 5 organizations Onshore / offshore development

11. w w w. n e s s. c o m Who is using Scrum? Yahoo! Sun Siemens Nokia Philips BBC IBM US Federal Reserve SAP HP Motorola TransUnion Google Microsoft Ness

12. w w w. n e s s. c o m SCRUM Characteristics Self-organizing teams Product progresses in a series of month-long “sprints” Requirements are captured as items in a list of “product backlog” No specific engineering practices prescribed Uses generative rules to create an agile environment for delivering projects One of the “agile processes”

13. w w w. n e s s. c o m What is SCRUM?

14. w w w. n e s s. c o m What is SCRUM?

15. w w w. n e s s. c o m Scrum framework Product owner ScrumMaster Team Roles Sprint planning Sprint review Sprint retrospective Daily scrum meeting Ceremonies Product backlog Sprint backlog Burndown charts Artifacts

16. w w w. n e s s. c o m Daily Scrum Hosted by Scrum Master Attended by all, but Stakeholders don’t speak Same time every day Answer: 1)What did you do yesterday? 2)What will you do today? 3)What’s in your way? Team updates Sprint Backlog; Scrum Master updates Blocks List PO Product Owner: Set priorities Roles SM Scrum Master: Manage process, remove blocks T Team: Develop product SH Stakeholders: observe & advise Artifacts Product Backlog List of requirements & issues Owned by Product Owner Anybody can add to it Only Product Owner prioritizes Sprint Goal One-sentence summary Declared by Product Owner Accepted by team Sprint Backlog List of tasks Owned by team Only team modifies it Blocks List List of blocks & unmade decisions Owned by Scrum Master Updated daily Increment Version of the product Shippable functionality (tested, documented, etc.) Meetings Sprint Planning Meeting Hosted by Scrum Master; ½-1 day In: Product Backlog, existing product, business & technology conditions Select highest priority items in Product Backlog; declare Sprint Goal Team turns selected items into Sprint Backlog Out: Sprint Goal, Sprint Backlog Sprint Review Meeting (Demo) Hosted by Scrum Master Attended by all Informal, informational Team demos Increment All discuss Hold retrospective Announce next Sprint Planning Meeting Product Backlog Development Process Increment Sprint Planning Meeting Daily Scrum Daily Work Sprint Goal Sprint Backlog Blocks List Product Sprint Review Meeting Sprint: 30 days each Product Backlog’ Increment’ Scrum framework in Detail

17. w w w. n e s s. c o m Sprints Scrum projects make progress in a series of “sprints” Analogous to Extreme Programming Iterations Typical duration is 2–4 weeks or a calendar month at most A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint

18. w w w. n e s s. c o m Sequential vs. Overlapping Development Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986. Rather than doing all of one thing at a time......Scrum teams do a little of everything all the time Requirements DesignCodeTest

19. w w w. n e s s. c o m No changes during a sprint Plan sprint durations around how long you can commit to keeping change out of the sprint Change

20. w w w. n e s s. c o m Scrum Framework - Roles Sprint planning Sprint review Sprint retrospective Daily scrum meeting Ceremonies Product backlog Sprint backlog Burndown charts Artifacts Product owner ScrumMaster Team Roles

21. w w w. n e s s. c o m Product owner Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value Adjust features and priority every iteration, as needed Accept or reject work results

22. w w w. n e s s. c o m Product Owner Charged with maximizing ROI and managing project risk Prioritize features according to market value. Takes inputs from: Customer Team Executives Competitors Other stakeholders Adjust features and priority every iteration, as needed; accept or reject work results. Determines release plan and communicates to all

23. w w w. n e s s. c o m The ScrumMaster Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences

24. w w w. n e s s. c o m Scrum Master Serve the Team Removal of impediments to the team’s productivity Facilitates the team’s group interactions, to help the team achieve its full potential Protect the Team Protects the team from outside interference or disruption Represent the team to management May need to raise uncomfortable issues within the team Support the Team’s use of Scrum Organizes and facilitates Scrum-related practices Serves as the Scrum “conscience” of the team, reminding the team of standard Scrum practices

25. w w w. n e s s. c o m Resolves obstacles Monitors the process The ‘driver’ of the Team Keeps the Team moving Responsible for the team functioning Scrum Master Role 25

26. w w w. n e s s. c o m Meetings Artifacts Coaching Working with the Product Owner Activities of a Scrum Master 26

27. w w w. n e s s. c o m SCRUM Team Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Members should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only between sprints Involved from conception to release Equal treatment and respect for all

28. w w w. n e s s. c o m Scrum Ceremonies Product owner ScrumMaster Team Roles Product backlog Sprint backlog Burndown charts Artifacts Sprint planning Daily scrum meeting Sprint review Sprint retrospective Ceremonies

29. w w w. n e s s. c o m Sprint Planning

30. w w w. n e s s. c o m 2-5 WEEKS 2-3 DAYS (PLANNING) RECAP, DEMO, RETROSPECTIVE, RELEASE, KICK-OFF Sprint

31. w w w. n e s s. c o m Sprint planning meeting Sprint prioritization Analyze and evaluate product backlog Select sprint goal Sprint planning Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Sprint goal Sprint goal Sprint backlog Sprint backlog Business conditions Team capacity Product backlog Technology Current product Sprint Planning

32. w w w. n e s s. c o m Initiated through ITIL/CAB, PMO or ad-hoc processes Internally generated requests Customer driven Market driven Describe what your doing and why your doing it Customer need and/or market assessment Business case High-level use cases, requirements, episodes … Level of formality will vary based on value/cost of the request May involve a formal approval processes Conception

33. w w w. n e s s. c o m The Sprint Goal A short statement of what the work will be focused on during the sprint Database Application Financial services Life Sciences Support features necessary for population genetics studies. Support more technical indicators than company ABC with real-time, streaming data. Make the application run on SQL Server in addition to Oracle.

34. w w w. n e s s. c o m Managing the Sprint Backlog Individuals sign up for work of their own choosing Work is never assigned Estimated work remaining is updated daily Any team member can add, delete or change the sprint backlog Work for the sprint emerges If work is unclear, define a sprint backlog item with a larger amount of time and break it down later Update work remaining as more becomes known

35. w w w. n e s s. c o m Activity: Sprint Planning meeting Goal of Sprint Planning Meeting: For the team to make a good commitment around what it will deliver by the end of the Sprint What’s a good commitment? Clearly understood by all Shared among the team Achievable without sacrificing quality Achievable without sacrificing sustainable pace Attended by Team, Product Owner, Scrum Master, Stakeholders May require 1-2 hours for each week of Sprint duration

36. w w w. n e s s. c o m Product Owner prioritizes features Identifies key external milestones and business commitments Resource capacity plan is developed for the project Each backlog item is estimated High-level estimates (+/- 50% accuracy) Team selects items from the product backlog they can commit to completing Effort is compared to resource capacity and an initial burndown is projected At the completion of Sprint 0, a release plan review is performed and the first sprint is kicked-off Activity: Sprint Planning Meeting

37. w w w. n e s s. c o m As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4) Activity: Sprint Planning Meeting

38. w w w. n e s s. c o m The backlog items are elaborated User Stories Interaction design / screen flows Feature content, release targets, capacity are re- calibrated by the Project Leads Sprint is kicked-off with a team meeting to review and discuss goals Sprint Definition and Planning Activity: Sprint Planning Meeting

39. w w w. n e s s. c o m Feature content, release targets, capacity are continuously reviewed/discussed/debated Key participants: Scrum Master and Product Owner This is where the term Scrum came from At times, the process can be brutal, but in the end a try can be scored Incremental Planning

40. w w w. n e s s. c o m Daily Scrum

41. w w w. n e s s. c o m The Daily Scrum Parameters Daily 15-minutes Stand-up Not for problem solving Whole world is invited Only team members, ScrumMaster, product owner, can talk Helps avoid other unnecessary meetings

42. w w w. n e s s. c o m Activity : Daily Scrum Parameters Daily, same time, same place 15-minutes or less Stand-up Not for problem solving Three questions: 1.What did you do yesterday 2.What will you do today? 3.What obstacles are in your way? No discussion, conversation until meeting ends Product Owner can attend and report Following the Daily Scrum Meeting… Team members update the Sprint Backlog with hours remaining for tasks that they’ve worked on ScrumMaster adds up the hours remaining and plots it on the Burndown Chart

43. w w w. n e s s. c o m Team meeting every day at the same time in the same place Everyone attends – Development, Test, Product Owner Led by the Scrum Master (Project Manager) <15mins Each member quickly reviews new accomplishments, next tasks, and raises any impediments Impediments resolved offline! Whiteboards – the more the better The Daily Stand-Up

44. w w w. n e s s. c o m Everyone answers 3 questions These are not status for the ScrumMaster They are commitments in front of peers What did you do yesterday? 1 1 What will you do today? 2 2 Is anything in your way? 3 3

45. w w w. n e s s. c o m Sprint Review

46. w w w. n e s s. c o m The Sprint Review Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal 2-hour prep time rule No slides Whole team participates Invite the world

47. w w w. n e s s. c o m Sprint Retrospective

48. w w w. n e s s. c o m Sprint Retrospective Periodically take a look at what is and is not working Typically 15–30 minutes Done after every sprint Whole team participates ScrumMaster Product owner Team Possibly customers and others

49. w w w. n e s s. c o m Activity: Sprint Retrospective What is it? 1-2 hour meeting following each Sprint Demo Attended by Product Owner, Team, Scrum Master Usually a neutral person will be invited in to facilitate What’s working and what could work better Objective: What’s working What’s could work better Things to try in the next Sprint Why does the Retrospective matter? Accelerates visibility Accelerates action to improve It’s a key mechanism of continuous improvement If Scrum is an engine, Retrospective is the “oil filter” Catches the debris and keeps it from recirculation Keeps the engine running clean and smooth

50. w w w. n e s s. c o m Start / Stop / Continue Whole team gathers and discusses what they’d like to: Start doing Stop doing Continue doing This is just one of many ways to do a sprint retrospective.

51. w w w. n e s s. c o m Scrum Artifacts Product owner ScrumMaster Team Roles Sprint planning Sprint review Sprint retrospective Daily scrum meeting Ceremonies Product backlog Sprint backlog Burndown charts Artifacts

52. w w w. n e s s. c o m Product backlog The requirements A list of all desired work on the project Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint This is the product backlog

53. w w w. n e s s. c o m Artifact: Product Backlog List of everything that could ever be of value to the business for the team to produce Ranked in order of priority Priority is a function of ROI and risk Product Owner can make any changes they want before the start of a Sprint Planning Meeting Items added, changed, removed, reordered The farther down the list, the bigger and less defined the items become ~2 Sprints worth are defined in detail

54. w w w. n e s s. c o m Artifact: Product Backlog

55. w w w. n e s s. c o m A Sample Product Backlog Backlog itemEstimate Allow a guest to make a reservation3 As a guest, I want to cancel a reservation.5 As a guest, I want to change the dates of a reservation. 3 As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8 Improve exception handling8...30...50

56. w w w. n e s s. c o m A Sprint Burn Down Chart Remaining Hours

57. w w w. n e s s. c o m SCRUM Issues: Scalability Typical individual team is 7 ± 2 people Scalability comes from teams of teams Factors in scaling Type of application Team size Team dispersion Project duration Scrum has been used on multiple 500+ person projects

58. w w w. n e s s. c o m Scaling through the Scrum of Scrums

59. w w w. n e s s. c o m Scrum of scrums of scrums

60. w w w. n e s s. c o m Artifact: Sprint Backlog 1.Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization 2.Team determines how much time it has available to Commit during the Sprint 3.Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan 3 Simple steps

61. w w w. n e s s. c o m Artifact: Burn Down Chart Electronic may look more convenient for the Sprint Backlog and Burn Down Charts, but... Paper is fast and easy Paper is much more visible Paper doesn’t “go down”

62. w w w. n e s s. c o m Scrum Disadvantages Makes all dysfunction visible Scrum doesn’t fix anything: the team has to do it May feel like things are worse at the beginning Bad products will be delivered sooner Doomed projects will fail faster High risk of turnover Some people will refuse to stay on a Scrum team Partial adoption may be worse than none at all If adoption fails, time will have been wasted, and some people may leave

63. w w w. n e s s. c o m Where to go next www.mountaingoatsoftware.com/scrum www.scrumalliance.org www.controlchaos.com scrumdevelopment@yahoogroups.com

64. w w w. n e s s. c o m Any Questions? Thank You!