The document explores the roles within a Scrum team, emphasizing that Scrum recognizes no specific titles other than 'developer.' It uses a parable to illustrate accountability in teamwork and stresses the importance of clear responsibilities to avoid confusion. Additionally, it highlights the priority of customer satisfaction through the continuous delivery of valuable software and calls for collaboration among specialists in an agile environment.

1. Demystifying roles in Scrum team
Simonas Razminas
Director of Engineering

2. Scrum Team in Scrum Guide
Scrum
recognizes no
titles for
Development
Team members
other than
Developer

4. Roles

5. Roles are not important
Tasks are

7. 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.

8. Role: Architect

9. Architecture that enables Agility
Loosely coupled

10. Component shepherd

11. Which roles should be part of Scrum Team in
Agile company?
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

12. Application
Middlaware
(App)
DB Design
Middleware
(Core)
DB
Operations
OS Virtual Compute
Storage Network
Departments by responsibility

13. DevOps
Or how IT Operations work with Developers

14. Summary
• Structure around business value chains
• Discover what specialists should work
together
• Tasks are important
• Form T-Shaped specialists
(c) Classic Powerpoint Slide