@rachelcdavies

CLOSING

WHO LEARNED SOMETHING NEW?

A FEW THINGS TO TRY

•  TDD, 4 Rules for Simple Design•  Connascence•  Listening to your types to improve flexibility•  Evaluation Kata • Not making classes public by default•  Architecturally Aligned Tests•  Consider user experience of your software

design•  Going to a SoCraTes unconference• Make software craftsmanship your ideology

and embark on a search for better ways

WE HOPE PEOPLE LIKE OUR IDEAS…

How do I do that?

Are we allowed to do that?

What if it goes wrong?

Might be hard

work. Do we have time?

THEY MAY HAVE A FEW WORRIES

GO CAREFULLY

MY BIGGEST TIP

PUT YOURSELF IN THEIR SHOES

CREATE AN EMPATHY MAP

•  Who is at the center?

•  What will they think?

•  What will they hear/see?

•  What will they say about the change?

ARE YOU REALLY READY FOR THIS?

INVEST TIME IN YOUR IDEA

CONDITIONS FOR LEARNING

MAKE IT ATTRACTIVE

MAKE IT EASY TO START

DECREASE DEPENDENCY

17

INVOLVE EVERYONE

GIVE UP YOUR SECRETS

INCLUDE SKEPTICS

LEARNINGS EVERYWHERE

SOURCES OF LEARNING

LEARN TOGETHER: PAIRING

LEARNING TOGETHER: MINI-MOB

RETROSPECTIVES: LEARNING FROM PAST EXPERIMENTS

CODING DOJOS: LEARNING TOGETHER

SHARING LEARNINGS: LIGHTNING TALKS

SHARING LEARNINGS: 20% TIME

LEARNING WITH: BUSINESS

SWAP TEAMS

SWAP ORGANISATIONS

OUR GLUE

CARE IT HAPPENS

TAKE TURNS

TRACKING & REFLECT

SO NOW WHAT?

BRING IT BACK HOME

•  Look for opportunities to help others learn

•  Invest time in learning more about something you heard about here

•  Share what you learned by giving a talk or blog

tech.unruly.co @rachelcdavies