Thierry is a salesperson at an organization that provides trading software to banking clients. His clients are telling him they are unhappy with the…

The scenario describes a common problem where an IT department is busy but has low throughput, indicating poor workflow. Visualizing work, often through a Kanban board, makes bottlenecks and priorities visible to all stakeholders. Limiting Work in Progress (WIP) is a core principle of Lean and DevOps that forces the team to finish existing tasks before starting new ones. This reduces context-switching, improves focus, and accelerates the flow of value from development to the client. By managing the flow of work, the team can deliver valuable changes to clients more frequently and predictably.

B. Increasing the budget for the IT department to hire more staff.

Adding more people to a system with poor workflow often decreases productivity due to increased communication and management overhead, a concept known as Brooks's Law.

C. Implementing a more rigorous change approval process to ensure quality.

This would add bureaucracy and delay, further slowing down the rate of change and worsening the problem from the clients' perspective.

D. Asking Thierry to create a comprehensive requirements document for all future changes.

This is a waterfall approach that creates large batches of work and delays feedback, preventing the team from responding quickly to evolving client needs.

1. Kim, G., Humble, J., Debois, P., & Willis, J. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations. IT Revolution Press.

Chapter 5: Make Our Work Visible: "One of the most critical steps to enabling fast flow is to make all the work in the value stream visible... Kanban boards are a common way to visualize work." (p. 57).

Chapter 6: Limit Work in Process (WIP): "When we have too much WIP, there is rampant multitasking, which makes it difficult to complete any one thing... By limiting WIP, we can get a much better understanding of the flow of work." (p. 65). This directly addresses the "busy but struggling to deliver" symptom.

2. Lwakatare, L. E., Kuvaja, P., & Oivo, M. (2020). "Dimensions of DevOps." In Agile Processes in Software Engineering and Extreme Programming – Workshops (pp. 216-223). Springer, Cham.

This publication discusses Lean principles as a core dimension of DevOps, stating, "DevOps is also influenced by Lean principles, which focus on the elimination of waste and continuous improvement of the value stream... Practices such as value stream mapping, limiting work-in-progress (WIP), and small batches are used." (p. 218). This supports using WIP limits to improve value delivery.

DOI: https://doi.org/10.1007/978-3-030-49392-926