my agile suitcase at agile 2013 in nashville

Post on 08-May-2015

7.034 Views

Category:

Business

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

Slides of session at Agile 2013 conference in Nashville. It was facilitated by Martin Heider with Pecha Kuchas of Arlo Belshee, Johanna Rothman, Michael Sahota, David Hussman & Bernd Schiffer presenting their Agile Suitcases they would bring to waterfall island.

TRANSCRIPT

My Agile Suitcase

#Agile2013 #MyAgileSuitcase

Pecha Kucha Agile 2013, Nashville

Agile Enthusiast, Consultant,

Coach & Trainer Community Groomer

Germany

holiday Your

one call

a new project

Your team http://www.flickr.com/photos/accolite/2927750264

Your last project

A message

Ask for help

Help is on the way

"My suitcase is

filled with the

things that I

really wish

others would

start packing for

themselves."

@arlobelshee

„Mindset

matters “

@johannarothman

„The Agile

Community is

so beautiful and

giving that I

want to share

what I have

learned."

@michael_sahota

„Sharing our

experiences and

our perspectives

is essential to

growing our

collective

knowledge."

@davidhussman

„I want to

practice what

I preach."

@berndschiffer

20 x 20 = 6´40

Applause Your

Feedback #Agile2013 #MyAgileSuitcase

Your

"My suitcase is

filled with the

things that I

really wish

others would

start packing for

themselves."

@arlobelshee

The typical agile suitcase

Stories

Adaptive planning

Complaint-fest retrospectives

Visible status

Stand-ups

Visible upcoming work

Estimation

My agile suitcase

Stuff I need

Stuff others need but

always leave at home

My agile suitcase

Plan,

Status,

Stories,

Burn-up,

Stand-up

Code well:

Work Tiny. Prove it. Get Done.

Learn and improve discipline.

Work together. Win together.

Make changes together.

Work tiny

Work tiny – spiral in reverse

Work tiny – impressive results eventually

Check in

Ship live

Validate business impact

Prove it

Traditional or 1 star Agile 2+ star Agile

Dev’s job • deliver software

Write ~8 bugs / man-day

Dev’s job • Deliver software • Demonstrate software does

what devs expect

Tools • Mechanized refactoring • Small steps, with reverting • Test first • Automated developer testing • Design in units • Design for testability

Write ~1 bug / 80 man-days

No bugs!

Low cost changes => Emergent Design

“Hey, we could …”

The simplest thing that could possibly work

You aren’t gonna need it

Pain No Pain

Low risk changes => Learn in the market

Get done

April May June

Product A

Product B

Product C

Revenue:

July

A+B+C

April May June

Product A Product B Product C

Revenue:

July

A+B+C A A+B

VS

Learn informally

Learn constantly

Improve together

Be trustworthy – be predictable

Be trustworthy – consider others

Do the work together

Work tiny

Prove it

Get done

Learn constantly

Improve together

Be trustworthy

Win together

My packing list generator

Pair or mob, 100%

Design small units

100% mechanized refactoring

Tests are specs; write them first

Finish and prove each step before

starting the next

1 process change / week (minimum)

Decentralize all decisions

Involve people directly

My current packing list

Applause

„Mindset

matters “

@johannarothman

My Agile Suitcase

Johanna Rothman

New: Hiring Geeks That Fit

@johannarothman

www.jrothman.com

jr@jrothman.com

781-641-4046

© 2013 Johanna Rothman 47

© 2013 Johanna Rothman 48

© 2013 Johanna Rothman 49

© 2013 Johanna Rothman 50

© 2013 Johanna Rothman 51

© 2013 Johanna Rothman 52

© 2013 Johanna Rothman 53

© 2013 Johanna Rothman 54

© 2013 Johanna Rothman 55

© 2013 Johanna Rothman 56

© 2013 Johanna Rothman 57

© 2013 Johanna Rothman 58

© 2013 Johanna Rothman 59

© 2013 Johanna Rothman 60

© 2013 Johanna Rothman 61

© 2013 Johanna Rothman 62

© 2013 Johanna Rothman 63

© 2013 Johanna Rothman 64

© 2013 Johanna Rothman 65

© 2013 Johanna Rothman 66

© 2013 Johanna Rothman 67

Want more?

Sign up for the Pragmatic

Manager newsletter, www.jrothman.com/pragmaticmanager

1

Your

Agile Suitcase

Define your Agile Suitcase by packing

your favorite 5 elements on post-its

Your Agile Suitcases of Pairs

1

„The Agile

Community is

so beautiful and

giving that I

want to share

what I have

learned."

@michael_sahota

My Agile Suitcase

@MichaelSahota michael.sahota@agilitrix.com

Big Open Toolbox

Scrum

Lean

Kanban

Systems Thinking

Adaptive Action

Most Value from Mindset/Culture, not Practices

~20% Benefit ~3X Benefit •Ability to manage changing priorities

