Scaling Scrum with UX

5,491 views

Published on

3 patterns to scale scrum - presented at the Big Design Conference in Dallas 2012

Published in: Technology
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,491
On SlideShare
0
From Embeds
0
Number of Embeds
175
Actions
Shares
0
Downloads
63
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Scaling Scrum with UX

  1. Scaling Scrum with UX
  2. Caleb JenkinsdevelopingUX.com @calebjenkins #bigd12ProactionMentors.com
  3. Development Engineering Process Object Orientation Automated Tests Agile, Lean, XP SOLID Source Control Team Dynamics Patterns Automated Builds Continuous Learning Secure Coding
  4. back to…Scaling Scrum
  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. agile principles & practices process framework scrum technical engineering clean code tddautomated unit test s.o.l.i.d. sonar continuous integration (ci) code coverage technical debt
  7. Software is a cake Scrum is a recipe
  8. what if we throwout the recipe, andjust use ingredientswe like?
  9. 16
  10. 17
  11. 18
  12. Can we do agile?
  13. Noyou can be agile
  14. Scrumagile you can do
  15. Scrum
  16. Scrum is An Elegantly Simple Software MethodThree Roles Product Owner Scrum Master Self-organizing teamsThree ceremonies Sprint/Iteration Planning Daily Scrum (Stand-Up) / debrief Scrum Sprint Review MeetingThree Artifacts Product Backlog Sprint Backlog Burn Down Chart
  17. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
  18. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
  19. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
  20. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Velocity
  21. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
  22. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
  23. Burn Down Customer Needs Daily Scrum SCRUM (stand-up)Product Owner Team Scrum Master Sprint Definition ofProduct 1 Month to 2 Weeks DoneBacklog Sprint Review Definition of (including demo) Ready Retrospective Sprint Planning Sprint Backlog Burn Up Shippable Velocity Release
  24. WAIT! What about …Task boards, Information RadiatorsReducing Work In Progress, Time BoxingSelf Organization, Pull vsPush, Empowerment, ContinuousLearning, Planning Poker, StorySizing, Velocity, Team Swarming…
  25. Scrum is Simplenot to be confused with easy 
  26. 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
  27. let’s talk about“cross functional”
  28. we have team goals we are not all the same
  29. and then Scrum is silent.
  30. and that’s why scrum is a framework
  31. whydo you need to scale?
  32. whatare your goals?
  33. Product Product ProductBacklog Backlog Backlog to do more?
  34. to go faster?ProductBacklog
  35. Product Product ProductBacklog Backlog Backlog to integrate?
  36. Scrum of Scrums (SoS)
  37. Scrum of Scrums is a reactive way tosynchronize teams and remove cross team impediments scrum of scrums scrum scrum scrum
  38. Coordination Team
  39. Coordination Team is a lean concept tosynchronize teams and proactively align backlog priorities Coordination Team scrum scrum scrum
  40. Coordination Team Product Product Product Backlog Backlog Backlog
  41. Coordination Team Product Product Product Backlog Backlog Backlog
  42. Coordination Team Org.Backlog Product Product Product Backlog Backlog Backlog
  43. Product Owner Team
  44. 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
  45. ? Scrum
  46. 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
  47. 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
  48. let’s talk about the product owner
  49. product visionrepresent the business write storiesupdate stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
  50. product visionrepresent the business write storiesupdate stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
  51. product visionrepresent the business write storiesupdate stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning
  52. product vision write storiesmeet with customers prepare for Sprint Planning
  53. product vision write storiesmeet with customers prepare for Sprint Planning
  54. product vision write storiesmeet with customers prepare for Sprint Planning
  55. product vision write storiesmeet with customers prepare for Sprint Planning
  56. Product Owner Team scales the role ofProduct Owner to support multiple Scrum teams with a single vision Product Owner Team scrum scrum scrum
  57. In a Product Owner Team, the PO acts as acoordinator or quarterback between all of the players. This team supports the Scrum Team
  58. The Product Owner Team works on their owncadence, ensuring backlog grooming and story readiness for the Scrum Team
  59. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hatsEveryone works within the Sprint Cycle to deliver working software!
  60. The Team Avg. Scrum Team Size 7±2 Everyone wears multiple hatsEveryone works within the Sprint Cycle to deliver working software!
  61. Pitfallsahead
  62. enterprise“adoption”
  63. cross teamcomparisons
  64. Beware the Matrix
  65. Bewarethe longcycles
  66. Optimizationscapacity vs through put
  67. productivity vs efficiency
  68. scrumis not a silver bullet
  69. lets review
  70. reactive approach to removescrum of scrums cross team impediments multiple product owners synchronizingCoordination Team and proactively aligning backlogs single PO working with supporting roles, to support multiple scrum teams
  71. final words of wisdom?
  72. Bring your cleats
  73. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com
  74. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com
  75. 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/
  76. 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/
  77. 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/
  78. 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/
  79. @calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com

×