Created by Ram Srinivasan CST, CTC, PST

Scrum Accountabilities http://linkedin.com/in/ramvasan

Ram@InnovAgility.com

Scrum Team Accountabilities

Scrum Team (other considerations)
Scrum Master Product Owner Developers

1. Accountable for establishing Scrum as per the Scrum 23. Product value maximize 44. Hold each other accountable as professionals 71. Consists of one Scrum Master, one Product Owner,
Guide 24. Ultimately accountable for the Product Backlog 45. No sub-teams (e.g., QA team, etc.) or sub-groups and Developers
2. Ensures Scrum is understood and enacted, and its (but can delegate any and all work to others) 46. Have competencies and skills to build the Increment and 72. Typically, 10 or fewer people
effective use 25. One person, not a committee the Product 73. Cross-functional - members have all the skills
3. Teaching, coaching, facilitation, mentoring and 26. Accountable for effective Product Backlog 47. Updates Sprint Backlog and Sprint Burn down charts necessary to create value each Sprint
training. Leads, trains, and coaches the organization management 48. Responsible for analysis, architecture, design, etc. 74. Self-Managing - they internally decide who does
in its Scrum adoption 27. Can delegate Product Backlog management to 49. Do Product Backlog Refinement if asked to do what, when, and how
4. Role model for Scrum Values Developers 50. Take responsibility for Product Backlog management 75. No sub-teams or hierarchies
5. Facilitating stakeholder collaboration as requested or 28. Collaborate with the Scrum Team(s), when delegated by the Product Owner (e.g., writing PBIs) 76. Cohesive unit of professionals focused on one
needed stakeholders, vendors, clients, buyers, sponsors 51. Have an eye for technical excellence, prevent and objective at a time, the Product Goal
6. Causes the removal of impediments (ensures that 29. Decision making authority minimize technical debt 77. Responsible for all product-related activities from
Impediments are removed either by themselves or by 30. Accountable for profit/loss, hence (usually) a 52. Determine how to build the Increment stakeholder collaboration, verification, maintenance,
engaging others) Subject Matter and Domain Expert 53. How this is done is at the sole discretion of the operation, experimentation, research and
7. Agent of change – brings change to the organization 31. Can answer how each PBI will be valuable to user Developers. development, and anything else that might be required
to increase productivity of the Scrum Team or customer 54. No one else tells them how to turn Product Backlog items 78. Entire Scrum Team is accountable for creating a
8. Ensuring that all Scrum events take place and are 32. Ensuring that the Product Backlog is transparent, into Increments of value Is accountable for quality of the valuable, useful Increment every Sprint
positive, productive, and kept within the timebox visible and understood product - must be high quality Increment 79. Consider organizational standards and create an
9. Ensure (actively or passively) that the Scrum Team is 33. Ensure that Product Backlog Items are clearly 55. Are required to conform to the Definition of Done when appropriate Definition of Done
protected from outside distractions and the Scrum expressed building the Increment 80. If there are multiple Scrum Teams working together on
Team is focused on creating high-value Increments 34. Their decisions are visible in the content and 56. Estimate effort for product backlog items a product, they must mutually define and comply with
that meet the Definition of Done ordering of the Product Backlog 57. Work at a sustainable pace the same Definition of Done
10. Serves the PO, Scrum Team and the Organization 35. Can cancel the Sprint or stop product 58. Be a multi-learner, learn new tech. skills, learn the 81. Participate in Sprint Planning, Sprint Review, and
11. Works with other SMs to increase the effectiveness of development domain, Sprint Retrospective
the ecosystem 36. Ensure appropriate stakeholders are invited for 59. Responsible for documentation (if necessary) 82. Working in Sprints at a sustainable pace improves the
12. Coach self-management and cross-functionality of the Sprint Review 60. Learn about customer domain and customer problems Scrum Team’s focus and consistency
Scrum Team 37. Learn about customer domain and customer 61. May renegotiate scope of the Sprint during the Sprint
13. Remove barriers between stakeholders and Scrum problems 62. Estimate effort of Product Backlog Items
Teams. 38. Own Product Goal – the commitment to the 63. Does not use Scrum Master as a baby sitter- removed
14. Detect incomplete transparency Product Backlog impediments that can be removed by themselves
15. Works to increase the transparency of Artifacts 39. Decides the strategy for when and how to release 64. Raise impediments to SM if it cannot be solved by
16. Plans scrum implementation within the organization the product/increment(s) themselves
17. Reveal not resolve – hence do not make themselves 40. Accountable for budgets and Profit/Loss – hence 65. Follow XP engineering practices - TDD, Refactoring, Pair
the “bottleneck” when it comes to “problem solving” has a lot of “authority” programming, collective code ownership, and Continuous
18. Be invisibly present – actively do nothing 41. Learn about marketplace changes, competition, Integration
19. Serve the PO - find techniques for effective Product and any new rules/regulations that might affect the 66. Manage and track Sprint Progress
Goal definition and Product Backlog management; Product, and the customers/users 67. Hold each other accountable towards working
20. Serve the PO - Understanding product planning in an 42. If others want to change the Product backlog, they agreements and towards building the increment
empirical environment do so by convincing the Product Owner 68. Continuously improve their technical practices
21. Acts with courage and actively takes direct action 43. The Product Owner ensures that attendees (of 69. Implement action items from the previous retrospective
when integrity of empiricism or Scrum Team’s health Sprint Planning) are prepared to discuss the most 70. Ensures increment is transparent as per DoD
is at risk important Product Backlog items and how they
22. Participate in Sprint Planning, Sprint Review and map to the Product Goal
Sprint Retrospective