True or False: Work Item Age is a leading indicator for the length of the Scrum Team’s feedback loop for that (in progress) item.
A. True
B. False

Scrum Teams using Kanban can start to increase predictability by:
(choose the best answer)
A. Inspecting and adapting the Product Backlog during the Sprint Review.
B. Improving transparency by having a CFD, Control Chart and Aging chart.
C. Visualizing the workflow using a Kanban board.
D. Reducing the amount of work in progress by introducing Work in Progress (WIP) Limits.

Some Kanban implementations prescribe the practice of implementing feedback loops. The Kanban Guide for Scrum Teams does not include that practice. Why?
(choose the best answer)
A. There are five feedback loops in Scrum. The Kanban Guide for Scrum Teams builds upon the Scrum guide. There is no need to explicitly add that practice.
B. There is no need to implement feedback loops in Kanban. Feedback loops only apply at the enterprise level.
C. A Scrum Team must devise and design their own feedback loops through an inspection and adaptation process.
D. Kanban boards may act as a feedback loop in a Scrum with Kanban environment.

What might be considered during the Sprint Retrospective once a team decides to supplement their Scrum with Kanban?
(choose the best answer)
A. Workflow.
B. Current policies.
C. WIP Limit.
D. Metrics and charts such as Cumulative Flow Diagram, Cycle Time Scatterplot, and Work Item Aging.
E. All of the answers.

What are the four key flow metrics in Scrum with Kanban?
(choose the best answer)
A. Work in Progress (WIP), Velocity, Lead Time, Cycle Time.
B. Velocity, Lead Time, Cycle Time, Cost.
C. Throughput, Work in Progress (WIP), Velocity, Lead Time.
D. Work in Progress (WIP), Work Item Age, Throughput, Cycle Time.

What are possible benefits of supplementing Scrum with Kanban practices?
(choose the best four answers)
A. May result in greater collaboration within Scrum Team.
B. Scrum Teams no longer need the Sprint time box.
C. May reduce an average Cycle Time.
D. Introduces better transparency into state of Work in Progress (WIP).
E. May help to discover areas of variability within your Sprint.
F. Removes the need for the Sprint Planning event.
G. Allows teams to release multiple times a Sprint.