Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The developer’s manual: working with and managi...

The developer’s manual: working with and managing software developers

As a product owner, manager or designer you are supposed to understand what the business needs. But once you got that covered, you need to ork with software developers to create the product. Time for some cat herding. Time to figure out how to get the information to these software developers just right so they understand and create what you and the business wants. Communicating with Software Developers takes some special finess. The difference in technical understanding between software developers and their surroundings can make it hard to find common ground and clearly communicate intent and requirements. In this talk I will provide you with some practical tools to better help you navigate these troubled waters. And most of all, to get them to work with you in achieving the business goals.

More Decks by Jeroen Leenarts (AppForce1)

Other Decks in Technology

Transcript

  1. G E T S T R E A M .

    I O The Developer’s Manual Working with and managing software developers Slide of 243 2
  2. G E T S T R E A M .

    I O Jeroen Leenarts • iOS Developer Relations Lead • Podcast: AppForce1 • Book: Being a Lead Developer • Over 20 years of experience
  3. G E T S T R E A M .

    I O Why talk about Managing Developers?
  4. G E T S T R E A M .

    I O Stream Chat • The #1 Chat API for Custom Messaging Apps. • Add fast, real-time messaging to your application in days • Free trial available, no credit card required .N ET SD K too
  5. G E T S T R E A M .

    I O Trusted by many companies
  6. G E T S T R E A M .

    I O The Developer’s Manual Working with and managing software developers
  7. G E T S T R E A M .

    I O The Developer’s Manual Working against and destroying the lives of software developers Nightmare
  8. G E T S T R E A M .

    I O So let’s talk about 
 the worst things you can do 
 So you know what NOT to do
  9. G E T S T R E A M .

    I O Let’s start simple 
 Have too many slides for any presentation you give
  10. G E T S T R E A M .

    I O Welcome to my mind
  11. G E T S T R E A M .

    I O Productivity is key Quality is secondary Right?
  12. G E T S T R E A M .

    I O Micromanage everything •
  13. G E T S T R E A M .

    I O Why should you have to do all the boring work?
  14. G E T S T R E A M .

    I O Never be specific about team and individual goals
  15. G E T S T R E A M .

    I O Leading by example? Never!
  16. G E T S T R E A M .

    I O If I ask something, I am entitled to an answer RIGHT NOW •
  17. G E T S T R E A M .

    I O Any fad metric you can find, we are implementing that one
  18. G E T S T R E A M .

    I O A dev talking is a dev not coding
  19. G E T S T R E A M .

    I O Question any and all input a dev makes
  20. G E T S T R E A M .

    I O Assumption is the mother of all progress
  21. G E T S T R E A M .

    I O People in your team HAVE to agree to this principle
  22. G E T S T R E A M .

    I O Any argument can be won with: 
 “It is a matter of principle”
  23. G E T S T R E A M .

    I O If you don’t like something…
  24. G E T S T R E A M .

    I O Shit hits the fan? Time to bail!
  25. G E T S T R E A M .

    I O Be ruthless in the pursuit of your goals
  26. G E T S T R E A M .

    I O And punish immediatly when progress is lacking
  27. G E T S T R E A M .

    I O Be the elephant in the room
  28. G E T S T R E A M .

    I O Questions?
  29. G E T S T R E A M .

    I O Thank You.