from divided to united - aligning technical and business teams

58
From Divided to United – Aligning Technical & Business Teams @dominicad ddegrandis.com @dominicad Dominica DeGrandis Director, Learning & Development www.leankit.com

Upload: leankit

Post on 14-Jan-2017

275 views

Category:

Software


0 download

TRANSCRIPT

Page 1: From Divided to United - Aligning Technical and Business Teams

@dominicad

From Divided to United – Aligning Technical & Business Teams

@dominicad ddegrandis.com

Dominica DeGrandis

Director, Learning& Development

www.leankit.com

Page 2: From Divided to United - Aligning Technical and Business Teams

@dominicad

Alignment: a position of agreement/alliance

Page 3: From Divided to United - Aligning Technical and Business Teams

@dominicad

improving alignment with clarity

Customers pleased?

Work transparent?

Team structure/measures?

Communication effective?

Page 4: From Divided to United - Aligning Technical and Business Teams

@dominicad

Nashville, TN August 2015

KatieSr. Product Marketing Manager

What do you do when you are unable to do what you were hired to do?

Page 5: From Divided to United - Aligning Technical and Business Teams

@dominicad

system limits + delayed delivery =

high demand on application impacts architecture andfeatures not delivered as expected, results in sad panda

Page 6: From Divided to United - Aligning Technical and Business Teams

@dominicad

a move closer to the core changes the game

Page 7: From Divided to United - Aligning Technical and Business Teams

Customers pleased?

Work transparent?

Team structure & measures ok?

Communication effective?

Page 8: From Divided to United - Aligning Technical and Business Teams

@dominicad

Customers determine business goals

After innovation of a new tool,what are thepriorities based on customer demand?

feature #1

feature #2

feature #3

Page 9: From Divided to United - Aligning Technical and Business Teams

@dominicad

capacity limits provoked priority convo

collective agreement by leadership reached after energetic discussion

✔ prioritize top 3 features

Page 10: From Divided to United - Aligning Technical and Business Teams

@dominicad

large customer affirms good experience

“you were a huge part of moving > 90% of our projects from waterfall to agile.”

Page 11: From Divided to United - Aligning Technical and Business Teams

@dominicad

Not everyone was happymore please• ux enhancements • new features • better integrations• faster loading

Page 12: From Divided to United - Aligning Technical and Business Teams

@dominicad

internal customers determine biz goals

Page 13: From Divided to United - Aligning Technical and Business Teams

@dominicad

marketing coordination cost is high

Will product feature be released in the timeframe

Marketing team expects?

Page 14: From Divided to United - Aligning Technical and Business Teams

@dominicad

the need for change was self-evident

Become more predictable

Allow Sales & Marketing to influence the roadmap

Page 15: From Divided to United - Aligning Technical and Business Teams

@dominicad

Ops team sacrifices go unoticed

Business exec investigates

new technology

promising zero impact on

tech teams, but guess

what happens?

Page 16: From Divided to United - Aligning Technical and Business Teams

@dominicad

Let’s talk about IT like it’s part of the business

Apologies only go so far. need actions to improve the mindset

Page 17: From Divided to United - Aligning Technical and Business Teams

Customers pleased?

Work transparent?

Team structure & measures ok?

Communication effective?

Page 18: From Divided to United - Aligning Technical and Business Teams

@dominicad

transparency is the necessary factor

Page 19: From Divided to United - Aligning Technical and Business Teams

donenext up

work-in-progresstheme

Page 20: From Divided to United - Aligning Technical and Business Teams
Page 21: From Divided to United - Aligning Technical and Business Teams

Optimize your workflow – Avoid starting new projects

until done with current project.

@dominicad

Page 22: From Divided to United - Aligning Technical and Business Teams

All team boards roll up to the roadmap

Each team has a team board where work is broken down into smaller chunks.

roadmap team board

Page 23: From Divided to United - Aligning Technical and Business Teams

From theme to working softwareA3the most valuable thing that fits within a sweep(≤ 5 weeks)

DIV: Deployed, Iterative, Value(≤ 5 days)

Task

DIV

Task Task

Task

A3

DIV

Task

DIV

Task Task

Task

Page 24: From Divided to United - Aligning Technical and Business Teams

Sequence of DIVs add up to A3 value DIVs deployed to prod

donein production

Page 25: From Divided to United - Aligning Technical and Business Teams

@dominicad

Ops Team board Current DIVs

Page 26: From Divided to United - Aligning Technical and Business Teams

MKT

MKTFIN

UXMKT

MKT

MKT

SLS DEVUXUX

SLS CSS

QAUX

DEVOPS SLS

SLS

1

2

3

4

6

5

DEV

DEV

OPS

How the A3 is populated

Cost of Delay?

Impact to users?What benefits who?

What does feature do?

Sustainability impact? fine print /misc?

Page 27: From Divided to United - Aligning Technical and Business Teams
Page 28: From Divided to United - Aligning Technical and Business Teams

What? So what? What now?

Demo DIV – Each squad has 5 min to demo their DIV*

*DIV – Deployable Iterative Value

