8 skills every software engineer needs in a Scrum team

What does mindset actually mean? Is my product owner angry at me? How can I become a better software engineer? In this blog post, I want to share with you the skills for software engineers I value as a product owner. Probably there are many more valuable attitudes out there but I wanted to collect these to remind my team and myself about the things that are important.


Commitment is not about working extra hours. It is rather a good mixture of a “Can Do It” attitude and realistic estimates. Sometimes, to “give our best” is not enough. Don’t get me wrong on this! I love people that try hard but to recognize delays early we need to be more realistic than optimistic.

Robert C. Martin summarizes this very well in The Clean Coder. You can read his chapter on “How to say yes” here.


Although we try to prepare our stories as good as possible, clarification can be necessary. Take action if there is something to clarify. Try to contact a colleague and clarify your problem or find another way to get the answer you need.

Fail fast & cheap

Approach 1:

Break your work down to incremental steps e.g. according to your sprint goal. This helps to stay focussed and quickly get back to work after an interruption.

Approach 2:

Solve the most critical tasks first to identify problems early.

Readable Code

How much documentation is enough? Readable code is already a good start. In-code documentation for the most important API makes it easier for your peer-developers to understand the interfaces inside your product. Follow the KISS principle during the implementation. In addition, a SOLID software design makes writing clean code easier.


Keeping attention to repetitive tasks is important. DevOps is a huge buzzword today and every engineer should think about which things can be done faster or better by automation.


Technology is evolving fast. If you want to be a top developer, you need to stay updated. Using existing libraries makes life easier. (Comment: I don’t know any example, where it was a waste of time to learn about new stuff in your field.  Nevertheless, I really struggle to see the value in this. I only have faith it pays off well!) 

Speak up

If something is not going well, give feedback (at latest in the retro) We want to work agile so everybody should get the change to learn something (even the product owner ;-))


All these things will result in a high level of ownership. From my experience, treating software engineers just as coders is not the right approach. Apps easily get quite complex and therefore everybody in the team needs to feel responsible for the product. This reaches from reducing technical debt to making sure to provide value for the users


Do you wonder even more what a product owner is doing now?

Check out this video about what a product owner is doing. 🙂

If you want to read more about getting a crafty software engineer. I summarized five books for you that helped me to boost my career. Don’t miss out on them.

Click Here to Leave a Comment Below 4 comments
Agile is Dead - Pragmatic Dave Thomas - Software Has Bugs - June 2, 2018

[…] If you want to know which attitudes I value in a Scrum team, I want to recommend to you this blog post about 8 skills every software engineer needs. […]

5 books to create a software development mindset - Software Has Bugs - June 2, 2018

[…] to boos your technical as well as communication skills. If you are working in a Scrum team these eight skills will help as […]

How to create better understanding for user stories - Software Has Bugs - June 24, 2018

[…] you like this article? Checkout my posts about 8 skills every software engineer needs in a Scrum team to get a real team […]

7 Tips to Create a Product Roadmap from the Backlog - Software Has Bugs - July 28, 2018

[…] And if you liked this post, you should check out the other post on my blog. For example, there is one about 8 skills every software engineer needs in a Scrum team. […]


Leave a Reply: