A.Sharing information.

B.Agreeing on a due date.

C.Agreeing on the design.

D.Pair programming.

A.Release vision, assumptions, action items, and iteration goals

B.Risks, action items, dependencies, and Release Backlog

C.Prioritized Product Backlog, risks, action items, and release goals

D.Estimated iteration velocities, risks, action items, and Release Backlog

A.Team members provide story estimates individually and discuss their reasoning until a consensus on the estimate is reached.

B.Team members assign a realistic and a pessimistic estimate to each story, and points are assigned based on the calculated average.

C.Team members apply relative sizing to each task, and story points are triangulated based on the other stories in the Sprint Backlog.

D.Team performance on prior projects is analyzed, and actual hours and durations are used to determine estimates for similar user stories.

A.Project managers

B.Team members

C.Scrum Masters

D.Agile coaches

A.Team completes them.

B.End of the sprint.

C.Release is complete.

D.End of the project.