A. Continue with the current plan to maintain team velocity.

B. Add a goal to the current iteration to fully mitigate or control the risk.

C. Balance risk reduction and value adding activities in the next iteration.

D. Update the risk register and seek direction from a risk specialist.

A. Increase the frequency of emails and/or try to call the stakeholder.

B. Set up a meeting with the stakeholder to modify the working agreement and ensure future engagement.

C. Remind the stakeholder of their obligation to engage in the project.

D. Talk to the stakeholder's superior so they can offer coaching and guidance on project involvement.

A. Assigning extra points to each task to allow time for changes

B. Stories describing infrastructure tasks and analysis tasks

C. A buffer in the sprint to mitigate unexpected risks

D. The increase in velocity and cost

A. The entire team is responsible for quality and QA is responsible for surprises, gaps, and other intricacies that may have been overlooked.

B. Quality is the responsibility of the entire team, and the product manager defines the functionality from end to end.

C. The entire team is responsible for quality, but each team member's role may vary as stated in the definition of done (Do

D. The entire team is responsible for quality and each team member is accountable for ensuring the success of every component.

A. Encourage a team member to raise this during the retrospective to ensure that the product owner is aware.

B. Communicate this to the product owner, and offer to help facilitate discussions with the team.

C. Escalate this issue to the sponsor so that corrective action may be taken.

D. Inform the product owner's manager so that corrective action may be taken.

A. Ask the team member to take full ownership of the issue.

B. Monitor the issue in a notation system.

C. Include the issue in the risk log.

D. Advise the team member to add the issue to the board.

A. Read and identify user stories from the backlog that will contribute to accomplishing the goal.

B. Compile a list of ideas to improve the velocity of the team so they can plan more story points in the next sprint.

C. Prepare an effort estimation for each story based on their technical expertise.

D. Prepare a list of tasks required to accomplish the goal and the order in which they should be executed.

E. Consider the possible risks of each selected user story and the value they add for the final user.

A. Passive-aggressive

B. Collaborative

C. Random

D. Synchronous

A. Ask questions to determine if the product owner can define the desired level of security.

B. Execute a spike to research security features for the project.

C. Ask questions to determine where and how the product owner wants to use the product.

D. Add new security features to the backlog and prioritize.