5 things bad developers say and what to do about it

from on 17.02.2015
Mad Developer

I talk to a lot of people (if the day is long enough) and so I get them to ask interesting questions like:

“What have you learned recently?”
“What is your top 1 goal for 2020?”

These questions and more leads us to interesting conversations about personal development and personal goals that a person has. Being a Scrum.org Trainer, I like to ask people questions especially related to software development so I ask them:

How well are your teams doing?” (and “How do you know?”)

What do you think is the content of the ‘Professional Scrum Developer’ class?“.

Especially to the last question I get this face

No clue

“No clue” from http://xenaandjonesgiflibrary.tumblr.com/post/42761898144

Scary thing is, most people don’t know what the content of our Professional Scrum developer class is.
For your convenience it’s written here on the PSD Subject Areas page. Go ahead and read it, I’ll wait here and prepare a little recap in the meantime:

The Professional Scrum Developer class
Turn your team of rockstars into a team that *rocks*

Since I got you to read that page and learn a little about the class (you can thank me later for that), I want to show you 5 sayings that should ring an alarm bell in your head.

  1. “I added a Refactoring Story for the next Cleanup Sprint”
  2. “The requirement #721 doesn’t meet the Definition of Ready”
  3. “I reviewed your code last night and deleted all of it since its crap”
  4. “I don’t write any tests since I am not a tester”
  5. “I couldn’t hire a Senior, so we hired 2 Juniors for this development team”

In the upcoming weeks I will publish a potential approach to these sayings and what to do about it.
Check back later for the link or follow me on Twitter @peitor.

What’s next?

Read more about Professionalism on How to become a Professional Scrum Developer and Team building and Scrum training combined.

BTW: Other Scrum Trainers got together and produced this nice little video that is worth watching.
#ProScrumDev: What does it mean to be a Professional Scrum Developer?

“We believe in delivering Value and we do it so fast that the customers don’t have time to change their mind”


What do you think is a professional developer?

If you are ready for a 3 day deep dive into professional software development
check out my class: Professional Scrum Developer.

Also read my follow-up post Can you find the 3 smells in “I added a Refactoring Story for the next Cleanup Sprint”?

See you soon!

Write a comment Daniel Tobler Cancel

Your e-mail address will not be published or shared with third parties. Fields marked with * are required.

5 comments for “5 things bad developers say and what to do about it

    1. Daniel Tobler

      Sarah, I think that there must be a lot more than only TDD. And very often I see programmers misunderstanding TDD as testing!
      For me, a professional programmer is one
      - where you can read and understand his code and designs immediately
      - who likes to exchanges his ideas with other professionals
      - who constantly learns from others and improved his skills
      (not complete listing)

      1. Peter Gfader Post author

        Hi Sarah and Dani
        Thanks for starting the conversation in this interesting direction.
        I think a Professional Developer should have 2 views. The inside technology view and the outside organisational view.

        Regarding the "outside organisational view", a Professional understands the organizational vision, priorities and business direction. The Professional Team will contribute to enterprise-wide success by optimizing the overall value stream.
        Yes, there is more than code 😉 and yes its fun to have a bigger impact and yes I think this is hard.