scaling scrum with ux in the enterprise

Post on 10-May-2015

433 Views

Category:

Software

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

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/

TRANSCRIPT

Scaling Scrum

Please help us!Thank our Sponsors:

Agile?

Managers?

Developers?

“Enterprisey” Company?

developingUX.comspeakermix.com/calebjenkins

@calebjenkins#ttf2014

developingUX.comspeakermix.com/calebjenkins

@calebjenkins#ttf2014

DevelopmentObject Orientation

SOLID

Patterns

Secure Coding

EngineeringAutomated Tests

Source Control

Automated Builds

ProcessAgile, Lean, XP

Team Dynamics

Continuous Learning

Building teams that engineer better software

D e v e l o p m e n t ∙ E n g i n e e r i n g ∙ P r o c e s s

What is Agile?

Others

SW Dev

ProcessDSDM1995

Crystal Clear1990

RUP1990

XP1996

Scrum1995

Feature Driven

Development

1997

Kanban

scrumban

lean toyota

agile principlesWe 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

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

Process(scrum)

Practices(Engineering)

Principles(Culture + Code Quality)

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

DoPlan

DP DP DP

Software is a cake

Scrum is a recipe

?what if we throw out the recipe, and just use ingredients we like?

Can we do agile?

you can be agileNo

Scrum

agile you can do

Scrum

Scrum

Scrum is An Elegantly Simple Software Method

Three RolesProduct OwnerScrum MasterSelf-organizing teams

Three ceremoniesSprint/Iteration PlanningDaily Scrum (Stand-Up) / debriefSprint Review Meeting

Three ArtifactsProduct BacklogSprint BacklogBurn Down Chart

Sprint1 Month to 2 Weeks

Shippable

Release

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUMProduct Owner

Customer Needs

Definition of Ready

Sprint Planning SprintBacklog

Definition of DoneProduct

Backlog

Sprint1 Month to 2 Weeks

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUM

Definition of Ready

Sprint Planning SprintBacklog

Definition of DoneProduct

Backlog

Product Owner

Customer Needs

Sprint1 Month to 2 Weeks

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUMProduct Owner

Customer Needs

Definition of Ready

Sprint Planning SprintBacklog

Definition of DoneProduct

Backlog

Sprint1 Month to 2 Weeks

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUMProduct Owner

Customer Needs

Definition of Done

Definition of Ready

Sprint Planning SprintBacklog

Product Backlog

Sprint1 Month to 2 Weeks

Shippable

Release

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUMProduct Owner

Customer Needs

Definition of Ready

Sprint Planning SprintBacklog

Definition of DoneProduct

Backlog

Sprint1 Month to 2 Weeks

Shippable

Release

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

SCRUMProduct Owner

Customer Needs

Definition of Ready

Sprint Planning SprintBacklog

Product Backlog Sprint Review

(including demo)

Retrospective

Burn Up

Velocity

Definition of Done

Sprint1 Month to 2 Weeks

Shippable

Release

Burn Down

Daily Scrum (stand-up)

TeamScrum Master

Sprint Review(including demo)

Retrospective

Burn Up

Velocity

SCRUMProduct Owner

Customer Needs

Definition of Ready

Sprint Planning SprintBacklog

Definition of DoneProduct

Backlog

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

Scrum is Simplenot to be confused with easy

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 ●

POSM

Scrum

3 Roles

let’s talk about “cross functional”

we have team goals we are not all the

same

Traditional Scrum Scaling ConceptsThe Team

PO

SM

UX

Traditional Scrum Scaling Concepts

scrum scrum scrum

Traditional Scrum Scaling Concepts

scrum scrum scrum

scrum of scrums

and then Scrumis silent.

and that’s why scrum is a framework

whydo you need to scale?

whatare your goals?

to do more?

Product Backlog

Product Backlog

Product Backlog

to go faster?

Product Backlog

to integrate?

Product Backlog

Product Backlog

Product Backlog

Scrum of Scrums(SoS)

Scrum of Scrums is a reactive way to synchronize teams and remove cross team

impediments

scrum scrum scrum

scrum of scrums

Coordination Team

Coordination Team is a lean concept to synchronize teams and proactively align

