In the Part 1 of “The Fancy Mess of Scrum”, I talked about the flawed intuition behind sprints: how they batch work, obfuscate inefficiencies, and are superfluous in terms of extrinsic motivation. In this post I want to delve deeper into higher order negative externalities that sprints spawn – the consequences of the consequences. By Reading This Post, You Will Learn: Why scrum is a mismatch for game development from the word go due to art asset pipelines How the need to allow time for QA and product owner review creates significant churn The problem with having developers move ahead on stories in future sprints How limiting developer throughput extends the flow time of feature development Haters Gonna Hate (But I’m Not a Hater) I am not anti-scrum. It was an essential starting point for me as a project and process manager. It offered a means for me to provide value for … Continue reading The Higher Order Consequences of Sprints: The Fancy Mess of Scrum, Part 2