•Improved Visibility

•Increased Productivity

•Improved Quality

•Reduced Risk

•Customer Delight

•Joy at work

•Engagement

•Innovation, Creativity

•Continuous Learning

Change is Within a Scope

Culture Provides Greatest Leverage

Supplication

Reveal Patterns

Value Stream Mapping

Innovation Games®

Strategic Play®

Supplication Let Them Choose (Let go of Outcome)

Partnership (50/50)

See People As Valuable

Love Myself

Courage & Vulnerability

Call for Help

Temenos Lab

Full Session - Wed. Aug 7 @10:45AM

Oneness Meditation

“Be the Change you want to See in the World”

- Mahatma Gandhi

• Photo Credits

• Seamless Grungy Teal Pattern -

http://www.flickr.com/photos/webtreatsetc/

• Toolbox - http://www.flickr.com/photos/arrrrt/

• Neo/Matrix Red Pill, Blue Pill, used without permission

• Handshake - http://www.flickr.com/photos/62751770@N05/

• Sleeping Homeless Person - http://www.flickr.com/photos/fotografar/

• Vulnerability Statue - http://www.flickr.com/photos/johnia/

• Phone Booth - http://www.flickr.com/photos/jarodcarruthers/

• Morraine Lake - http://commons.wikimedia.org/wiki/User:Gorgo

• World - http://www.flickr.com/photos/donkeyhotey/

Applause Your

Define your common Agile Suitcase by • Introducing each others suitcase • Packing new suitcase(keep family tree)

Your Agile Suitcases of two Pairs

1 1 1 + =

„Sharing our

experiences and

our perspectives

is essential to

growing our

collective

knowledge."

@davidhussman

Cutting an Agile Groove

David Hussman - DevJam

Empathy

What’s it like on Waterfall Island?

Listening

“We have two ears and one mouth so we

listen twice as much as we speak” - Epictetus

Questioning

Dude’s Law: Value = Why / How

V= W H

V= W H

How much process is enough?

Test Driven

Refactoring

User Stories

Acceptance Tests

Sprints

Product Backlogs

Sprint Reviews

Sprint Backlog Continuous Integration

Evolutionary Design Burndown Burnup Velocity

Information Radiators

Iterations Releases

Personas Kanban

Kaizen

Common Workspace

Cross Functional Teams

Daily Scrum

Retrospectives

Iteration 0

Chartering

Collective Ownership

WIP

Pivot

MVP

Planning Poker

Story Points

Technical Debt

Story Maps Domain Driven Design

Don’t tell me what the book says Walter,

what practices do we really need man?

Don’t assume you know where you’re going

Getting Ready

Getting Productive

Staying Productive

Don’t assume you know how to get there

Getting Ready: Discover Product

Who needs what and why?

Getting Ready: Get to Know the People

Who’s in the band?

Getting Ready: Uncover the Eco-System

Tools and technologies?

Design areas? Collaboration spaces?

Getting Ready: Make Remote Connections

Who are “they” and what are their names?

Raj

Sam

Sue

Ivan

Etta

Adopt Humanely with Intent

Avoid “Scrum buts” and other prescriptions

Getting Productive: Learn from Delivery

“Done” means more than “demod”

Getting Productive: Monitor Tech Debt

What is your next best investment?

Getting Productive: Invest Wisely

Getting Productive: Continuously Learn

Don’t wait to reflect and adapt

Staying Productive: Use Humor

Don’t mistake crowds for collaboration

Staying Productive: Less is More

Staying Productive: Keep Process Lean

Readiness over process (or procedure)

Epistemic Arrogance: “The difference between

what you know and what you think you know”

Staying Productive: Avoid Arrogance

Staying Productive: Frame and Reframe

Building for the future Building to adapt

Talking about code Talking about tests

Late integration Continuous Deployment

What’s required? What’s needed?

How many hours? How much product?

How much cost? How much opportunity?

(from) Last Millennia (to) This Millennia

How big? Too big?

Learning to estimate Learning from estimates

Completing work Validating value delivered

Practice empirical skepticism

Never stop questioning and learning!

Define your common Agile Suitcase by • Introducing each others suitcase • Packing new suitcase(keep family tree)

Your Agile Suitcases of two groups of four

1 1 1 + =

„… because I

want to practice

what I preached."

@berndschiffer

My Agile suitcase 05/08/2013 Agile Conference Nashville

Bernd Schiffer

http://i.imgur.com/rE0Za68.jpg

http://en.wikipedia.org/wiki/File:Australian_Coat_of_Arms.png

One group presents their last suitcase • Others check for same in their suitcase • Count different items

Your Agile Suitcases Diversity

Your Agile Suitcases Gallery of „family trees“

1 1 1

1 1

1

1 1 1 1

1 1

1

1 1 1 1

1 1

1

1

Feedback #Agile2013 #MyAgileSuitcase

Your

Keep & Try

top related