Scaling Scrum with UX in the Enterprise

1,581 views

Published on

Scrum is the most popular Agile framework in the world for effective team collaboration on complex projects. Scrum provides a small set of rules that create just enough structure for teams to be able to focus their innovation. Scrum is optimized for teams for teams of 5 to 9 people. Making Scrum work with larger teams or in large enterprise environments brings its own set of challenges. This talk presents 3 patterns used on enterprise teams to scale Scrum effectively with global teams.

This presentation was given at the 2014 Tulsa Tech Fest in Tulsa, OK - http://developingux.com/TulsaTech2014/

Published in: Software
2 Comments
7 Likes
Statistics
Notes
No Downloads
Views
Total views
1,581
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
38
Comments
2
Likes
7
Embeds 0
No embeds

No notes for slide

Scaling Scrum with UX in the Enterprise

  1. 1. Scaling Scrum
  2. 2. developingUX.com speakermix.com/calebjenkins @calebjenkins #ttf2014
  3. 3. developingUX.com speakermix.com/calebjenkins @calebjenkins #ttf2014
  4. 4. Development Object Orientation SOLID Patterns Secure Coding Engineering Automated Tests Source Control Automated Builds Process Agile, Lean, XP Team Dynamics Continuous Learning
  5. 5. agile principles We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. (2001) Kent Beck l Mike Beedle l Arie van Bennekum l Alistair Cockburn l Ward Cunningham l Martin Fowler l James Grenning l Jim Highsmith l Andrew Hunt l Ron Jeffries l Jon Kern l Brian Marick l Robert C. Martin l Steve Mellor l Ken Schwaber l Jeff Sutherland l Dave Thomas
  6. 6. agile principles & practices process framework scrum technical engineering automated unit test clean code tdd continuous integration (ci) technical debt code coverage s.o.l.i.d. sonar
  7. 7. Process (scrum) Practices (Engineering) Principles (Culture + Code Quality)
  8. 8. - Helmuth von Moltke. (German military strategist 1800-1891) “No Battle Plan Survives Contact With the Enemy” “Plans are worthless. Planning is invaluable.” – Sir Winston Churchill (1874 – 1965) “Everyone Has A Plan Until They Get Punched In The Face” - Mike Tyson American Philosopher (1966 - )
  9. 9. DoPlan DP DP DP
  10. 10. Software is a cake Scrum is a recipe
  11. 11. what if we throw out the recipe, and just use ingredients we like?
  12. 12. 26
  13. 13. 27
  14. 14. 28
  15. 15. Can we do agile?
  16. 16. you can be agile No
  17. 17. Scrum agile you can do
  18. 18. Scrum
  19. 19. Scrum Scrum is An Elegantly Simple Software Method Three Roles Product Owner Scrum Master Self-organizing teams Three ceremonies Sprint/Iteration Planning Daily Scrum (Stand-Up) / debrief Sprint Review Meeting Three Artifacts Product Backlog Sprint Backlog Burn Down Chart
  20. 20. Sprint 1 Month to 2 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
  21. 21. Sprint 1 Month to 2 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog Product Owner Customer Needs
  22. 22. Sprint 1 Month to 2 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
  23. 23. Sprint 1 Month to 2 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Done Definition of Ready Sprint Planning Sprint Backlog Product Backlog
  24. 24. Sprint 1 Month to 2 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
  25. 25. Sprint 1 Month to 2 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Product Backlog Sprint Review (including demo) Retrospective Burn Up Velocity Definition of Done
  26. 26. Sprint 1 Month to 2 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
  27. 27. WAIT! What about … Task boards, Information Radiators Reducing Work In Progress, Time Boxing Self Organization, Pull vs Push, Empowerment, Continuous Learning, Planning Poker, Story Sizing, Velocity, Team Swarming… etc, etc, etc..
  28. 28. Scrum is Simple not to be confused with easy 
  29. 29. Scrum Master Product Owner The Team Facilitates and protects the process ● removes team impediments ● Represents the business interests ● sets priorities ● owns the product backlog Does the work ● self organizes ● owns sprint backlog ● dev, test, arch, DBA, BA, SME, etc ● Scrum
  30. 30. let’s talk about “cross functional”
  31. 31. we have team goals we are not all the same
  32. 32. Traditional Scrum Scaling Concepts The Team
  33. 33. Traditional Scrum Scaling Concepts scrum scrum scrum
  34. 34. Traditional Scrum Scaling Concepts scrum scrum scrum scrumofscrums
  35. 35. and then Scrum is silent.
  36. 36. and that’s why scrum is a framework
  37. 37. why do you need to scale?
  38. 38. what are your goals?
  39. 39. to do more? Product Backlog Product Backlog Product Backlog
  40. 40. to go faster? Product Backlog
  41. 41. to integrate? Product Backlog Product Backlog Product Backlog
  42. 42. Scrum of Scrums (SoS)
  43. 43. Scrum of Scrums is a reactive way to synchronize teams and remove cross team impediments scrum scrum scrum scrumofscrums
  44. 44. Coordination Team
  45. 45. Coordination Team is a lean concept to synchronize teams and proactively align backlog priorities scrum scrum scrum CoordinationTeam
  46. 46. Product Backlog Product Backlog Product Backlog CoordinationTeam
  47. 47. Product Backlog Product Backlog Product Backlog CoordinationTeam
  48. 48. Product Backlog Product Backlog Product Backlog CoordinationTeam Org. Backlog
  49. 49. Product Owner Team
  50. 50. Scrum Master Product Owner The Team Facilitates and protects the process ● removes team impediments ● Represents the business interests ● sets priorities ● owns the product backlog Does the work ● self organizes ● owns sprint backlog ● dev, test, arch, DBA, BA, SME, etc ● Scrum
  51. 51. Scrum ?
  52. 52. Scrum Master Product Owner The Team Facilitates and protects the process ● removes team impediments ● Represents the business interests ● sets priorities ● owns the product backlog Does the work ● self organizes ● owns sprint backlog ● dev, test, arch, DBA, BA, SME, etc ● Scrum
  53. 53. let’s talk about the product owner
  54. 54. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
  55. 55. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
  56. 56. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
  57. 57. product vision write stories prepare for Sprint Planning meet with customers
  58. 58. product vision write stories prepare for Sprint Planning meet with customers
  59. 59. product vision write stories prepare for Sprint Planning meet with customers
  60. 60. product vision write stories prepare for Sprint Planning meet with customers
  61. 61. Product Owner Team scales the role of Product Owner to support multiple Scrum teams with a single vision scrum scrum scrum ProductOwnerTeam
  62. 62. In a Product Owner Team, the PO acts as a coordinator or quarterback between all of the players. This team supports the Scrum Team
  63. 63. The Product Owner Team works on their own cadence, ensuring backlog grooming and story readiness for the Scrum Team
  64. 64. The Product Owner Team works on their own cadence, ensuring backlog grooming and story readiness for the Scrum Team
  65. 65. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hats Everyone works within the Sprint Cycle to deliver working software!
  66. 66. Meta Backlog “Sagas” Product Owner Team
  67. 67. Stories Meta Backlog “Sagas” Product Backlog Sprinting Software Product Owner Team Validation
  68. 68. Stories Idea Backlog “Ideas” Product Backlog Sprinting Software Product Owner Team Validation
  69. 69. SprintingSprintingSprinting Product Owner Team Sprinting Grooming Product Backlog new sizing ready in sprint done closed
  70. 70. SprintingSprintingSprinting Product Owner Team Sprinting Grooming Product Backlog
  71. 71. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Ideas Ideas Ideas Ideas Lean UX
  72. 72. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Lean UX
  73. 73. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Lean UX
  74. 74. Pitfalls ahead
  75. 75. enterprise “adoption”
  76. 76. the macro doesn’t work without the micro
  77. 77. cross team comparisons
  78. 78. Beware the Matrix
  79. 79. Beware the long cycles
  80. 80. Optimizations capacity vs through put
  81. 81. productivity vs efficiency
  82. 82. lets review
  83. 83. scrumofscrums CoordinationTeam reactive approach to remove cross team impediments multiple product owners synchronizing and proactively aligning backlogs single PO working with supporting roles, to support multiple scrum teams
  84. 84. final words of wisdom?
  85. 85. Bring your cleats
  86. 86. developingUX.com speakermix.com/calebjenkins @calebjenkins
  87. 87. http://www.flickr.com/photos/johnwilliamsphd/3288928346/ http://www.flickr.com/photos/grahamcrewe/396400543/ http://www.flickr.com/photos/nowak/5048838814/ http://www.flickr.com/photos/hugosimmelink/2252095723/ http://www.flickr.com/photos/trinity-of-one/20562069/
  88. 88. http://www.flickr.com/photos/maniya/2471677206/ http://www.flickr.com/photos/fireflythegreat/2845637227/ http://www.flickr.com/photos/tambako/2414419226/ http://www.flickr.com/photos/woodwood/2521586391/ http://www.flickr.com/photos/92795775@N00/4469179194/
  89. 89. http://www.flickr.com/photos/maniya/2471677206/ http://www.flickr.com/photos/zlatko/4304565375/ http://www.flickr.com/photos/22750018@N05/4379889930/ http://www.flickr.com/photos/bluesquarething/6418961921/ http://www.flickr.com/photos/spikeydudeuk/4656395114/
  90. 90. http://www.flickr.com/photos/planettelex/826864344/ http://www.flickr.com/photos/jscherber/2264624742/ http://www.flickr.com/photos/neilarmstrong2/5492920817/ http://www.flickr.com/photos/rutlo/3086313958/ http://www.flickr.com/photos/freakgirl/3322751664/
  91. 91. http://www.flickr.com/photos/jonobass/2082974481/
  92. 92. Please Complete An Evaluation Form Your input is important! You can access Evaluation Forms at: http://TulsaTechFest.com
  93. 93. developingUX.com speakermix.com/calebjenkins @calebjenkins

×