Kallokain

I recently made a video, An Introduction to Reference Class Forecasting , where I show how to use a simple, yet reliable, alternative to estimates in software projects. In the video, I touch on the topic of timeboxing , and why it can have the opposite of the desired effects in software development. Timeboxing is generally accepted as a good, even indispensable thing. It is an integral part of Scrum, and other Agile methodologies. (Even the ones I like a lot.) It is worth going into a little bit of  detail about how, and why, timeboxing can backfire. What is timeboxing? Timeboxing is a project planning technique where a fixed time period is allocated to an activity. For example, in Scrum, Sprints, Sprint Planning, Sprint Review, and Daily Scrum, are all timeboxed. If we look at other Agile methodologies, like Extreme Programming, Lean Software, Development, and Dynamic systems Development Method (DSDM), they use timeboxing in some shape or form. Kanban is an exception. Note t...

This has been an interesting week. Vasco Duarte interviewed me for Scrum Master Toolbox recently. The podcast was published yesterday. I also rebooted my own management Youtube channel, with three videos on how to go Agile, in a much more flexible and adaptive manner than most organizations do. Here is a link to the Scrum Master Toolbox podcast: From Waterfall to Flow—Rethinking Mental Models in Software Delivery We had a long talk about things that might be useful for you to know. As Vasco put it in his introduction to the podcast: In this BONUS episode, we explore the origins and persistence of waterfall methodology in software development with management consultant Henrik Mårtensson.    Based on an article where he details the history of Waterfall, Henrik explains the historical context of waterfall, challenges the mental models that keep it alive in modern organizations, and offers insights into how systems thinking can transform our approach to software delivery.   ...