Nenad Despić

Nenad Despic is a real Agile enthusiast, very passionate about Agile Software Development. He has more than 6 years of experience as a Project Manager, Delivery Manager and Scrum Master at companies Seavus, Levi9, Humanity and Puzzle Software.

Nenad strives to create a culture that values team success, promotes experimentation, supports stable team composition and rewards behavior over achievements. Nenad is also the owner of the Professional Scrum Master I certificate and he is an NLP Business Practitioner.

As the ex-professional basketball player, he enjoys working in a team and he loves to help teams to achieve maximum productivity through the stages of forming, storming, norming and performing.


Scrum Roles and Responsibilities Demystified

Are you currently a member of a Scrum team? Are you interested in learning more about the core philosophy of Scrum roles and how that can benefit your own business? Do you want to learn about responsibilities of each role and how they make things work? Well, you knocked at the right door!

When it comes to organizations embracing Scrum framework, one of the first things you have to understand is how actually Scrum roles differ from traditional project execution roles. Even though there are only three main roles in Scrum, they are not necessarily aligned with titles that are familiar to most of us. We’ll take it off by briefly defining each one of these three roles:

  • Product Owner – He is responsible for maximizing the value of the product and his task is to hold the vision for the product;
  • Scrum Master – the main task for this role is to help the team to use Scrum in the best way, in order to build the product;
  • Development Team – is the one that builds the product.

So, we can all agree that at first this looks fine, but when it comes to organizations that are not familiar with Scrum, we are facing a problem because all of this could make no sense to them. These roles may look like they are something like traditional Waterfall-based project management. In order to encourage comparison – the Product Owner is like the sponsor, right? Well, not quite… So, let’s take a closer look at the roles and their responsibilities.

Get ready! We are about to become even better in what we’re doing now!

Scrum on!