happy teams make better code

62
Happy Teams Make Better Code Matt Campbell [email protected] @beardedcoder

Upload: matthew-campbell-oct

Post on 06-Jan-2017

68 views

Category:

Engineering


1 download

TRANSCRIPT

Page 1: Happy Teams Make Better Code

Happy Teams Make Better CodeMatt Campbell

[email protected]@beardedcoder

Page 2: Happy Teams Make Better Code

Matt Campbell

Senior Development Manager with D2L

Leading project to achieve proper web-scale in AWS

Previously lead move to monthly deployments

Pssst … we’re hiring and we have an office in Vancouver

Page 3: Happy Teams Make Better Code
Page 4: Happy Teams Make Better Code

Actual D2L Workspace

Page 5: Happy Teams Make Better Code

(Hopefully) Not Actual D2L Employees

Page 6: Happy Teams Make Better Code
Page 7: Happy Teams Make Better Code
Page 8: Happy Teams Make Better Code

Software development is mostly problem solving, therefore we want our teams solving problems.

Page 9: Happy Teams Make Better Code

KnowledgeSkillsCreativityExperimentation

Page 10: Happy Teams Make Better Code

KnowledgeSkillsCreativityExperimentation

Page 11: Happy Teams Make Better Code

KnowledgeSkillsCreativityExperimentation

Page 12: Happy Teams Make Better Code

KnowledgeSkillsCreativityExperimentation

Page 13: Happy Teams Make Better Code

Software development is mostly problem solving, therefore we want our teams solving problems.

Problem solving requires knowledge, skills, creativity, and experimentation.

Page 14: Happy Teams Make Better Code
Page 15: Happy Teams Make Better Code
Page 16: Happy Teams Make Better Code

Ideas for Slack Time

• Reading

• Book clubs

• Watching webinars

• Attending conferences

• Hacking

• Taking courses

• Learn a new language

Page 17: Happy Teams Make Better Code
Page 18: Happy Teams Make Better Code

Software development is mostly problem solving, therefore we want our teams solving problems.

Problem solving requires knowledge, skills, creativity, and experimentation.

Page 19: Happy Teams Make Better Code
Page 20: Happy Teams Make Better Code
Page 21: Happy Teams Make Better Code
Page 22: Happy Teams Make Better Code
Page 23: Happy Teams Make Better Code
Page 24: Happy Teams Make Better Code
Page 25: Happy Teams Make Better Code
Page 26: Happy Teams Make Better Code
Page 27: Happy Teams Make Better Code
Page 28: Happy Teams Make Better Code
Page 29: Happy Teams Make Better Code
Page 30: Happy Teams Make Better Code
Page 31: Happy Teams Make Better Code
Page 32: Happy Teams Make Better Code
Page 33: Happy Teams Make Better Code
Page 34: Happy Teams Make Better Code

http://www.brickprinter.com/

Page 35: Happy Teams Make Better Code
Page 36: Happy Teams Make Better Code
Page 37: Happy Teams Make Better Code
Page 38: Happy Teams Make Better Code
Page 39: Happy Teams Make Better Code
Page 40: Happy Teams Make Better Code
Page 41: Happy Teams Make Better Code

Alignment

Autonomy

Page 42: Happy Teams Make Better Code

Alignm

ent

Autonomy

Page 43: Happy Teams Make Better Code

WHAT

WHY

HOW

Page 44: Happy Teams Make Better Code

We’re working on X because we think it is going to give impact Y which benefits the project/company because of Z.

We’re done when …

Page 45: Happy Teams Make Better Code
Page 46: Happy Teams Make Better Code

Software development is mostly problem solving, therefore we want our teams solving problems.

Problem solving requires knowledge, skills, creativity, and experimentation.

Creativity requires constraints and alignment to be purposeful.

People require safety, a sense of belonging, and esteem to be able to be Creative.

Page 47: Happy Teams Make Better Code
Page 48: Happy Teams Make Better Code
Page 49: Happy Teams Make Better Code
Page 50: Happy Teams Make Better Code
Page 51: Happy Teams Make Better Code
Page 52: Happy Teams Make Better Code
Page 53: Happy Teams Make Better Code

Software development is mostly problem solving, therefore we want our teams solving problems.

Problem solving requires knowledge, skills, creativity, and experimentation.

Creativity requires constraints and alignment to be purposeful.

People require safety, a sense of belonging, and esteem to be able to be Creative.

Experimentation requires embracing failure. Failure can’t be a bad word.

Page 54: Happy Teams Make Better Code
Page 55: Happy Teams Make Better Code
Page 56: Happy Teams Make Better Code
Page 57: Happy Teams Make Better Code

Things you can change

Page 58: Happy Teams Make Better Code

Things you can influence

Page 59: Happy Teams Make Better Code

Things you can neither change nor influence

Page 60: Happy Teams Make Better Code

Things you can change

Page 61: Happy Teams Make Better Code

Questions?

Page 62: Happy Teams Make Better Code

Happy Teams Make Better CodeMatt Campbell

[email protected]@beardedcoder