A. Report progress of the work effort, what work will be done next, and review impediments to progress.

B. Prioritize the Product Backlog, generate development and testing estimates, and plan the next iteration.

C. Provide a demonstration of the features developed during the iteration, get feedback from users, and begin testing.

D. Identify what worked well, what did not work well, and what actions should be taken to improve the process.

A. Reflect at the end of every iteration and identify improvements that will increase the quality of the product.

B. Participate in a mandatory meeting to share status updates across the team and to ensure that everyone is on track.

C. Understand from the management if the project is achieving the Scope, Quality, Cost, and Schedule goals.

D. Set goals at the beginning of the iteration and identify requirements that can be delivered in that iteration.

A. Too large.

B. Not estimated correctly.

C. Not testable.

D. Not descriptive of the value.

A. Release planning

B. Sprint planning

C. Sprint Retrospective

D. Daily Scrum

A. Iterations, Product Road map Planning, and Number of Sprint Iterations

B. Visioning, Product Roadmap Planning, and Product Backlog Definition

C. Visioning, Product Backlog Definition, and Project Charter Creation

D. Burndown chart, Product Roadmap, and sprints’length

A. Release planning, Iteration planning, and Estimation

B. Estimation, Spike Solutions, and Iteration planning

C. Iteration planning, Continuous Integration, and Estimation

D. Vision, Release planning, and Performance Optimization