A Developers Primer to Managing Developers

A Developers Primer to Managing Developers

Session from DrupalCon Austin 2014 - Recording here: https://austin2014.drupal.org/session/developers-primer-managing-developers

7c49b77a97bebe0eabe6bb5cb2b66671?s=128

eojthebrave

June 04, 2014
Tweet

Transcript

  1. A Developers Primer to Managing Developers @joe ~$> echo “joe

    shindelar - @eojthebrave” php[tek] Chicago - 2015 https://joind.in/13753
  2. _ _ _ __| |_ __ _ _ _ __

    __ _| (_)_______ _ __ ___ ___ / _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \ | (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/ \__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___| |_| ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,, ,,, ,,, ,,, ,,,,,, ,,, ,,,, ,,,,, ,,,,,, ,,, ,,, ,,, ,,, ,,, ,,,,,,,,,, ,,,,,,,,,, ,,,,,,,,, ,,,,,, ,,, ,,, ,,, ,,, ,,, ,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,,,,,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,, ,,,, ,,, ,,, ,,,, ,,, ,,, ,,, ,,,,,,,,, ,,, ,,,, ,,, ,,, ,,, ,,,, ,,, ,,, ,,, ,,, ,,, ,,,,,,,,, ,,,,,,,,,, ,,, ,,, ,,,,,,,,,, ,, ,,,,,, ,,,,,,,, ,,,,, @joe ~$> echo “joe shindelar - @eojthebrave”
  3. I’m a developer

  4. Who are you?

  5. 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
  6. 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.
  7. Motivation

  8. I kick ass when I’m having fun.

  9. I kick ass when I’m having fun. challenged engaged learning

  10. Made with love. Just like mom’s $_COOKIE[‘peanut_butter’]

  11. Not all developers are created equal so know what each

    person on your team finds
 /[fun|challenging|awesome]/i
  12. What motivates /[you|me]/? Tell your PM, tell your boss. Tell

    your co-workers.
  13. “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
  14. _ _ _ __| |_ __ _ _ _ __

    __ _| (_)_______ _ __ ___ ___ / _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \ | (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/ \__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___| |_| • 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
  15. _ _ _ __| |_ __ _ _ _ __

    __ _| (_)_______ _ __ ___ ___ / _| | '__| | | | '_ \ / _ | | |_ / _ \ | '_ ' _ \ / _ \ | (_| | | | |_| | |_) | (_| | | |/ / __/_| | | | | | __/ \__._|_| \__._| .__/ \__,_|_|_/___\___(_)_| |_| |_|\___| |_| • 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
  16. 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.
  17. Project management methodologies sell books. They don’t solve problems.

  18. Process should be fluid

  19. A good process will motivate developers to do good work.

  20. Words Are Powerful <img src=“ ” />

  21. 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
  22. 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.
  23. Lessons / Gains • Better tickets. • Better understanding of

    what constitutes broken. • Increased understanding of overall project priorities. • I’m an adult.
  24. “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
  25. Oracle: Multiple Alternatives Program (MAP)

  26. Continuous Deployment I want others (and myself) to be able

    to benefit from the work I’m doing ASAP.
  27. It’s not
 always pretty. But we change it
 when we

    need to.
  28. 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
  29. 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?
  30. Process should be fluid

  31. Keep your documentation up-to-date

  32. Improving communication
 between us

  33. Don’t make me context switch.

  34. $_COOKIES!

  35. But seriously.
 Please don’t.

  36. Emergency Classification System @W5Coaching: https://twitter.com/W5Coaching/status/466309417592696833/photo/1

  37. The PM
 Abstraction Layer

  38. “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
  39. 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.
  40. Thanks @joe ~$> echo “joe shindelar - @eojthebrave” https://joind.in/13753