Software projects tend to miss deadlines far more often than they deliver on time, regardless of whether a modern, Agile methodology is employed or software development is guided using a more traditional, waterfall approach. But why is it that software projects, be it partial milestones or the complete delivery of the application, so often come in late and over budget?
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
According to Daniel Bryant, a principle consultant at OpenCredo in London, many of the answers can be found in the psychology of the individual. Borrowing from the international bestseller, Thinking, Fast and Slow, by Nobel Memorial Prize-winning researcher Daniel Kahneman, Bryant applies concepts such as the optimistic bias and illusion of control to help explain how both the psychology of the individual developer and the sociology of the software development team are inclined to create unrealistic estimates that put software delivery schedules at risk.
At JavaOne 2015, TheServerSide spoke with Daniel Bryant about these common flaws in the thought processes of the IT professional, and what they can do to address the problems these flaws present.
"People naturally like to think about good consequences when we set up projects. When we set up interesting things, we like to think we'll do well," Bryant said. However, efficient managers need to be wary of that mindset, he later added, and learn to ask developers, "Do you understand the [business] problem and the context it's being talked about in the software and the context?"
Watch the first of two video interviews featuring Daniel Bryant to hear more about optimistic bias and other software development fallacies that might be putting your software projects at risk.
Has your enterprise come across development flaws in software projects? Let us know.