Do your developers make business decisions?
By Wayne Ariola
December 21, 2012 —
(Page 1 of 2)
Related Search Term(s): Delta Airlines, testing
Those of us in the development testing business rarely show restraint when software-related news about a failure makes big headlines. It’s bad enough that these organizations take a PR beating, but to kick them while they’re down to hock our wares is uncouth at best. We’re not first in line, nor will we be last, but we’re taking our turn just the same.
Delta’s legal turbulence
In this particular case, Delta is lucky. Aside from the bad publicity and small amount of work to update the app, Delta will likely incur minimal damages from the infraction. Had there been a problem with one of the core features that may result in real damages, such as the “pay for checked bags” feature, the airline may have had a bigger problem on its hands.
Honest mistake? Maybe
We’re not here to judge Delta, or any other company for that matter. We’re only talking about this snafu to make a point: that developers are making business decisions every day, and that these decisions carry real consequences. Their code determines the safety, security, performance and reliability of the software that drives the business, giving them the power to introduce or minimize risks. By allowing developers to make critical business decisions related to the software, managers, directors and C-level executives have delegated to them an extraordinarily high level of business responsibility. Developer decisions directly affect immediate or future success, growth, damages or liabilities, as well as the stability of business leadership positions.