Supplementing Scrum with Kanban practices can bring several benefits to a Scrum Team:
* Greater Collaboration (A): By using Kanban practices like visualizing work and managing flow, team members have clearer visibility into each other's tasks, fostering better collaboration.
* Reduced Average Cycle Time (C): Kanban's focus on flow and limiting WIP helps decrease the time it takes for items to move from start to finish.
* Better Transparency (D): Kanban practices enhance visibility into the current state of work, making it easier to identify bottlenecks and areas for improvement.
* Discover Areas of Variability (E): The use of flow metrics such as cycle time and throughput in Kanban can help identify variability in processes, enabling the team to make adjustments for more predictable delivery

During a flow-based Daily Scrum, the team is likely to review metrics such as Work Item Age and Work in Progress (WIP):
* Work Item Age: Helps to identify items that have been in progress for a longer time than expected, signaling possible impediments or the need for swarming to complete those items.
* Work in Progress (WIP): Indicates the number of items currently being worked on, ensuring that the team is not exceeding the agreed WIP limits, which is crucial for maintaining a steady flow

Cycle Time in the context of Professional Scrum with Kanban is defined as the time it takes for a single work item to move from the start to the end of a specific process or workflow. This metric is crucial for understanding how efficiently a team can process individual work items through their defined workflow stages.
*Option A describes a broader measurement from the initial concept to customer feedback post-release. This could align more with the concept of Lead Time rather than Cycle Time.
*Option B correctly describes a possible measurement for Cycle Time - the time a work item spends in one specific column (workflow stage). This is in line with the definitions provided in the Kanban Guide for Scrum Teams, where Cycle Time can measure time within distinct parts of the workflow.
*Option D accurately reflects the definition of Cycle Time, which measures the elapsed time from when work starts on an item until it is completed.
*Option C describes "Throughput," which is a measure of the number of items delivered over a specific time period (e.g., daily or weekly). This is not related to Cycle Time but is a separate flow metric often used alongside Cycle Time to understand team performance and capacity better( Thus, Option C is the correct answer as it does not correctly describe Cycle Time. This explanation is verified with resources from Scrum.org that define Cycle Time within the scope of Professional Scrum with Kanban practices.

According to the Kanban Guide for Scrum Teams, Work in Progress (WIP) limits are set to control the amount of work in progress in a system, enhancing flow, reducing bottlenecks, and ensuring smoother delivery. WIP limits can be changed as a result of an inspection and adaptation cycle, which primarily occurs during the Sprint Retrospective.
During the Sprint Retrospective, the Scrum Team reflects on its process, practices, and interactions. This is the time when the team inspects its flow, evaluates the effectiveness of the current WIP limits, and can make decisions to adjust them based on observed issues or potential improvements. The goal is to optimize the team's ability to deliver value, and adjusting WIP limits during the Retrospective allows for thoughtful consideration based on the team's experience and data from the completed Sprint.
Changing WIP limits at other times could disrupt the flow and reduce the predictability and stability that the limits are intended to create. Therefore, the best practice is to evaluate and change them during the Sprint Retrospective, where the team can inspect the results of their workflow and make informed decisions for the upcoming Sprints