Scaling Scrum with UX in the Enterprise
•Download as PPTX, PDF•
7 likes•2,282 views
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/
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Scaling Scrum with UX in the Enterprise
Similar to Scaling Scrum with UX in the Enterprise (20)
More from Caleb Jenkins
More from Caleb Jenkins (19)
Recently uploaded
Recently uploaded (20)
Scaling Scrum with UX in the Enterprise
- 12. Development Object Orientation SOLID Patterns Secure Coding Engineering Automated Tests Source Control Automated Builds Process Agile, Lean, XP Team Dynamics Continuous Learning
- 19. 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
- 20. 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
- 22. - 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 - )
- 23. DoPlan DP DP DP
- 24. Software is a cake Scrum is a recipe
- 25. what if we throw out the recipe, and just use ingredients we like?
- 26. 26
- 27. 27
- 28. 28
- 29. Can we do agile?
- 30. you can be agile No
- 31. Scrum agile you can do
- 32. Scrum
- 33. 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
- 34. 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
- 35. 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
- 36. 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
- 37. 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
- 38. 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
- 39. 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
- 40. 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
- 41. 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..
- 42. Scrum is Simple not to be confused with easy
- 43. 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
- 44. let’s talk about “cross functional”
- 45. we have team goals we are not all the same
- 46. Traditional Scrum Scaling Concepts The Team
- 47. Traditional Scrum Scaling Concepts scrum scrum scrum
- 48. Traditional Scrum Scaling Concepts scrum scrum scrum scrumofscrums
- 49. and then Scrum is silent.
- 50. and that’s why scrum is a framework
- 51. why do you need to scale?
- 57. Scrum of Scrums is a reactive way to synchronize teams and remove cross team impediments scrum scrum scrum scrumofscrums
- 59. Coordination Team is a lean concept to synchronize teams and proactively align backlog priorities scrum scrum scrum CoordinationTeam
- 64. 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
- 65. Scrum ?
- 66. 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
- 67. let’s talk about the product owner
- 68. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
- 69. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
- 70. represent the business product vision write stories slice stories groom the Product Backlog prepare for Sprint Planning meet with customers update stake holders
- 71. product vision write stories prepare for Sprint Planning meet with customers
- 72. product vision write stories prepare for Sprint Planning meet with customers
- 73. product vision write stories prepare for Sprint Planning meet with customers
- 74. product vision write stories prepare for Sprint Planning meet with customers
- 76. Product Owner Team scales the role of Product Owner to support multiple Scrum teams with a single vision scrum scrum scrum ProductOwnerTeam
- 77. In a Product Owner Team, the PO acts as a coordinator or quarterback between all of the players. This team supports the Scrum Team
- 78. The Product Owner Team works on their own cadence, ensuring backlog grooming and story readiness for the Scrum Team
- 79. The Product Owner Team works on their own cadence, ensuring backlog grooming and story readiness for the Scrum Team
- 80. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hats Everyone works within the Sprint Cycle to deliver working software!
- 84. SprintingSprintingSprinting Product Owner Team Sprinting Grooming Product Backlog new sizing ready in sprint done closed
- 86. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Ideas Ideas Ideas Ideas Lean UX
- 87. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Lean UX
- 88. DeliveryDeliveryDelivery Product Owner Team Delivery Deliv Lean UX
- 90. Pitfalls ahead
- 92. the macro doesn’t work without the micro
- 102. lets review
- 103. 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
- 104. final words of wisdom?
- 105. Bring your cleats
- 112. Please Complete An Evaluation Form Your input is important! You can access Evaluation Forms at: http://TulsaTechFest.com