The idea of limited work-in-progress (WIP) is coming from Lean methodologies. At its core it means that new tasks should only be started when the current piece of work is done and delivered. Finding the right work-in-progress limit can increase overall system (organisation) throughput. This idea can be applied on many levels including writing code. In this live coding session I will write FizzBuzzWoof code kata in Kotlin showcasing software development workflows which can be used for limiting work-in-progress. In particular: change size notifications, auto-revert, TDD, TCR (test && commit || revert).
Learning outcomes: Details of workflows that help minimise work-in-progress while writing code.
Prerequisites: Basic knowledge of a programming language similar to Java/Scala/Kotlin.