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