Happier Teams Through Tools
-
Upload
laura-frank -
Category
Leadership & Management
-
view
34.845 -
download
0
Transcript of Happier Teams Through Tools
University of Warwick Study
• People treated with positive stimuli were, on average, 12% more productive than the control group
• People treated with negative stimuli were similarly less productive
• Still, hard to quantify what we consider ‘negative’ and ‘positive’
• tinyurl.com/warwickhappiness
Happiness Metrics• How do you feel?
• What are you doing right now?
• Do you have to be doing what you’re doing?
• How productive are you being right now?
• Do you want to do what you’re doing?
!
– DR DANIEL SGROI, UNIVERSITY OF WARWICK
“The driving force seems to be that happier workers use the time they
have more effectively, increasing the pace at which they can work without
sacrificing quality.”
This type of communication is ‘pull-based’. You can choose when to
consume it and it’s not as disruptive unless you allow it to be.
Meetings are good for complex discussion…
But they go against the pattern of persistent communication.
You MUST document the discussion and outcome of a meeting if you intend to have a team that can
function remotely.
Choose one mode of communication only
Try to make it as least disruptive as possible
Document the discussion and outcomes
!
– MELVIN CONWAY
“Organizations which design systems are constrained to produce designs
which are copies of the communication structures of these
organizations.”
If you have three engineering teams working on one piece of software, you’ll probably end up with three
pieces of software
In a SOA or microservices architecture pattern, each of the services is autonomous and can
operate independently
A service team can choose the correct tools — like languages, deployment
processes, and incident management systems — specific to their component
Dev Teamautomated
testsfeature
continuous deliverymaster
timed releaseproduction
review and merge
review and merge
push
Dev Teamautomated
tests
continuous delivery
timed release
feature
master
production
review and merge
review and merge
push
• The team shares responsibility for deployment, and each engineer is empowered to control the flow of his or her code into production
• Your customers are always getting the best product you have to offer
A P0 incident is urgent, and communication for this incident
requires interrupting people in order to accomplish the task
!
– NICO APPEL, TIGHTOPS.COM
“You pay for urgency with interruption; and you should
understand whether or not you are getting a good deal.”
Incident 💥
PagerDuty wakes me up 🚨
I wake my boss up, because I don’t have access to production logs without his sign off 💩
My boss opens a ticket with the NOC 😫
NOC gives me temporary log/deploy access ✅
I fix stuff 🐛
I merge and manually trigger Jenkins 👔 tasks to deploy
Verification 🏆
PagerDuty wakes me up 🚨
I fix stuff 🐛
I merge my fix and it deploys automatically 🔁
Verification 🏆
Incident 💥
Sleep 😴
Post-mortem 📖
!
– CAPTAIN OBVIOUS
“If an engineer is on call, make sure he or she has access to logs, metrics, and the ability to deploy new code to
production.”