LEMİ ORHAN ERGİNManaging Partner & Master Software Craftsman, ACM

thinking about motivation of developers

GUIDETO THE GALAXY

HAPPY DEVELOPER’S

the talk will be about developers who really love their professioncaution

is a common problem for everyoneMotivation

zz

z

z zz

for me too

improveI cannot myself

Nothing excited Monotonous

Hard to focus No innovation

Nothing to learn

Feel alone work for long hours

Cannot get help Blame rules

No teamwork

workI cannot with people

No trust Arguing via emails

No care for feelings I am an headcount Monitored closely

controlledI am like a kid

I FEELunmotivated

exhaustedtired

hopelesssad

angrylazy

depressedstressed

alone

Similar?

unmotivated

I want tosucceed

feel valuabletrust

be trustedbe in decisionsfeel improved

focusedbe efficient

learnfeel proud

only passionate, disciplined and motivated people

can continuously deliver well-crafted software and value

passionate disciplined motivated

passionatedisciplinedmotivated

motivationAll you have your own preference for

motivationAcceptance Curiosity Power Honor Social Contact / Relatedness Idealism Status Independence / Autonomy Order Competencein

stri

nct

motivation

extr

inct

“We zombify people by using wrong practices”Niels Pflaeging Management Exorcist

from his talk at Agile Turkey Summit 2014

managersare not responsible for our motivation

managersare not responsible for our motivation ??????

managers have to build an environment that improves motivation and happiness

humanwe have to build and use

centricpractices and processes

Lean

focus on the human side of our work life to build better products

AgilityCraftsmanship

LeanCraftsmanship

Agility

Trust Honesty

Teamwork Self-Organization Empowered Teams

Continuous Improvement Retrospecting Regularly

Sustainable Pace Proxy to InterRuptions

Face to face Communication Collaboration

Efficiency Removing Waste

Pairing courage Professionalism No Blame Rule Limiting multi-tasking Mentorship Fast Feedback Loops Community of Professionals Code of Ethics Collective Ownership Practicing to Master Five Whys Slack Time

mindsetmakes the difference, not the tools

mindsetpractices and characteristics of the

improving motivation and culture

mindset

be aware of god complexityTrial and error might be the best way most of the time

Your “that’s just simple” solutions might not be realistic in real complex world

leave your egoyou have to be ready for being motivated

“Mix of youth and a bit of experience can easily lead to arrogance”

Sandro Mancuso Author of “The Software Craftsman”

abandon learnt despairsnever work on a place where you have no hope

innovation is about culturecontinuously doing the same thing does not mean doing it in the same way

provide safe environment for trial and errors do experiments, do it a lot

stop producing messlearn how to build high quality software

learn your professionsoftware development might be something different that you think

tools & rituals are not what concepts are all about

stop micro managingchecking social media improves productivity

trust by defaultno matter how senior or experienced your team is

set goals to be proud ofcreativity directly bounds to purpose and constraints you have

watch conference videosspend 2 hours every week for watching conference videos

define mastery goalsstop pushing performance goals for difficult problems

Dr. Heidi Grant HalvorsonFrom the book “Succeed: How We Can Reach Our Goals”

http://amzn.com/0452297710

be communicator & fightersspend time to remove impediments, communicate to learn the complexity

Insanity: doing the same thing over and over again and expecting different results.

Albert Einstein

foster collaborationorganize brown bag sessions, work with foremen

pair programming code reviews

mob programming lunch and learn sessions proof of concept projects

enlightement talks technical backlog items

community of professionals

invest in yourselfit’s your profession, own it!

give back to communitieswhat you get is what you give

WYG WYG

these communities do not have to be public ones

manage your branddefine target audience

write blog posts use social media effectively

give back to the community attend conferences

contribute to open source

. .

don’t be the guy in the corner

deliver positive feedbackgive special importance to thank people

ask responsiblity of what you create

don’t act as if you do, ask for re

design architecture code testing deployment monitoring

pay for a better placestop cutting costs of the essentials of our profession

confotable chairs at least 1 monitor

large enough desk fresh air

silent area day light

licenses for your tools

document for the next developer Commit messages

Branch names Commit graph

Production code Test code

Flow diagrams API documentation

Release notes Code review comments

define definition of fundefine nerdy rituals, feed your sense of humor, enjoy your job

never work for badbehave unethical treat people as resources treat you as a dummy wheel insensible to your feelings ill intensioned you lost your hope

Blizzard developers John Lagrave, Ion Hazzikostas, David Kim, and Kaeo Milker are signing autographs at the Blizzard booth at Developer Signing Sessions!

gamescon2012

work with correct people

ENJOYremember whatever you do do not forget to

https://www.flickr.com/photos/fraserspeirs/3394902061Joe O'Brien and Jim Weirich while doing ruby code review

Credits

Icons made by FlatIconhttp://www.flaticon.com/authors/freepik

CC BY 3.0 http://creativecommons.org/licenses/by/3.0

CC Zero http://creativecommons.org/publicdomain/zero/1.0

Images made by Gratisography.com, Ryan McGuirehttp://www.gratisography.com

Lemİ orhan ergİnagile software craftsman

/lemiorhanhttps://www.linkedin.com/in/lemiorhan

@lemiorhanhttps://twitter.com/lemiorhan

/lemiorhanhttp://www.slideshare.net/lemiorhan

lemiorhanergin.comOfficial site having personal information

www.acm-software.com