The team is behind in scope compared to projections is the correct response. When a line shows scope built at a very low level compared to projected progress, the indication is that the story points completed are not where they were forecasted to be. The other responses are incorrect. We don’t know what the projected spending is because the chart gives no indication of anything related to spending; it does show that there’s an issue with scope, so the team is not fine.

The correct answer is that agile projects have a fixed cost and time, but the scope can vary. The other responses are incorrect because they don’t accurately define the agile triangle of constraints. Agile projects have a scope that’s flexible, but attempt to have a fixed cost and time. A company knows the amount of money they plan to spend over a certain timeframe, but the actual work done in that time will only be determined….over time.

The correct answer is $160. If late, its expected that Bay Veterinarians will charge less per hour- this provides an incentive for on-time delivery. In the options shown here, $160 is the most reasonable choice for a graduated fixed-price contract. The other responses are incorrect because a standard fixed-price contract includes a lower rate for work that is late; keeping the amount at $175 or increasing it to $190 is not appropriate.

When two developers work together in pair programming they’ll be communicating directly with each other as they work on the project.

The correct answer is: Jalan’s team is able to complete frequent product releases without the introduction of new bugs by using continuous integration; it is embedded into the release to make sure no new bugs are being introduced. The other responses are incorrect because manual testers don’t need to be involved; it would be burdensome on testing resources if releases are frequent, which could be numerous times a day. In addition, regression testing is time-consuming and not a good choice for frequent releases; pair programming is focused more on continuous integration than bugs.

The correct answer is that most defects can be caught early in the software cycle. Test-Driven Development’s most significant benefit on this list is that defects are aught early on. The other answers are incorrect because TDD does not cause extra work for the QA team; it doesn’t ensure full interface testing; it’s not faster than standard development (as both development and unit tests must be completed).

The correct answer is that agile stakeholder management is not focused on controlling and managing; its focus is more on stewardship. The other responses are incorrect because they aren’t focuses of agile stakeholder management. There is no implication that a stakeholder group would be smaller in an agile project, or easier to handle; agile methods don’t require that the team decides what to tell stakeholders; preferred communication is face-to-face and is never limited to information radiators.

The correct and best answer is to explain agile basics to the team, so they understand what it’s about and know what to expect. The other responses are incorrect because they aren’t items required for all stakeholders on an agile team. Since agile charters are different from traditional charters, the team may be confused if this was presented first. Several steps occur before an iteration is planned, so capacity should not be the first thing discussed either. Additionally, there is no agile requirement for a communications planning document, nor must one be created together.

The correct answer is respect. In a retrospective, the value the team is focused on is respect for the opinions of others. The other answers are incorrect. Retrospectives involve both Respect and Courage, but the only accurate answer on this list is Respect. Decency, Education, and Vocalization are not the best choices listed; they are not XP core values. The XP core values are Simplicity, Communication, Feedback, Courage, and Respect.

The correct answer is so that the team owns the issue together, and participates in the solution together. The reason roadblocks are discussed in the daily standup meetings is so the team can deal with the issue together outside of the meeting. The other responses are incorrect because none of them are reasons a roadblock would be discussed in standups. Roadblocks are not resolved in standups, nor is there a document requirement. The team should be solving roadblocks and issues, not the ScrumMaster.