Page 29: From Divided to United - Aligning Technical and Business Teams

Customers pleased?

Work transparent?

Team structure & measures ok?

Communication effective?

Page 30: From Divided to United - Aligning Technical and Business Teams

@dominicad

team organization & measures

Page 31: From Divided to United - Aligning Technical and Business Teams

Web DevCore DevOperations Mobile

Product Development team structure 2015

Tightly coupled

Page 32: From Divided to United - Aligning Technical and Business Teams

FSGD as a company wide thinking tool

Page 33: From Divided to United - Aligning Technical and Business Teams

Web2 - RocketWeb1 - GrootPlatform Ops

A3

Mobile

Product Development team structure 2016

Analytics

A3

A3

A3

A3

Automation & Tools

Business Enablement

A3

A3

Loosely coupled

Page 34: From Divided to United - Aligning Technical and Business Teams

@dominicad

conversation on number of

deployments metric

• What does it mean to deploy to prod?

• concerns with this measurement?• What was learned during

experiment?• What counts?• What doesn’t count?

Page 35: From Divided to United - Aligning Technical and Business Teams

@dominicad

Vanity metric?Does metric pass “so what?" test?

Does it: 1) Matter to my customer?2) Help me make a decision?

Page 36: From Divided to United - Aligning Technical and Business Teams

@dominicad

Number of deployments is easy to game?

Not so easy when the qualification of a deployment is that it must be related to a DIV*, on the roadmap.

DIV – Deployable Iterative Value

Page 37: From Divided to United - Aligning Technical and Business Teams

Team metric morphed to dept metric

Deployments this Sweep

Page 38: From Divided to United - Aligning Technical and Business Teams

@dominicad

Cycle Time metrics

Page 39: From Divided to United - Aligning Technical and Business Teams

@dominicad

Prod issues impacting cycle time on feature work

Page 40: From Divided to United - Aligning Technical and Business Teams

@dominicad

“Be approximately right instead of exactly wrong” ~John Tukey

Page 41: From Divided to United - Aligning Technical and Business Teams

Customers pleased?

Work transparent?

Team structure & measures ok?

Communication effective?

Page 42: From Divided to United - Aligning Technical and Business Teams

@dominicad

team communication protocols

Page 43: From Divided to United - Aligning Technical and Business Teams

@dominicad

Demo DIV feedback from Biz teams

* DIV - deployed iterative value

“I just want to learn about the things I can sell.

“I don’t want to listen to the technical stuff.”

Page 44: From Divided to United - Aligning Technical and Business Teams

@dominicad

Forum for discussing A3’s

A3 reviews

A3 Wall • all invited• context provided• user perspective• why’s addressed• goals explained• concerns heard• opinions aired• feedback

welcome

Page 45: From Divided to United - Aligning Technical and Business Teams

@dominicad http://leancoffee.org

Forum for retrospectives

Page 46: From Divided to United - Aligning Technical and Business Teams

@dominicad

Forum for raising & solving problems

Page 47: From Divided to United - Aligning Technical and Business Teams

@dominicad

What makes a great team?Google two year study results:

Who is on a team matters less than how team members interact.

The willingness to talk about errors is by far the most important factor for a team

Amy Edmonson TED talk: https://www.youtube.com/watch?v=LhoLuui9gX8

Page 48: From Divided to United - Aligning Technical and Business Teams

@dominicad

Alignment requires absolute clarity

Customers pleased?

Work transparent?

Team structure/measures?

Communication effective?

Page 49: From Divided to United - Aligning Technical and Business Teams

@dominicad

For the innovators

Generate ideas to increase transparency

Page 50: From Divided to United - Aligning Technical and Business Teams

@dominicad

For the doersInvestigate and study customer recommendation levels

Net Promoter Score = % promoters - detractors

Page 51: From Divided to United - Aligning Technical and Business Teams

@dominicad

For those with budgetsOffer teams the tools and training they need to do their job well.

Page 52: From Divided to United - Aligning Technical and Business Teams

@dominicad

For the influencersAcknowledge perceptions - then shift incentives towardtransparency,safe measures,& listening.

Wired article - The science of why no one agrees on the color of this dress

Page 53: From Divided to United - Aligning Technical and Business Teams

@dominicad www.ddegrandis.com Dominica DeGrandis www.leankit.com

Page 54: From Divided to United - Aligning Technical and Business Teams

Questions

@dominicad www.ddegrandis.com Dominica DeGrandis www.leankit.com

Page 55: From Divided to United - Aligning Technical and Business Teams

@dominicad

tech stack.net webservers and SQL DB ServersDocker hosts node servicesRedis for caching and volatile storageRabbit MQ for messaging hosted off linuxPuppet for managing infrastructure configuration automationTableau for Analytics

Page 56: From Divided to United - Aligning Technical and Business Teams

@dominicad

yes - relational data model limits, but does the way the

code consumes the data factor in?

strangler patternin play to tackle

architecture

Page 57: From Divided to United - Aligning Technical and Business Teams

@dominicad

metrics on individuals avoided

Page 58: From Divided to United - Aligning Technical and Business Teams