Downloaded 64 times
Uploaded byCaleb Jenkins
Scaling Scrum with UX
This document summarizes scaling Scrum with UX. It discusses various approaches to scaling Scrum to support multiple teams, including Scrum of Scrums, a Coordination Team, and a Product Owner Team. Scrum of Scrums is a reactive approach where representatives from each team meet to remove cross-team impediments. A Coordination Team proactively aligns backlog priorities across teams. A Product Owner Team supports multiple Scrum teams with a single product vision through story writing and backlog grooming. The document cautions that while Scrum can scale, its principles of self-organization and empiricism should not be lost.
More Related Content
![[QaOps] Continuouss Integration | Pipeline strategy](https://cdn.slidesharecdn.com/ss_thumbnails/pipelinestrategy-200601222821-thumbnail.jpg?width=640&height=640&fit=bounds)
![Designing with Lean UX : Rapid Product Design [UX Lisbon 2014]](https://cdn.slidesharecdn.com/ss_thumbnails/uxlisbon2014designingleanux-workshopslideshare-140604100358-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
More from Caleb Jenkins
Scaling Scrum with UX
- 2. Scaling Scrum with UX
- 3. Caleb Jenkins developingUX.com @calebjenkins#bigd12 ProactionMentors.com
- 6. Development Engineering Process Object Orientation Automated Tests Agile, Lean, XP SOLID Source Control Team Dynamics Patterns Automated Builds Continuous Learning Secure Coding
- 8.
- 11. 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
- 12. agile principles &practices process framework scrum technical engineering clean code tdd automated unit test s.o.l.i.d. sonar continuous integration (ci) code coverage technical debt
- 13. Software is acake Scrum is a recipe
- 14. what if wethrow out the recipe, and just use ingredients we like?
- 15.
- 16.
- 17.
- 18. Can we doagile?
- 19. No you can beagile
- 20.
- 21.
- 22. Scrum is AnElegantly Simple Software Method Three Roles Product Owner Scrum Master Self-organizing teams Three ceremonies Sprint/Iteration Planning Daily Scrum (Stand-Up) / debrief Scrum Sprint Review Meeting Three Artifacts Product Backlog Sprint Backlog Burn Down Chart
- 23. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
- 24. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
- 25. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
- 26. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
- 27. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
- 28. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
- 29. Burn Down CustomerNeeds Daily Scrum SCRUM (stand-up) Product Owner Team Scrum Master Sprint Definition of Product 1 Month to 2 Weeks Done Backlog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
- 30. 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…
- 31. Scrum is Simple notto be confused with easy
- 32. Scrum Master Product Owner The Team Represents the Does the work Facilitates and business interests ● self organizes ● protects the process ● sets priorities ● owns sprint backlog ● removes team owns the product ● dev, test, arch, DBA, impediments ● backlog BA, SME, etc ● Scrum
- 33. let’s talk about “crossfunctional”
- 34. we have teamgoals we are not all the same
- 36. and then Scrum is silent.
- 37. and that’s why scrum is a framework
- 38. why do you needto scale?
- 39.
- 40. Product Product Product Backlog Backlog Backlog to do more?
- 41.
- 42. Product Product Product Backlog Backlog Backlog to integrate?
- 43. Scrum of Scrums (SoS)
- 44. Scrum of Scrumsis a reactive way to synchronize teams and remove cross team impediments scrum of scrums scrum scrum scrum
- 45.
- 46. Coordination Team isa lean concept to synchronize teams and proactively align backlog priorities Coordination Team scrum scrum scrum
- 47. Coordination Team Product Product Product Backlog Backlog Backlog
- 48. Coordination Team Product Product Product Backlog Backlog Backlog
- 49. Coordination Team Org. Backlog Product Product Product Backlog Backlog Backlog
- 50.
- 51. Scrum Master Product Owner The Team Represents the Does the work Facilitates and business interests ● self organizes ● protects the process ● sets priorities ● owns sprint backlog ● removes team owns the product ● dev, test, arch, DBA, impediments ● backlog BA, SME, etc ● Scrum
- 52. ? Scrum
- 53. Scrum Master Product Owner The Team Represents the Does the work Facilitates and business interests ● self organizes ● protects the process ● sets priorities ● owns sprint backlog ● removes team owns the product ● dev, test, arch, DBA, impediments ● backlog BA, SME, etc ● Scrum
- 54. Scrum Master Product Owner The Team Represents the Does the work Facilitates and business interests ● self organizes ● protects the process ● sets priorities ● owns sprint backlog ● removes team owns the product ● dev, test, arch, DBA, impediments ● backlog BA, SME, etc ● Scrum
- 55. let’s talk aboutthe product owner
- 56. product vision represent thebusiness write stories update stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
- 57. product vision represent thebusiness write stories update stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
- 58. product vision represent thebusiness write stories update stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
- 59. product vision write stories meet with customers prepare for Sprint Planning
- 60. product vision write stories meet with customers prepare for Sprint Planning
- 61. product vision write stories meet with customers prepare for Sprint Planning
- 62. product vision write stories meet with customers prepare for Sprint Planning
- 65. Product Owner Teamscales the role of Product Owner to support multiple Scrum teams with a single vision Product Owner Team scrum scrum scrum
- 66. In a ProductOwner Team, the PO acts as a coordinator or quarterback between all of the players. This team supports the Scrum Team
- 67. The Product OwnerTeam works on their own cadence, ensuring backlog grooming and story readiness for the Scrum Team
- 68. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hats Everyone works within the Sprint Cycle to deliver working software!
- 69. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hats Everyone works within the Sprint Cycle to deliver working software!
- 74.
- 75.
- 76. cross team comparisons
- 77.
- 78.
- 79.
- 80. productivity vs efficiency
- 81. scrum is not a silver bullet
- 82.
- 83. reactive approach toremove scrum of scrums cross team impediments multiple product owners synchronizing Coordination Team and proactively aligning backlogs single PO working with supporting roles, to support multiple scrum teams
- 84. final words ofwisdom?
- 85.
- 86. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com
- 87. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com
- 88. 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/
- 89. 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/
- 90.
- 91.
- 92. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com