agile in enterprise - tpse 2013

46
THE MISSING PIECES AGILE IN ENTERPRISE

Upload: varokas

Post on 22-Dec-2014

64 views

Category:

Technology


2 download

DESCRIPTION

by: http://www.tpseconf.org/team-member/varokas-panusuwan/ We all have heard about how Agile nourish in a team. However, successful adoption in a large organization requires far beyond jelled teams. It is about how changes happened and how transformation spread throughout organization. It is about how sprint teams communicate and coordinate. It is about how to ensure that all managements, engineers and operations march towards one goal. This session will discuss the essential topics in Agile adoption when scaling up to large enterprise. Why simple structure such as teams of teams is not enough. What are the missing pieces. How a billion dollars company, starting with a few Scrum teams, leverages Agile to bring value to customers exponentially faster, is publicly identified by their execution of Agile and in the end is recognized by Forbes magazine as one of the world’s most innovative company.

TRANSCRIPT

Page 1: Agile in Enterprise - TPSE 2013

THE MISSING PIECESAGILE IN ENTERPRISE

Page 2: Agile in Enterprise - TPSE 2013
Page 3: Agile in Enterprise - TPSE 2013

TDD

Scrum

XP

Continuous Delivery

Continuous Integration

Automated Tests

Multidisciplinary Team

Retrospective

Page 4: Agile in Enterprise - TPSE 2013
Page 5: Agile in Enterprise - TPSE 2013

YOUR ENTERPRISE, INC

Page 6: Agile in Enterprise - TPSE 2013

WHO AM I?

Page 7: Agile in Enterprise - TPSE 2013

WHAT I DO

Page 8: Agile in Enterprise - TPSE 2013

* My presentation here reflect my personal views and do not necessarily represent those of my employer.

Page 9: Agile in Enterprise - TPSE 2013
Page 10: Agile in Enterprise - TPSE 2013

BRIAN PASCH - THE SIX HORSEMEN OF AUTOMOTIVE INNOVATION

“One company that has impressed me with their agile development is Cobalt”.

“… skeptics said that they would be stuck for years with integrating the ADP … It took the Executive team just two weeks to make

a decision on how to move forward. “

“Dealers will have to get used to Cobalt leading the market and not being late to the

party“

Page 11: Agile in Enterprise - TPSE 2013

AGILE IN ENTERPRISE

• Mission 1: Survive

• Mission 2: Spread

• Mission 3: Conquer

Page 12: Agile in Enterprise - TPSE 2013

SURVIVEMISSION 1

Z

Page 13: Agile in Enterprise - TPSE 2013
Page 14: Agile in Enterprise - TPSE 2013
Page 15: Agile in Enterprise - TPSE 2013

“BUSINESS ACCEPTANCE CRITERIA”

Page 16: Agile in Enterprise - TPSE 2013

KPI?

Page 17: Agile in Enterprise - TPSE 2013

GOAL

GOAL GOAL GOAL

GOAL GOAL GOAL GOAL

Page 18: Agile in Enterprise - TPSE 2013

SPREADMISSION 2

Page 19: Agile in Enterprise - TPSE 2013
Page 20: Agile in Enterprise - TPSE 2013

GOAL

GOAL GOAL GOAL

GOAL GOAL GOAL GOAL

Page 21: Agile in Enterprise - TPSE 2013

–MARY POPPENDIECK

“How long would it take your organization to deploy a change that involves just one

single line of code?”

Page 22: Agile in Enterprise - TPSE 2013
Page 23: Agile in Enterprise - TPSE 2013

CONQUERMISSION 3

Page 24: Agile in Enterprise - TPSE 2013
Page 25: Agile in Enterprise - TPSE 2013
Page 26: Agile in Enterprise - TPSE 2013

PO

PO

POFEATURES

ARCH

ARCH

Page 27: Agile in Enterprise - TPSE 2013

ARCH

FEATURESPO

ARCH

DEV

Page 28: Agile in Enterprise - TPSE 2013

POARCHDE

V

Page 29: Agile in Enterprise - TPSE 2013
Page 30: Agile in Enterprise - TPSE 2013

ORGANIZATION TRANSFORMATION

Page 31: Agile in Enterprise - TPSE 2013

PRODUCT & ENGINEERING RESPONSIBILITY

PO DEV

1

2

3

Page 32: Agile in Enterprise - TPSE 2013

PRECISE GOAL

Page 33: Agile in Enterprise - TPSE 2013
Page 34: Agile in Enterprise - TPSE 2013

LEGACY CULTURE

Page 35: Agile in Enterprise - TPSE 2013
Page 36: Agile in Enterprise - TPSE 2013

REMOTE TEAM?

Page 37: Agile in Enterprise - TPSE 2013

– C. A. R. HOARE

“There are two ways of constructing a software design:

One way is to make it so simple that there are obviously no deficiencies, and

the other way is to make it so complicated that there are no obvious deficiencies.

The first method is far more difficult.”

Page 38: Agile in Enterprise - TPSE 2013

Make the wrongs obvious.

Page 39: Agile in Enterprise - TPSE 2013

MORE INFO?

HTTP://WWW.SCALEDAGILEFRAMEWORK.COM/

Page 40: Agile in Enterprise - TPSE 2013

Q&ATHANK YOU

Page 41: Agile in Enterprise - TPSE 2013

TRANSFORMATION TOOLBOX

Page 43: Agile in Enterprise - TPSE 2013

GOT AGILE?

Page 44: Agile in Enterprise - TPSE 2013

–MARY POPPENDIECK

“How long would it take your organization to deploy a change that involves just one

single line of code?”

organization

Page 45: Agile in Enterprise - TPSE 2013
Page 46: Agile in Enterprise - TPSE 2013