backlog priorities

scrum scrum scrum

Coordination Team

Product Backlog

Product Backlog

Product Backlog

Coordination Team

Product Backlog

Product Backlog

Product Backlog

Coordination Team

Product Backlog

Product Backlog

Product Backlog

Coordination Team

Org.Backlog

Product Owner Team

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 ●

POSM

Scrum

3 Roles

UX

Scrum

3 Roles

?BA

DBA

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 ●

POSM

Scrum

3 Roles

UX

let’s talk about the product owner

represent the business

product vision

write stories

slice stories

groom the Product Backlogprepare for Sprint Planning

meet with customers

update stake holders

Arch

DBA

BA

UX

represent the business

product vision

write stories

slice stories

groom the Product Backlogprepare for Sprint Planning

meet with customers

update stake holders

UX

represent the business

product vision

write stories

slice stories

groom the Product Backlogprepare for Sprint Planning

meet with customers

update stake holders

UX

product vision

write stories

prepare for Sprint Planning

meet with customers

UX

product vision

write stories

prepare for Sprint Planning

meet with customers

UX

product vision

write stories

prepare for Sprint Planning

meet with customers

UX

product vision

write stories

prepare for Sprint Planning

meet with customers

Arch

DBA

BA

UX

#MSU !

Product Owner Team scales the role of Product Owner to support multiple Scrum

teams with a single vision

scrum scrum scrum

Product Owner Team

UX

Arch

BA

BAPO

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

UX

Arch

BA

BAPO

The Product Owner Team works on their own cadence, ensuring backlog grooming and story

readiness for the Scrum Team

UX

Arch

BA

BAPO

The Product Owner Team works on their own cadence, ensuring backlog grooming and story

readiness for the Scrum Team

The Team

PO

SM

UX

Avg. Scrum Team Size 7±2Everyone wears multiple hats

Everyone works within the Sprint Cycle to deliver working software!

business value!

UX

Arch

BA

BAPO

MetaBacklog

“Sagas”

Product Owner Team

Stories

UX

Arch

BA

BAPO

MetaBacklog

“Sagas”

Product Backlog

Sprinting

Software

Product Owner Team

Validation

“Definition of

Ready”

“Definition of

Done”

Stories

UX

Arch

BA

BAPO

IdeaBacklog

“Ideas”

Product Backlog

Sprinting

Software

Product Owner Team

Validation

“Definition of

Ready”

“Definition of

Done”

SprintingSprintingSprinting

Product Owner TeamSprinting

GroomingProductBacklog

new sizing readyin

sprintdone closed

SprintingSprintingSprinting

Product Owner TeamSprinting

GroomingProductBacklog

DeliveryDeliveryDelivery

Product Owner Team

Delivery Delivery

Ideas Ideas Ideas Ideas

Lean UX

DeliveryDeliveryDelivery

Validati

on

Product Owner Team

Delivery Delivery

Lean UX

Stories

StoriesValid

ation

DeliveryDeliveryDelivery

Validati

on

Product Owner Team

Delivery Delivery

Lean UX

Stories

StoriesValid

ation

Validati

on

Validati

on

Validati

on

Stories

Storie

s

Pitfalls ahead

enterprise “adoption”

the macro doesn’t work

without the micro

crossteam

comparisons

Beware the Matrix

Beware the long

cycles

Optimizationscapacity vs through

put

productivity

vs efficiency

lets review

scrum of scrums

Coordination Team

reactive approach to removecross team impediments

multiple product owners synchronizing and proactively aligning backlogs

single PO working with supporting roles, to support multiple scrum teams

final words of wisdom?

Bring your cleats

developingUX.comspeakermix.com/calebjenkins

@calebjenkins

Photo Creditshttp://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/

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/

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/

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/

http://www.flickr.com/photos/jonobass/2082974481/

Please Complete An Evaluation FormYour input is important!

You can access Evaluation Forms at:

http://TulsaTechFest.com

Fill them out!

You can win additional prizes!

Like a $50 Best Buy Gift Card!!

Winner drawn – Midnight, Sun Aug 17th!

Please help us!Thank our Sponsors:

developingUX.comspeakermix.com/calebjenkins

@calebjenkins

top related