SAFe Scrum Master Questions & Answers
1. Agile development is...: incremental
2. over processes and tools: Individuals and interactions
3. Working software over...: comprehensive documentation
4. Customer collaboration over...: contract negotiation
5. over following a plan: Responding to change
6. Agile Manifesto: Individuals and interactions over processes
and tools Working software over comprehensive documentation
Customer collaboration over contract
negotiation Responding to change over
following a plan
7. Agile Manifesto Principles 1-6: 1. Our highest priority is to satisfy the
customer through early and continuous delivery of valuable software
2.Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference for the shorter timescale
4.Business people and developers must work together daily
throughout the project (Have a role for business sides, then roles for IT.
Show your work, transparency builds trust)
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
,done
6.The most efficient and effective method of converying information to
and within a development team is face-to-face conversation
8. Transparency builds...: trust
9. Agile Manifesto Principles 7-12: 7. Working software is the primary
measure of progress
8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely
9. Continuous attention to technical excellence and good design
enhances agility
10.Simplicity - the art of maximizing the amount of work is not done - is
essential
11. The best architectures, requirements, and designs emerge from
self-organizing teams
12.At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
(Retrospective "retro"; reuse/revision)
10.Develop on cadence...: Release on demand
11.Agile is value...: and quality driven
, 12.Agile teams show that matter: dates
13.Business owners show how matter: priorities
14.Fix , not scope: quality
15.Stretch Objectives: Time & capacity to do it, we plan for it, but
are not committed to it
16.Backlog is NOT a...: commitment
17.Queue IS a...: commitment
18.Agile frameworks:
SAFe Scrum
Crystal
Kanba
n
eXtreme Programming
(XP) Feature-driven
development
19.Agile practices:
Timeboxing User stories
Daily stand-
ups Frequent
demos
Test-driven
development
Information radiators
1. Agile development is...: incremental
2. over processes and tools: Individuals and interactions
3. Working software over...: comprehensive documentation
4. Customer collaboration over...: contract negotiation
5. over following a plan: Responding to change
6. Agile Manifesto: Individuals and interactions over processes
and tools Working software over comprehensive documentation
Customer collaboration over contract
negotiation Responding to change over
following a plan
7. Agile Manifesto Principles 1-6: 1. Our highest priority is to satisfy the
customer through early and continuous delivery of valuable software
2.Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive advantage
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference for the shorter timescale
4.Business people and developers must work together daily
throughout the project (Have a role for business sides, then roles for IT.
Show your work, transparency builds trust)
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
,done
6.The most efficient and effective method of converying information to
and within a development team is face-to-face conversation
8. Transparency builds...: trust
9. Agile Manifesto Principles 7-12: 7. Working software is the primary
measure of progress
8. Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely
9. Continuous attention to technical excellence and good design
enhances agility
10.Simplicity - the art of maximizing the amount of work is not done - is
essential
11. The best architectures, requirements, and designs emerge from
self-organizing teams
12.At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
(Retrospective "retro"; reuse/revision)
10.Develop on cadence...: Release on demand
11.Agile is value...: and quality driven
, 12.Agile teams show that matter: dates
13.Business owners show how matter: priorities
14.Fix , not scope: quality
15.Stretch Objectives: Time & capacity to do it, we plan for it, but
are not committed to it
16.Backlog is NOT a...: commitment
17.Queue IS a...: commitment
18.Agile frameworks:
SAFe Scrum
Crystal
Kanba
n
eXtreme Programming
(XP) Feature-driven
development
19.Agile practices:
Timeboxing User stories
Daily stand-
ups Frequent
demos
Test-driven
development
Information radiators
