Kanban does not eliminate the need for a Scrum Master when used with Scrum. The Scrum Master

remains an essential role to facilitate the Scrum framework, help the team adopt both Scrum and

Kanban practices effectively, and ensure the team understands and adheres to Scrum principles.

The role of the Scrum Master includes coaching the team on both Scrum and Kanban practices,

removing impediments, and promoting continuous improvement. Therefore, even when Scrum is

used with Kanban, the Scrum Master is not optional but a critical role in ensuring that the integration

of these practices is successful(

Reducing batch size does not always guarantee an increase in overall efficiency. While smaller batch

sizes can lead to faster feedback, more frequent deliveries, and reduced risk, there can be situations

where reducing the batch size too much results in inefficiencies, such as increased overhead costs or

excessive context switching. Thus, the relationship between batch size and efficiency depends on the

context, system constraints, and the nature of the work

Little's Law establishes a relationship between three flow metrics: Work in Progress (WIP), Cycle

Time, and Throughput. It provides insights into how changes in one metric affect the others in a

stable system​​.

Little's Law is used to understand and manage flow within a system but is not a forecasting tool for

output or future performance. It assumes a stable and predictable system where the input and

output rates are consistent.

Why Not True?

Forecasting requires variability, historical data, and often different statistical models. While Little's

Law supports system predictability and capacity planning, it does not directly project future Scrum

Team outputs or delivery dates​.

Thus, Little's Law helps teams analyze and optimize flow but is not used for forecasting.

Work Item Age is the amount of time a work item has been in progress. It acts as a leading indicator

for the length of the Scrum Team's feedback loop for that item. If a work item stays in progress for

too long, it indicates that feedback is delayed, potentially impacting the team's ability to adapt and

respond effectively. Tracking Work Item Age helps the team monitor flow and take timely actions to

ensure that feedback loops remain short and effective

The primary effect of limiting Work in Progress (WIP) is to create a pull system. A pull system ensures

that new work is only started when there is capacity, meaning that work is "pulled" into the system

when the team has the availability to do so. This approach prevents overloading the team and helps

maintain a steady and predictable flow of work, aligning with the Kanban practices within the Scrum

framework