Top Banner
www.rallydev.com @zachnies ©2013 Responding to Change Zach Nies – Chief Technologist
84

Responding to Change

Feb 23, 2016

Download

Documents

hedva

Responding to Change. Zach Nies – Chief Technologist. Chief Technologist Rally Software. Zach Nies. Faculty University of Colorado at Boulder . @ zachnies. The biggest risk you face is changing. Responing to market shifts. An example…. Local consumer data company. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Responding to Change

www.rallydev.com @zachnies ©2013

Responding to Change

Zach Nies – Chief Technologist

Page 2: Responding to Change

www.rallydev.com @zachnies ©2013

Zach Nies

@zachnies

Chief TechnologistRally Software

FacultyUniversity of Colorado at

Boulder

Page 3: Responding to Change

www.rallydev.com @zachnies ©2013

The biggest risk you face

is changing

Page 4: Responding to Change

www.rallydev.com @zachnies ©2013

Responing tomarket shifts

Page 5: Responding to Change

www.rallydev.com @zachnies ©2013

An example…

Page 6: Responding to Change

www.rallydev.com @zachnies ©2013

Local consumer data company

Page 7: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

We have 80% market share

Page 8: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

We needa mobile app

Page 9: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Mobile app specification

begins

Page 10: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Startup competitor ships 1.0

Page 11: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Startup competitor ships 1.1

Page 12: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Appdefined

Page 13: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Startup competitor ships 1.2

Page 14: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

Mobile app ships

Page 15: Responding to Change

www.rallydev.com @zachnies ©2013

Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 20140%

10%

20%

30%

40%

50%

60%

70%

80%

90%

Desktop Mobile

Mar

ket S

hare

We forever lost half our market share in one year

Page 16: Responding to Change

www.rallydev.com @zachnies ©2013

Gut wrenching

Page 17: Responding to Change

www.rallydev.com @zachnies ©2013

What’sgoing on here?

Page 18: Responding to Change

www.rallydev.com @zachnies ©2013

Time neededto change

market expectations

Page 19: Responding to Change

www.rallydev.com @zachnies ©2013

Some examples…

Page 20: Responding to Change

www.rallydev.com @zachnies ©2013

1984

Page 21: Responding to Change

www.rallydev.com @zachnies ©2013

2006

Page 22: Responding to Change

www.rallydev.com @zachnies ©2013

About 20 years

Page 23: Responding to Change

www.rallydev.com @zachnies ©2013

2001

Page 24: Responding to Change

www.rallydev.com @zachnies ©2013

2006

Page 25: Responding to Change

www.rallydev.com @zachnies ©2013

5 years

Page 26: Responding to Change

www.rallydev.com @zachnies ©2013

2007

Page 27: Responding to Change

www.rallydev.com @zachnies ©2013

2010

Page 28: Responding to Change

www.rallydev.com @zachnies ©2013

3 years

Page 29: Responding to Change

www.rallydev.com @zachnies ©2013

2010

Page 30: Responding to Change

www.rallydev.com @zachnies ©2013

2012

Page 31: Responding to Change

www.rallydev.com @zachnies ©2013

2 years

Page 32: Responding to Change

www.rallydev.com @zachnies ©2013

1979

Page 33: Responding to Change

www.rallydev.com @zachnies ©2013

1989

Page 34: Responding to Change

www.rallydev.com @zachnies ©2013

10 years

Page 35: Responding to Change

www.rallydev.com @zachnies ©2013

5 years

Page 36: Responding to Change

www.rallydev.com @zachnies ©2013

2.5 years

Page 37: Responding to Change

www.rallydev.com @zachnies ©2013

1.5 years

Page 38: Responding to Change

www.rallydev.com @zachnies ©2013http://hbr.org/2013/03/big-bang-disruption/

Page 39: Responding to Change

www.rallydev.com @zachnies ©2013

Huge market shifts can happen

in a few years

Page 40: Responding to Change

www.rallydev.com @zachnies ©2013

Are youAgile enough

to balance

Page 41: Responding to Change

www.rallydev.com @zachnies ©2013

operating the businessand

responding to change?

Page 42: Responding to Change

www.rallydev.com @zachnies ©2013

Lean Thinking

Agile Execution

Page 43: Responding to Change

www.rallydev.com @zachnies ©2013

Balanceexploration and

execution

Page 44: Responding to Change

www.rallydev.com @zachnies ©2013

Typical approach

Page 45: Responding to Change

www.rallydev.com @zachnies ©2013http://www.flickr.com/photos/brostad/3461277605

Page 46: Responding to Change

