The correct answer is Charlie won’t have to focus solely on code testing. In Acceptance Test-Driven Development (ATDD), the focus is not exclusively on code testing, but on requirements instead. The other answers are incorrect: In ATDD, developers write the tests upfront; focus on testing business requirements; when an item is pulled from the backlog, the acceptance criteria is discussed often.

The correct answer is to ensure stakeholder engagement so that any changes are known as soon as possible. The primary purpose is to ensure engagement and elicit changes as early as possible. The other responses are incorrect because regardless of reasons, iterations are not supposed to be given a time extension; stakeholders have no such requirement to try the software themselves or submit changes to a board.

The correct answer is to have the product owner and the delivery team prioritize the backlog. This is done to ensure the alignment with stakeholder priorities. The product owner should be well-versed in business priorities and customer needs. The other responses are incorrect because prioritization is done just in time for each iteration; it’s not charter based; the entire stakeholder team doesn’t prioritize nor does it use Planning Poker.

The correct answer is information radiators; this is what is described in the scenario. The other answers are incorrect because they aren’t accurate descriptions of what’s listed in the scenario: cards won’t reduce risk; they aren’t wireframes, which are a type of diagram; nor are they agile status reports.

A wall chart showing the team’s velocity is the best example of an information radiator and is the correct answer. A velocity chart on the wall allows everyone to see the information and its relevance to the project. The other answers are incorrect because they are not examples of information radiators. A spreadsheet, a daily status report, and chat in the breakroom are not highly visible to the team.

The correct answer is that as long as the team is comfortable seeing this type of information, and the tool is accessed easily, it’s perfectly ok. It’s fine to use a tool such as this if the information is easily accessed and there is little time required. The other responses are incorrect because there’s no definitive rule about the type of details that may be helpful in an agile project – the team’s agreement of the value provided is what is most important; an automated feed doesn’t have to be avoided per se, but it shouldn’t be difficult to get due to security restrictions that take extra time from everyone.

The correct answer is the assurance that one responsible party is accountable. More than one party should be accountable. This is untrue in agile projects; the team is accountable, and Manuel needs to bring this issue to the team. The other responses are incorrect: They are all accurate descriptions of options used to handle issues in an agile project; Manuel should take his problem to the team to allow for better decisions using multi-functional knowledge; to build team relationships; to ensure that the group takes ownership of the problem, not Manuel personally.

The correct answer is working through the Red Zone. In this scenario, Raquel’s team is working in the Red Zone, which goes against agile principles. The other responses are incorrect because they are not good descriptions of the behaviors presented in the scenario: norming, or collaboration, is when a team starts to work together, i.e. collaborate, is not represented here; Raquel is being transparent, but the team is not.

Quiet writing is the correct answer. Carlotta’s writing her ideas for five minutes is an accurate description of quiet writing. The other responses are incorrect because they are inaccurate based on this scenario. Fishbone diagramming is focused on root cause analysis of an issue; free hand is a fictional term; Round Robin focuses on everyone speaking in the group.

Remember the Future is the proper name for the technique depicted in this question and is the correct answer. The other terms are incorrect because they are not valid for this description; they are fictional; they are not agile techniques for risk identification.