An incremental and emergent approach to software design

A software development technique based on automated tests

A predictable way to develop working well-organized code

Creating a manual test script before writing code

Having testers involved in the development process

During the sprint planning when they can’t fit enough into the sprint

Prior to starting a new sprint

In the retrospective when it turns out they can improve quality

Prior to starting a new project

A technique for ensuring that units of co-dependent systems integrate correctly

A way to ensure product code satisfies the user requirements

A test that isolates and verifies individual units of functionality

A test that ensures a specific method integrates properly with the code calling it

Extracting methods

Reordering method parameters to improve readability

Changing external interfaces or APIs

Renaming things to be more logical

Extracting interfaces

Daily Scrum

Sprint

Sprint planning

All of these

Sprint review

Sprint retrospective

A term representing the eventual consequences of poor technical choices

Developers that have to pay college debt

Code that hasn’t been documented

The money an organization owes to tool and hardware vendors

Manage the meeting

All of these

Lead the discussion

Ensure that the meeting takes place and that its timebox won't be exceeded

Make sure all three questions of the daily scrum are answered

Increase quality

Complain only in this session to avoid complaining in the rest of the sprint

Have more fun during the sprint

Increase effectiveness

The continuous restructuring of software to retain flexibility

Having the tester in the development team write the test plans before coding

Creating tests before satisfying them

Testing existing code before adding more code to it

Release planning

Daily scrum

Sprint review

Sprint retrospective

Refinement meeting

Just before the first check-in

Just before the product is released

When the product owner asks for a build

Just before the end of the sprint

As soon as there is code in the version control system

Allow the developers to self-manage and decide what to do their selves.

Raise it as an impediment and make sure that management solves it.

Create a schedule and alternate who is responsible for the daily scrum logistics

Decide the best solution and arrange a meeting to inform the developers.

True

False

Unit tests per class

Cycle time per product backlog item

Number of check-ins per day

Depth of inheritance

Cyclomatic complexity

Class coupling

The ratio of the number of tests to lines of code in the system being tested

The quality of unit tests being written

Code being exercised by tests

The absence of defects in code

When a feature is done