The Latest

Choosing agile metrics that will be most effective in measuring application success is a challenge, and then tracking those metrics can be tricky as well. But with a good strategy, agile metrics can be a powerful tool for sharing the team’s progress and identifying existing and possible roadblocks. These meaningful metrics can reduce confusion and bring clarity throughout the application development cycle.

Faster DevOps processes also create new challenges. It was difficult enough to add security into a traditional waterfall software development lifecycle with monthly or quarterly releases, but now software updates are released several times a day! What can developers do to build and maintain more secure applications? Here are some ways to encourage better security practices throughout the DevOps lifecycle.

DevSecOps is about more than just the tools—it is an organizational, operational, and strategic transformation. So, as a “thorough or dramatic change in form or appearance” across the three main pillars of an organization, how can we expect a DevSecOps transformation to take place overnight?

Nearshore software development—or working with teams in similar time zones—have different challenges from teams that are collocated. They might find it easier to work in a traditional, hierarchical structure, but agile practices are actually still an ideal way to work through these challenges. Here's how an agile mindset can help nearshore development teams improve communication, organization, and processes.

The learning pattern Shu-Ha-Ri—originally from the Japanese martial art aikido—has been adapted to apply to agile adoption, with the three levels sometimes interpreted as imitate, assimilate, and innovate. However, it is easy to oversimplify Shu-Ha-Ri, which can slow or halt your agile adoption. Agile is not just another process—it requires changes to our mindsets. Here's how to approach this as a cycle of learning.

We hire for programming language skills or framework experience, but these are the kinds of things that any developer should be able to pick up quickly. David Bernstein says we should be hiring based on talent instead, and mentoring developers to write code that can be maintained and extended more easily. These critical skills are best learned on the job, which is why mentoring is so valuable.

With traditional software development methods, you are betting that end-of-lifecycle testing will let your team correct all risks, but experience has taught us that this seldom happens. With agile, you are incrementally reducing risk with every iteration and release you do, mitigating risks as you go. This article examines each of the value statements from the Agile Manifesto to illustrate how agile ultimately helps us reduce product risk.