Estimation is one of the most important components of project management. In my opinion it is second only to the creation of a work breakdown structure (WBS). Project schedule and costs are directly impacted by accuracy of the estimation. Whenever I bring up the subject of estimation as a topic of discussion, invariably someone will mention: “We typically end up underestimating the amount of time needed to complete tasks – especially unfamiliar tasks.” The one common theme that resonated was that everyone was reasonably confident that the tasks would be finished on time. After all, they did add safety to tasks to account for variation. So if we had safety protecting the tasks, why then do we not finish projects on time? Before we look at answering this question, let’s briefly look at the principle behind Theory of Constraints.
No such thing as multitasking
There is no such thing as multitasking. Humans are incapable at multitasking. We only task switch. And so do computers. The difference is that computers can task switch at a much faster rate to create an illusion of multitasking. I’ll use the term multitasking and task switching interchangeably for the reminder of this post.
Importance of Kanban work-in-progress (WIP) limits
Traffic Jams! For some it is the bane of driving. Accidents, construction, reduced speed zones are all some of the root causes. But did you know of Phantom Traffic Jams? For no apparent reason the traffic slows to a crawl. No accidents or lane closures and there is no easy way out. Researchers have linked such phantom traffic jams to traffic density and variations in driver behavior. A trivial reason such as a driver braking too hard, can cause a phantom traffic jam 8 to 10 kms behind. And this traffic jam takes a life of its own. You could spend hours within that jam. So what does phantom traffic jams have to do with WIP limits on Kanban for software development?
Lean software development using Kanban
Unlock efficiency in software projects with Kanban, a Lean Agile tool that minimizes waste and maximizes delivery speed. Explore Kanban’s pull system and key principles to improve workflow and reduce project duration without sacrificing quality.