“…Flow differs from traditional software project management because it focuses on managing queues rather than project timelines and phases (Anderson, 2013; Poppendieck, 2011; Power & Conboy, 2015; Reinertsen, 2009). Flow differentiates itself from agile management approaches by (1) adopting an end-to-end perspective of the whole process (Anderson, 2013; Anderson et al, 2011; Petersen, 2011; Reinertsen, 2009), (2) moving from time boxed sprints to continuous deployment of software, and (3) limiting work in progress (WIP) (Cawley, Wang, & Richardson, 2013; Petersen, 2011; Sjøberg, Johnsen, & Solberg, 2012). Flow aims to maximize a continuous flow of value by (1) implementing WIP limits; (2) permitting new work items to immediately enter the development process, and, when required, prioritize it within the WIP limits; and (3) removing impediments to flow (i.e., time boxed sprints, context switching).…”