A. Two developers writing code together, providing constant peer review
B. Developer and tester work together to write and test code
C. Two programmers writing code separately, but always review each other's pull requests
D. Managers doing performance reviews by comparing one programmer's code to another's
A. typically 10 or fewer people
B. this differs every sprint
C. at least 8 people
D. 3 to 11
A. Objective Driven Development
B. Acceptance test driven development
C. Quality Oriented Requirements Development
D. Regression testing
A. Two or more developers working together to ensure proper coding and configuration management
B. Copying a portion of a codebase to isolate it from the original codebase
C. Combining two or more versions of code into a single codebase
D. Identifying a particular codebase as ready for distribution
A. Sprint goal
B. Sprint planning outcome
C. Definition of done
D. Product goal
A. Great development practices
B. A technical requirement that must be satisfied
C. A bug
D. Something that completes the test coverage of a system
A. You are unable to check in code without them
B. Without them you can't tell if your code works
C. They help you find defects and configuration management issues
D. They are part of the Definition of Done
A. How to improve the scrum process in this sprint?
B. Who is going to do what?
C. What can be done in this sprint?
D. When is this sprint going to be done?
E. How will the selected work get done?
F. Why is this sprint valuable?
A. Code that hasn't been documented
B. The money an organization owes to tool and hardware vendors
C. A term representing the eventual consequences of poor technical choices
D. Developers that have to pay college debt