www.rallydev.com @zachnies ©2013

Page 47: Responding to Change

www.rallydev.com @zachnies ©2013

Assumes:Certainty is high

Goal: Maximize individual efficiency

Page 48: Responding to Change

www.rallydev.com @zachnies ©2013

100 years later

Page 49: Responding to Change

www.rallydev.com @zachnies ©2013

Status QuoBudgets

ComprehensiveAnalysis

DetailedPlans

WaterfallExecution

Page 50: Responding to Change

www.rallydev.com @zachnies ©2013

Works when:

Certainty is high

Page 51: Responding to Change

www.rallydev.com @zachnies ©2013

Leads to

Page 52: Responding to Change

www.rallydev.com @zachnies ©2013

Little flexibility

Page 53: Responding to Change

www.rallydev.com @zachnies ©2013

Unmanageable demand

Page 54: Responding to Change

www.rallydev.com @zachnies ©2013

Poor visibility

Page 55: Responding to Change

www.rallydev.com @zachnies ©2013

Seems like every project is late

Page 56: Responding to Change

www.rallydev.com @zachnies ©2013

Trust issues

Page 57: Responding to Change

www.rallydev.com @zachnies ©2013

Poor quality

Page 58: Responding to Change

www.rallydev.com @zachnies ©2013

Constant interruptions

Page 59: Responding to Change

www.rallydev.com @zachnies ©2013

Little improvement

Page 60: Responding to Change

www.rallydev.com @zachnies ©2013http://www.flickr.com/photos/oregondot/4132135156

Page 61: Responding to Change

www.rallydev.com @zachnies ©2013

Need an approach that

Page 62: Responding to Change

www.rallydev.com @zachnies ©2013

Assumes:Uncertainty exists

Goal:Maximize value delivery

Page 63: Responding to Change

www.rallydev.com @zachnies ©2013

Make the shift to Agile

Page 64: Responding to Change

www.rallydev.com @zachnies ©2013

AdaptiveSteering

DisciplinedExploration

EmpiricalLearning

AgileExecution

Page 65: Responding to Change

www.rallydev.com @zachnies ©2013

How canRally help?

Page 66: Responding to Change

www.rallydev.com @zachnies ©2013

Implement a scaled Agile process to connect strategyand execution.

Provide an Agile Lifecycle Management platform to act as “single source of truth” for all artifacts.

Be an enterprise Agile partner to guide you through this transformation, creating an Agile business.

The Whole Agile Solution

Page 67: Responding to Change

www.rallydev.com @zachnies ©2013

Responsiveto change

Page 68: Responding to Change

www.rallydev.com @zachnies ©2013

InvestmentCategories

Initiatives

Features

StoryHierarchies

Tasks

Align strategy and execution

Page 69: Responding to Change

www.rallydev.com @zachnies ©2013

Balancesupply and demand

Page 70: Responding to Change

www.rallydev.com @zachnies ©2013

Portfolio ViewClearly communicate the status of your portfolio

Page 71: Responding to Change

www.rallydev.com @zachnies ©2013

Gain visibility

Page 72: Responding to Change

www.rallydev.com @zachnies ©2013

Program ViewMap team level execution to strategic initiatives and see progress in real-time

Page 73: Responding to Change

www.rallydev.com @zachnies ©2013

Steer projects

Page 74: Responding to Change

www.rallydev.com @zachnies ©2013

Release ViewSee release progress and respond in real-time

Page 75: Responding to Change

www.rallydev.com @zachnies ©2013

Build trust

Page 76: Responding to Change

www.rallydev.com @zachnies ©2013

Team View

Page 77: Responding to Change

www.rallydev.com @zachnies ©2013

Improve quality

Page 78: Responding to Change

www.rallydev.com @zachnies ©2013

Delivery Team View

Page 79: Responding to Change

www.rallydev.com @zachnies ©2013

Keep work flowing

Page 80: Responding to Change

www.rallydev.com @zachnies ©2013

Product Owner View

Page 81: Responding to Change

www.rallydev.com @zachnies ©2013

Benchmarked improvement

Page 82: Responding to Change

www.rallydev.com @zachnies ©2013

Paper with research findings so far:http://rallydev.com/agilemetrics

Software Development Performance Index (SDPI)

Page 83: Responding to Change

www.rallydev.com @zachnies ©2013

Complete Solution for Your Agile Business

Begin Your

TransformationExpand

CollaborationRun

DevelopmentSteer

Strategy

Page 84: Responding to Change

www.rallydev.com @zachnies ©2013

Talk to us abouthow we can help you.