Release Management

Better Software Magazine Articles

The Danger of Testing "Only" Stories

Finding defects late is a common issue when teams don't consider levels of precision or detail. You must take into account how stories and features fit into the system. In this FAQ column, Janet Gregory tells you how you should remember the big picture—even while testing the small stuff.

Janet Gregory's picture Janet Gregory
Quick, Before We Release

Matt Heusser presents ten key factors to establish a team cadence—the time between running tests and getting a product into production. The shorter the cadence, the less time spent in test/fix/retest land, and the more time spent working on new features.

Matthew Heusser's picture Matthew Heusser
Explosion of Mobile and The Internet of Everything

Better Software magazine editor Ken Whitaker highlights the contents of the July/August issue with two articles featuring mobile and wearable intelligent devices and the challenges they present to typical software development.  Ken also provides information on ordering a print copy of Better Software.

Ken Whitaker's picture Ken Whitaker
Developing Custom Apps for the Cloud

With the cloud providing tremendous freedom like instant deployment of updates, you're definitely going to have to adjust how you develop and deploy apps. Pete and Matt have created a list of things you need to consider when developing apps for the cloud.

How DevOps Drives the Agile ALM

One of the most effective approaches to DevOps involves moving the automation of the application build, package, and deployment upstream to the beginning stages of the software development lifecycle—an industry best practice long before DevOps became as popular as it is today.

Bob Aiello's picture Bob Aiello Leslie Sachs
You Can't Be Agile without Automated Unit Testing

Agile projects assume that test planning, test creation, and test execution take place throughout a project's lifecycle. So the need for unit testing (and especially automated unit testing) can't be ignored and should be considered as a key responsibility of the entire team—not just the software developers.

Gil Zilberfeld's picture Gil Zilberfeld
The $440 Million Software Bug

In August, Knight Capital Group lost $440 million in one day. But there weren’t any traders to blame—at least no human ones. The loss was the result of a software system upgrade gone awry. What can we learn from this and other software catastrophes in the financial sector, and how can we prevent them in the future?

Traditional Test Engineering, Your Days Are Numbered

In the first installment of this article, Dr. James Whittaker discussed turning testing on its head—to revitalize and improve the value of late-stage testing. James also discussed ideas behind empowering your dogfooders, testers, and the crowd to significantly and efficiently improve software quality. In part two, Jason Arbon discusses the research and engineering experimentation behind realizing these ideas into new tools and processes.

Jason Arbon's picture Jason Arbon
Agile Code for Agile Teams

What makes a team agile? Is it in the way it plans projects or how it engineers its products? In this article, Steve Berczuk explains how agile code and technical practices can help a team stay agile across the product lifecycle.

Steve Berczuk's picture Steve Berczuk
Raising The Bar For Configuration Management

Configuration management (CM) has matured into a "must-have" discipline. But, many CM experts have failed to keep up with what's required to implement CM best practices. Find out what needs to be done to raise the bar for CM.

Bob Aiello's picture Bob Aiello

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.