ABSTRACT
This chapter particularly makes an attempt to justify the author's assertion about the importance of making value visible by making my key points visually. It considers the value of cumulative flow diagrams in Kanban processes for using visualization to predict developing issues. Visualization is a simple way of representing small and large changes to the big picture, letting the viewer determine significance. There are three important ways in which visualization adds value: Learning about the problem status, learning about the process status, and learning about the solution status. Learning is the process of attaining knowledge. In a changing environment, the value of knowledge decreases over time—?put simply, knowledge becomes out of date. Ideally, software development teams are co-located, and managers walk around so information radiators are on paper, posted in the team room or in the hallway. The goal of software development should be to maximize the flow of value through software development.
