demystifying roles in scrum team - agile tour 2013 kaunas

Demystifying roles in Scrum team

Simonas RazminasDirector of Engineering

Scrum Team in Scrum Guide

Scrum recognizes no titles for Development Team members other than Developer

Roles

Roles are not important

Tasks are

Story about four people: Everybody, Somebody, Anybody, and Nobody.

There was an important job to be done and Everybody was asked to do it.Everybody was sure Somebody would do it.Anybody could have done it, but Nobody did it.Somebody got angry about that because it was Everybody's job.Everybody thought Anybody could do it, but Nobody realized that Everybody wouldn't do it.It ended up that Everybody blamed Somebody when actually Nobody asked Anybody.

Role: Architect

Architecture that enables Agility

Loosely coupled

Component shepherd

Which roles should be part of Scrum Team in Agile company?

Our highest priority is to satisfy the customerthrough early and continuous delivery

of valuable software.

Application Middlaware (App) DB Design Middleware

(Core)

DB Operations OS Virtual Compute

Storage Network

Departments by responsibility

DevOpsOr how IT Operations work with Developers

Summary

• Structure around business value chains• Discover what specialists should work

together• Tasks are important• Form T-Shaped specialists

(c) Classic Powerpoint Slide