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?
It seems that everyone is aflutter with DevOps, the shiny new panacea for all of our software ailments. What technical goodness can DevOps bestow upon us? What riddles does it unlock for us as technologists?
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.
Most teams that do agile development start with Scrum. And why not? Scrum is a proven method for focusing your team, ensuring that work adds value, and minimizing the risk with release. Then, after awhile, Scrum becomes stagnant.