The Latest

Open agile workspace The Ideal Workspace for an Agile Team[article]

If your agile team is all wearing noise-canceling headphones and stepping outside for conference calls, you have a problem. An agile workspace doesn't only mean putting everyone in the same room. The layout, configuration, and seating must be conducive to sustainable teamwork. Here are some tips about what an agile workspace is—and isn't.

Joel Bancroft-Connors's picture Joel Bancroft-Connors
Technical writing Fitting Technical Writing into Agile Development[article]

As teams strive to move to a mature agile process, technical writers must adapt as effectively as the development personnel. This new agile process demands that knowledge dealing with software or product releases is only sparingly documented up front, making the technical writer's job of gathering information much more dependent on talking with people over reading requirements.

Robert Spielman's picture Robert Spielman
Martin Chikilian Why It’s Critical to Invest in DevOps Right Now: An Interview with Toptal’s Martin Chikilian[interview]

In this interview, Martin Chikilian, lead director of engineering at Toptal, digs into current DevOps trends and whether DevOps is just a fad. Martin explains why the gig economy is so big for DevOps, why there are so many unfilled positions, and what continuous concepts mean for software.

Josiah Renaudin's picture Josiah Renaudin
Pencil to paper Document Why as Well as What: Finding the Purpose of Your Software[article]

Code can express what we want to accomplish, but it’s a little more difficult to express why we’re doing something in the first place. The people who maintain code are often not those who originally wrote it, so documenting why helps set a context and gives clues as to what the author was thinking when they came up with a particular design, making developers' jobs easier.

David Bernstein's picture David Bernstein
Release management Why DevOps Still Needs Release Management[article]

Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation.

Adam Auerbach's picture Adam Auerbach

AgileConnection is a TechWell community.

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