The Latest

There are many companies today implementing agile and DevOps practices, usually enabled by a microservices architecture. Most of them are focused on continuously delivering value to their customers within the boundary of a time-bound sprint. 

When agile transformations fail, many agilists blame their executives for not caring about or understanding agile. However, few people focus on the different languages that IT and business people speak, and the different outcomes that both sides desire.

Trying to achieve real continuous deployments into production is hard for everyone, but it’s especially hard for highly regulated or government projects. 

Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Even well-groomed, refined stories, framed with typical, alternate, and error scenarios and gracefully described in well-formed Gherkin, continue to encounter all sorts of bugs.

Have you ever been to Japan and noticed that their railway system is incredibly efficient? As places like Tokyo continue to expand and the cost of living rises, more and more people rely on trains that start hours away from the city to arrive on time.

Organizations are moving to DevOps to build and deploy software more rapidly. But as they break down organizational silos to bring together testing, development, and operations, they often avoid or exclude security in their transformational efforts.