Slide 1
Slide 1 text
A Developers Primer
to Managing Developers
@joe ~$> echo “joe shindelar - @eojthebrave”
php[tek] Chicago - 2015
https://joind.in/13753
Slide 2
Slide 2 text
_ _ _
__| |_ __ _ _ _ __ __ _| (_)_______ _ __ ___ ___
/ _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \
| (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/
\__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___|
|_|
,,, ,,, ,,, ,,, ,,,
,,, ,,, ,,, ,,, ,,,
,,, ,, ,,, ,,, ,,, ,,,,,, ,,, ,,,, ,,,,, ,,,,,,
,,, ,,, ,,, ,,, ,,, ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,, ,,,,,,
,,, ,,, ,,, ,,, ,,, ,, ,,, ,,, ,,, ,,, ,,, ,,,
,,, ,,, ,,, ,,, ,,, ,,,,,,,, ,,, ,,, ,,, ,,, ,,,
,,, ,,, ,,, ,,, ,,, ,,,, ,,, ,,, ,,,, ,,, ,,, ,,,
,,,,,,,,, ,,, ,,,, ,,, ,,, ,,, ,,,, ,,, ,,, ,,, ,,, ,,,
,,,,,,,,, ,,,,,,,,,, ,,, ,,, ,,,,,,,,,, ,, ,,,,,, ,,,,,,,, ,,,,,
@joe ~$> echo “joe shindelar - @eojthebrave”
Slide 3
Slide 3 text
I’m a developer
Slide 4
Slide 4 text
Who are you?
Slide 5
Slide 5 text
Here’s what we’re
going to talk about
1. Things that motivate developers.
2. Drupalize.Me process, changes, and
their impact on the team.
3. Some other sudo random tid-bits.
4. goto: 1
Slide 6
Slide 6 text
A ticket is the same as a
todo is the same as a task
is the same as an actionable
item I can work on.
Slide 7
Slide 7 text
Motivation
Slide 8
Slide 8 text
I kick ass when
I’m having fun.
Slide 9
Slide 9 text
I kick ass when
I’m having fun.
challenged
engaged
learning
Slide 10
Slide 10 text
Made with love.
Just like mom’s
$_COOKIE[‘peanut_butter’]
Slide 11
Slide 11 text
Not all developers are created
equal so know what each person
on your team finds
/[fun|challenging|awesome]/i
Slide 12
Slide 12 text
What motivates /[you|me]/?
Tell your PM, tell your boss.
Tell your co-workers.
Slide 13
Slide 13 text
“You can’t always get what
you want … but if you try
sometimes … you just might
find … you get what you need”
- Sir Michael Philip Jagger
Slide 14
Slide 14 text
_ _ _
__| |_ __ _ _ _ __ __ _| (_)_______ _ __ ___ ___
/ _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \
| (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/
\__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___|
|_|
• 2-6 person team with varying hours.
• Buckets of tickets organized by
milestones – really just a date.
• 2 week sprints.
• PM focused on assigning tickets
based on estimated hours to complete.
v 1.0
Slide 15
Slide 15 text
_ _ _
__| |_ __ _ _ _ __ __ _| (_)_______ _ __ ___ ___
/ _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \
| (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/
\__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___|
|_|
• 2-6 person team with varying hours.
• Buckets of tickets organized by goals.
• Developers choose any ticket they want
to work on.
• 1 week sprints.
• PM focuses on removing blockers and
aiding team communication.
v 1.2
Slide 16
Slide 16 text
Your process shouldn’t be
the same, but here are
some of the big wins we
encountered and more
importantly the lessons
they taught us.
Slide 17
Slide 17 text
Project management
methodologies sell
books. They don’t
solve problems.
Slide 18
Slide 18 text
Process should
be fluid
Slide 19
Slide 19 text
A good process will
motivate developers
to do good work.
Slide 20
Slide 20 text
Words Are Powerful
Slide 21
Slide 21 text
self::assignTask()
• Working on things that I can
self-identify as being
/[fun|challenging|engaging]/i*
• Higher satisfaction in completed work.
• Better overall communication about
who is doing what.
* most of the time
Slide 22
Slide 22 text
Roadmaps / Structured Chaos
• Define big picture goals.
• Provide a rallying point for
the team.
• Created by the team and
continuously maintained.
• Allow anyone to sandbox an
idea.
Slide 23
Slide 23 text
Lessons / Gains
• Better tickets.
• Better understanding of what
constitutes broken.
• Increased understanding of
overall project priorities.
• I’m an adult.
Slide 24
Slide 24 text
“Great teams, it turns out, begin
with a shared vision – a unified,
clearly articulated belief about
the software they're creating.”
- Paul Roberts paraphrasing Tim Mcarthy
Slide 25
Slide 25 text
Oracle: Multiple
Alternatives Program
(MAP)
Slide 26
Slide 26 text
Continuous Deployment
I want others (and myself) to be able to
benefit from the work I’m doing ASAP.
Slide 27
Slide 27 text
It’s not
always pretty.
But we change it
when we need to.
Slide 28
Slide 28 text
goto: 7
1. I want to do my best work.
2. I’m more productive when I work on
things I can self-identify as being a
good fit for me.
3. The more I know about the mission and
vision the better I’ll do at helping to
achieve it.
4. Process should be fluid.
5. I’m motivated by $_COOKIES
Slide 29
Slide 29 text
Document your process
POST: /api/v1/ask-question
- name (string): Name of person asking the question.
- query (string): The question you need answered.
- priority (int): 0-9 how soon do you need an answer?
Slide 30
Slide 30 text
Process should
be fluid
Slide 31
Slide 31 text
Keep your
documentation
up-to-date
Slide 32
Slide 32 text
Improving
communication
between us
Slide 33
Slide 33 text
Don’t make me
context switch.
Slide 34
Slide 34 text
$_COOKIES!
Slide 35
Slide 35 text
But seriously.
Please don’t.
Slide 36
Slide 36 text
Emergency Classification
System
@W5Coaching: https://twitter.com/W5Coaching/status/466309417592696833/photo/1
Slide 37
Slide 37 text
The PM
Abstraction
Layer
Slide 38
Slide 38 text
“Management,is about human
beings. Its task is to make
people capable of joint
performance, to make their
strengths effective and their
weaknesses irrelevant.”
- Peter Drucker
Slide 39
Slide 39 text
Recap
• Know what motivates your team
and yourself. Then leverage it.
• Recognize when your process
curbs motivation/morale.
• Allow your process to change and
document it when it does.
Slide 40
Slide 40 text
Thanks
@joe ~$> echo “joe shindelar - @eojthebrave”
https://joind.in/13753