Demystifying roles in scrum team - Agile Tour 2013 Kaunas


Published on

Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule. What does that mean? Should everyone write code? What about testers, designers, architects or data-warehouse specialists? Should every Scrum Team get one person per such role? What if potentially releasable Increment of “Done” product cannot bet achieved without infrastructure design? How does IT come to the picture? Who is responsible for architecture of components and solution (especially when multiple teams work on them)? When North Korea is going to stop their madness? All questions but last will be revisited on presentation by Simonas

Published in: Technology, Sports
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Image:
  • Image: area specialist are the best – not fact anymore. Examples when and whyWhy T-Shaped specialists are good: common language with other specialists,no handovers required, no need for maintaining docs (Lean, waste removal) no bottlenecks
  • Image: specialists are required and how many? DW, IT Ops, infrastructure – do you need them in Scrum Team?Simply – you need all who will build part of increment.
  • Image: is not about roles in Scrum, it is about tasks requiredto accomplish increment
  • Image: Agile or big product/project.Architecture challenge. Everybody is responsible for architecture in Agile company
  • Can’t have dedicated one in each Scrum Team – you will say and I will agree.Architecture can be found in tasks of the backlog. It is part of Sprint increment.Best practices for Agile architecture in next slides
  • Image: defined by Esther Derby
  • Organize company around Value ChainsYou may want evenmerge departments
  • Every important business opportunity goes through Development and IT OpsBe careful: internal sytem optimization may NOT damage global system (e.g. by increasing lead time to get business value)Quite often goals set by managers to their employees are not well aligned with value chain
  • Emergency issue: Grey areas of responsibilities when IT Ops and Development are separated departmentsChange management: role theater. Idea is good, but result rarely is at expected level
  • Image:
  • Demystifying roles in scrum team - Agile Tour 2013 Kaunas

    1. 1. Demystifying roles in Scrum team Simonas Razminas Director of Engineering
    2. 2. Scrum Team in Scrum Guide Scrum recognizes no titles for Development Team members other than Developer
    3. 3. Roles
    4. 4. Roles are not important Tasks are
    5. 5. 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.
    6. 6. Role: Architect
    7. 7. Architecture that enables Agility Loosely coupled
    8. 8. Component shepherd
    9. 9. 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.
    10. 10. Application Middlaware (App) DB Design Middleware (Core) DB Operations OS Virtual Compute Storage Network Departments by responsibility
    11. 11. DevOps Or how IT Operations work with Developers
    12. 12. Summary • Structure around business value chains • Discover what specialists should work together • Tasks are important • Form T-Shaped specialists (c) Classic Powerpoint Slide