Some software bugs are like the cicadia, emerging only under the 'right' conditions and wreaking havoc until they're stopped. Without the right tools, no amount of software testing can stop these bugs from causing a meltdown. Just ask Nasdaq.
On many an old map, unknown territories were marked, 'Here be dragons!' Sure, it's actionable, but it's not very informative. Centuries later, do we have the same problem with software project management? Here's how to slay the dragons that threaten to set your cloud projects aflame.
Beyond testing scripts and automating everything, a new approach to software testing is gaining traction in larger organizations. Proponents including Barclays, the world's fourth largest bank. Should your team listen?
The agile development community gave up on the idea of 'approving' specifications and designs about 10 years ago. The next thing to go may just be the when-to-ship decision. As software release schedules are increasingly compressed, here are three ways to rethink the ship/no ship decision.
Big conferences take you to Las Vegas, feed you well and feature keynotes in lavish ballrooms. Smaller events may lack the glamour but offer much more camaraderie. The end result is a much more productive use of your time, a more valuable group of new colleagues and a more robust to-do list.
Imagine you're working on a major project such as Healthcare.gov. Suddenly, you realize there's no way the software will be done on time -- or even work. What do you do? Hear how veteran testers, project managers and developers tactfully handle such situations.
The idea behind the #NoEstimates approach to software development isn't to eliminate estimates but, rather, to explore other ways to solve problems without specifically asking, 'How long will it take?' Here are five real-world examples of teams that are doing just that.
In last week's post, I discussed why dev/test can be a good first use of cloud computing. Without rehashing the entire post, it's clear that dev/test is often hampered in its activities by the difficulty of getting enough computing resources to its job.