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