The KSS-scheduling algorithm saved 4 days in terms of schedule and one person-day of effort. Every time when
an unfinished WI is interrupted, it takes some extra effort to finish it (effort penalty). This effort penalty is caused by
reduced resource performance due to context switching between different WIs. Effort associated with the KSSscheduling
algorithm was saved because of fewer of context switching events between different WIs. Time was
saved because of more efficient work dependency resolution. To better explore how limiting work in progress can
affect schedule and effort, the simulation scenario must be larger in terms of number of WIs and length of the
simulation. The simple SoS example has 4 teams and 22 WIs. This example was used as a proof of concept for small
agile teams. Typical number of WIs in larger scenarios is between 100 and 2000 WIs. Additional experiments have
been run with such scenarios. The outputs were relatively consistent with smaller cases