Descriptions Tools Establishing control limits on the project to prevent too much work from being included Sprint Review in a sprint Explaining to the business what the project team has accomplished in an iteration Information Radiator Providing senior management with information to give them a pulse of where Pareto Graph the project stands Having limited time for requirements elicitation and having many stakeholders Kanban and Task Boards with informationStakeholder Scenario Engagement Level Investors who do not fully understand the project Supportive implementation scenarios Vendors for the project Unaware Sales team not aligned to delivery Resistant teams Senior management LeadingMatch the project situation on the left to the meeting on the right where the situation could occur. Project Situation Meeting A team member explains that they will not finish their assignment because they have Iteration review no experience in the activity The product owner receives new requirements from the stakeholders and Retrospective includes them in the product backlog The team has decided to commit 10% more than the team's capacity in the next iteration Daily standup and presents it to the product owner. The team identifies that its velocity went down about 40% in the last iteration and Iteration planning then documents the root causeKPis KPis that could reflect project size Revenue KPI 1 KPI 2 Budget KPIs that could reflect project benefits Market share KPI 1 Project duration KPI 2A project is on its sixth iteration out of seven. Select the two points where the team is performing better than expected. (Choose two.) Progress - Burndown 350 300 250 200 Work 150 100 50 0 1 2 4 5 6