TheManager’sGuide To Self

Managing Teams

SAVE our

Development Managers

#saveourdevmanagers

#saveourdevelopmentmanagersa@diaryofscrum

Meet the cast...

The DirectorsPurpose: Run companyHobbies: Big Deals and Big lunches

Our Dev Manager - VicentePurpose: Manage 5 Dev teamsHobbies: Filmmaking

The Scrum TeamPurpose: Build StuffHobbies: npm

Why is Vicente in despair?

Bemused – By what the developers and directors

consider important

Overwhelmed – Technology moving so fast

Insecure – Team autonomy takes away traditional role

What does Vicente think he should do?

Goal? Who? How?

To ensure development

teams meet the business need?

Make technical decisions

Impose Process

Take Responsibility

What?

MEETINGS & EMAILS!

What could Vicente do?

Goal? Who? How?

To ensure development

teams meet the business need?

Autonomy

Mastery

Purpose

What?

?

Autonomy

Boundaries

Alignment

Enquiry Creative Freedom

Mastery Growth Mindset

Busyness is Laziness

Challenge overcomes

complacency

LearningDelivery

PurposeReconnect

TeamsWith the

Business and Customers

Tell Stories

Measure Profit

Customer Visits

Focus on Value

A Common Language

Profit?

Profitable Development is when:

(customerValue/costToDevelopAndMaintain) > 1

PO’s Job

Devs Job

Clean Code

Continuous DeliveryHunt The

Value

Collaborate

MEASURE!MEASURE!

The Story So Far...

Manolo tells Vicente the budget has been cut and we must deliver all the features by Thursday

Scrummaster Dora tells Vicente that they are in the middle of rewrite from React to Angular2 and it’s taking longer than planned

The Scrum TeamPurpose: Build StuffHobbies: npm

What should Vicente do?

Vicente’s Plan

Task: Help Vicente - what happens next in the story?

Vicente’s Vision

A group of smart diverse people, passionate about their shared purpose, openly collaborating and continually experimenting creating truly profitable software.

My first actions for Vicente1.Run an Open Space Workshop with the teams to establish

boundaries of self management and how to keep the teams aligned (autonomy)

2.Invite the teams to form guilds with the purpose of improving expertise in key areas [Clean Code, UX, Javascript, Testing](mastery)

3.Take the devs out with Manolo to see his favourite customer and see how their software helps people (purpose)

Thank You!

@diaryofscrum www.leantomato.com

http://www.channel4.com/programmes/magnifica-70

Credits...