The Latest

When agile teams are working, the all-important stories stay on the wall (or, worse, in a tool). They sometimes get seen, touched, and loved only once a day. Why are the stories not the focus of the work?

The Agile Manifesto says we value people and interactions over processes and tools. Yet when we talk about the agile methods, we usually end up talking about processes.

For any continuously improving organization, certain actions are commonly applicable when going through large amounts of change. Dan Barker walks through the five steps to transformational change that he's found to be crucial for moving to DevOps processes.

Successful agile software development depends on a healthy product backlog. Too often, teams attempting to adopt an agile methodology for a project with a new product owner struggle in their transition due to a sparse product backlog.

Teams can hesitate to adopt agile practices, even when there’s a clear desire for transformation at the executive level. But there are strategies for coaching agile-skeptical teams into an agile mindset. 

Many organizations ignore culture and overfocus on picking and implementing the right tools. However, these tools have underlying cultural assumptions. If the current culture does not support these assumptions, then automation will only have limited success, or even fail altogether. 

The primary goal of DevOps is to provide velocity and quality through improved collaboration. However, without a tailored measurement framework to direct efforts to the problems that matter to the customer and the business, these goals are meaningless.