A.Assembling the team and asking the members to achieve a milestone in a small iteration.

B.Assembling the team and discussing roles and responsibilities of each member on the team.

C.Taking the team offsite for icebreaker sessions and other activities to ensure team members get to know each other.

D.Creating a project charter, documenting roles and responsibilities of each member, and sending it to the team members.

A.interview new team members for fit.

B.set priorities and identify product features.

C.set sprint and release schedules.

D.approve development plans and tasks.

A.Display the remaining work across time.

B.Identify dependencies between sprints or iterations.

C.Display the level of effort and resources utilized.

D.Identify and communicate upcoming milestones.

A.Function points

B.Use-case points.

C.Story points.

D.Lines of code.

A.Amount of money the risk will cost if it occurs.

B.Amount of damage to the project if the risk occurs.

C.Funds set aside to contain the risk.

D.Probability a risk will occur.