Agile Tester 2

Question 1

The Agile Manifesto contains four STATEMENTS of values:

Answer 1

 Individuals and interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

Question 2

From a customer perspective, working software is much more useful and valuable than overly detailed documentation.

What benefit does it give the team?

Answer 2

it provides an opportunity to give the development team rapid feedback.

Question 3

Customers often find great difficulty in specifying the system that they require. Collaborating directly with the customer gives what benefit?

Answer 3

Improves the likelihood of understanding exactly what the customer requires.

Question 4

Core agile manifesto values has twelve principles, which are those?

Question 5

Core agile manifesto values has twelve PRINCIPLES, which are those?

Answer 5

 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
 Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
 Deliver working software frequently, at intervals of between a few weeks to a few months, with a preference to the shorter timescale.
 Business people and developers must work together daily throughout the project.
 Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.
 The most efficient and effective method of conveying information to and within a development
team is face-to-face conversation.
 Working software is the primary measure of progress.
 Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefinitely.
 Continuous attention to technical excellence and good design enhances agility.
 Simplicity—the art of maximizing the amount of work not done—is essential.
 The best architectures, requirements, and designs emerge from self-organizing teams.
 At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behavior accordingly.

Question 6

What does the whole team approach mean?

Answer 6

The whole-team approach means involving everyone with the knowledge and skills necessary to ensure project success.

Question 7

What is the correct size of a team?

Answer 7

A team should be relatively small; successful teams have been observed with as few as three people and as many as nine.

Question 8

What kind of meeting supports the whole team approach?

Answer 8

Daily stand-up meetings

Question 9

What are the 3 main benefits of the whole team approach:

Answer 9

 Enhancing communication and collaboration within the team
 Enabling the various skill sets within the team to be leveraged to the benefit of the project
 Making quality everyone’s responsibility

Question 10

Where does the ESSENCE of the whole team approach lie?

Answer 10

The essence of the whole-team approach lies in the testers, developers, and the business representatives working together in every step of the development process.

Question 11

What is known as the power of three?

Answer 11

The concept of involving testers, developers, and business representatives in all feature discussions is known as the power of three

Question 12

Name a way to provide rapid feedback throughout the development lifecycle.

Answer 12

By using continuous integration

Question 13

What are the 5 main benefits of early and frequent feedback?

Answer 13

The benefits of early and frequent feedback include:
 Avoiding requirements misunderstandings, which may not have been detected until later in the
development cycle when they are more expensive to fix.
 Clarifying customer feature requests, making them available for customer use early. This way,
the product better reflects what the customer wants.
 Discovering (via continuous integration), isolating, and resolving quality problems early.
 Providing information to the Agile team regarding its productivity and ability to deliver.
 Promoting consistent project momentum.

Question 14

What five VALUES does Extreme Programming embrace to guide development?

Answer 14

Communication, simplicity, feedback, courage, and respect.

Question 15

In Scrum, what is a Sprint?

Answer 15

Scrum divides a project into iterations (called sprints) of fixed length (usually two to four weeks).

Question 16

In Scrum, what is a Product Increment?

Answer 16

Each sprint results in a potentially releasable/shippable product (called an increment).

Question 17

In Scrum, what is a Product Backlog

Answer 17

The product owner manages a prioritized list of planned product items (called the product backlog). The product backlog evolves from sprint to sprint (called backlog refinement).

Question 18

In Scrum, what is a Sprint Backlog?

Answer 18

At the start of each sprint, the Scrum team selects A SET OF HIGHEST PRIORITY ITEMS (called the sprint backlog) from the product backlog. Since the Scrum team, not the product owner, selects the items to be realized within the sprint, the selection is referred to as being on the PULL PRINCIPLE rather than the push principle.

Question 19

In Scrum, what is Defenition of Done?

Answer 19

To make sure that there is a potentially releasable product at each sprint’s end, the Scrum team discusses and defines appropriate criteria for sprint completion. The discussion deepens the team’s understanding of the backlog items and the product requirements.

Question 20

In Scrum, what is Timeboxing?

Answer 20

Only those tasks, requirements, or features that the team expects to finish within the sprint are part of the sprint backlog. If the development team cannot finish a task within a sprint, the associated product features are removed from the sprint and the task is moved back into the product backlog. Timeboxing applies not only to tasks, but in other situations (e.g., enforcing meeting start and end times).

Question 21

In Scrum, what is Transparency?

Answer 21

The development team reports and updates sprint status on a daily basis at a meeting called the daily scrum. This makes the content and progress of the current sprint, including test results, visible to the team, management, and all interested parties. For example, the development team can show sprint status on a whiteboard.

Question 22

Which 3 roles does Scrum define?

Answer 22

Scrum Master
Product Owner
Development Team

Question 23

What does a Scrum Master add?

Answer 23

Ensures that Scrum practices and rules are implemented and followed, and
resolves any violations, resource issues, or other impediments that could prevent the team
from following the practices and rules. This person is not the team lead, but a coach.

Question 24

What does a Product Owner add?

Answer 24

Represents the customer, and generates, maintains, and prioritizes the
product backlog. This person is not the team lead.

Question 25

What does the development team add?

Answer 25

Develop and test the product. The team is self-organized: There is no
team lead, so the team makes the decisions. The team is also cross-functional (see Section 2.3.2 and Section 3.1.4).

Question 26

What is the general objective of Kanban?

Answer 26

The general objective is to visualize and optimize the flow of work within a value-added chain.

Question 27

What is the Kanban Board?

Answer 27

The value chain to be managed is visualized by a Kanban board. Each column shows a station, which is a set of related activities, e.g., development or testing. The items to be produced or tasks to be processed are symbolized by tickets moving from left to right across the board through the stations.