Agile Scrum Master Certification (Answered)
Verified Solution
Manifesto for Agile Software Development // individuals and interactions
———————- Over processes and tools
Manifesto for Agile Software Development // contract negotiation
Customer collaboration Over —————
Manifesto for Agile Software Development // comprehensive documentation
Working software Over —————————-
Manifesto for Agile Software Development
responding to change ——— Over following a plan
Our highest —- is to satisfy the —- through early and ——- delivery of valuable
software
Priority, customer, continuous // principles
Welcome ———- requirements, even ——— In development. Agile processes
harness ———- For the customers's competitive advantage.
Changing, late, change // principles
Deliver ———- software frequently, from a ——- weeks to a couple ———-, with a
preference for the shorter timescale
Working, couple of, months // principles
Business people and ——— must work ——— daily throughout the ————.
Developers, work, project // principles
Build projects around ——- individuals. ——— the environment and ——- they
need, and trust them to get the job done.
Motivated, give, support // principles
The most ———- and ———— method of conveying information to and within a
development team is ————— conversation.
Efficient, effective, face-to-face
—————- is the primary measure of progress.
Working software // principles
Agile processes promote ———- development. The ————, developers, and
users should be able to maintain a constant pace ———.
Sustainable, sponsors, indefinitely // principles
Continuous attention to technical ———— and good design enhances ————-.
Excellence, agility // principles
Simplicity — the ——— of maximizing the ———- of work not done — is ————.
Art, amount, essential // principles
The best ————, ————, and ————-, emerge from self-organizing teams.
Architectures, requirements, designs
Iteration
Single development cycle where each Agile team defines, builds, integrates and tests
the stories from their iteration backlog
Program Increment (PI)
Timebox in which an agile release train (ART) delivers incremental value In the form of
working, tested software and systems. Typically 8-12 weeks long
Acceptance Criteria
Verified Solution
Manifesto for Agile Software Development // individuals and interactions
———————- Over processes and tools
Manifesto for Agile Software Development // contract negotiation
Customer collaboration Over —————
Manifesto for Agile Software Development // comprehensive documentation
Working software Over —————————-
Manifesto for Agile Software Development
responding to change ——— Over following a plan
Our highest —- is to satisfy the —- through early and ——- delivery of valuable
software
Priority, customer, continuous // principles
Welcome ———- requirements, even ——— In development. Agile processes
harness ———- For the customers's competitive advantage.
Changing, late, change // principles
Deliver ———- software frequently, from a ——- weeks to a couple ———-, with a
preference for the shorter timescale
Working, couple of, months // principles
Business people and ——— must work ——— daily throughout the ————.
Developers, work, project // principles
Build projects around ——- individuals. ——— the environment and ——- they
need, and trust them to get the job done.
Motivated, give, support // principles
The most ———- and ———— method of conveying information to and within a
development team is ————— conversation.
Efficient, effective, face-to-face
—————- is the primary measure of progress.
Working software // principles
Agile processes promote ———- development. The ————, developers, and
users should be able to maintain a constant pace ———.
Sustainable, sponsors, indefinitely // principles
Continuous attention to technical ———— and good design enhances ————-.
Excellence, agility // principles
Simplicity — the ——— of maximizing the ———- of work not done — is ————.
Art, amount, essential // principles
The best ————, ————, and ————-, emerge from self-organizing teams.
Architectures, requirements, designs
Iteration
Single development cycle where each Agile team defines, builds, integrates and tests
the stories from their iteration backlog
Program Increment (PI)
Timebox in which an agile release train (ART) delivers incremental value In the form of
working, tested software and systems. Typically 8-12 weeks long
Acceptance Criteria
