Scaling Scrum with UX

2.
* I’m hereto help.

7.
Development Engineering Process Object Orientation Automated Tests Agile, Lean, XP SOLID Source Control Team Dynamics Patterns Automated Builds Continuous Learning Secure Coding

8.
back to… Scaling Scrum

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.
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

14.
Scrum

15.
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

16.
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

17.
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

18.

19.

20.

21.

22.

23.
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..

24.
Scrum is Simple notto be confused with easy 

25.
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

26.
? Scrum

27.
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

28.
The Team Avg. Scrum Team Size 7±2 Everyone wear’s multiple hats Everyone works within the Sprint Cycle to deliver working software!

29.
The Team Avg. Scrum Team Size 7±2 Everyone wear’s multiple hats Everyone works within the Sprint Cycle to deliver working software!

30.
let’s talk about “crossfunctional”

31.
we have teamgoals we are not all the same

32.
Traditional Scrum ScalingConcepts The Team scrum of scrums scrum scrum scrum

33.
and then Scrum is silent.

34.
and that’s why scrum is a framework

35.
Scrum of Scrumsis a reactive way to synchronize teams and remove cross team impediments scrum of scrums scrum scrum scrum

36.
Coordination Team

37.
Coordination Team isa lean concept to synchronize teams and proactively align backlog priorities Coordination Team scrum scrum scrum

38.
let’s talk aboutthe product owner

39.
product vision represent thebusiness write stories update stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning

40.
we all where multiplehats

41.
Product Owner Team

42.
In a ProductOwner Team, the PO acts as a coordinator or quarterback between all of the players. This team supports the Scrum Team

43.
Product Owner Teamscales the role of Product Owner to support multiple Scrum teams with a single vision Product Owner Team scrum scrum scrum

44.
product vision represent thebusiness write stories update stake holders slice stories meet with customers groom the Product Backlog prepare for Sprint Planning

45.
product vision write stories meet with customers prepare for Sprint Planning

46.

47.

48.

49.
Pitfalls ahead

50.
cross team comparisons

51.
enterprise “adoption”

52.
Beware the Matrix

53.
Beware the long cycles

54.
scrum is not a silver bullet

55.
lets review

56.
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

57.
final words ofwisdom?

58.
Bring your cleats

59.
@calebjenkins http://developingux.com @proactionmentor caleb@calebjenkins.com

60.
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/

61.
http://www.flickr.com/photos/planettelex/826864344/

Scaling Scrum with UX

More Related Content

What's hot

Similar to Scaling Scrum with UX

More from Caleb Jenkins

Recently uploaded

Scaling Scrum with UX