In many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost.
Lisa Crispin writes that you need to understand the purpose of a user story or feature. Start with the "why." You can worry later about the "how." The customers get to decide on the business value to be delivered. They generally aren't qualified to dictate the technical implementation of that functionality. It's up to the technical team to decide the best way to deliver the desired feature through the software.
When the tasks in the "Done" column needed more attention, the team created a "Done Done" column. Later, they created a "Done Done Done" column. In this article, Brian Bozzuto discusses how you can stop adding columns and honestly get to "done" without having to kid yourself.
Kirk Knoernschild discusses the subtle though significant ways that continuous integration can be leveraged—from helping to align IT with the business to enforcing architectural constraints—and shows that this fundamental aspect of agility is the defining and necessary element of a truly agile development experience.
Investing in a new product always involves risk. We may have targeted the wrong market segment, envisioned the wrong product or the wrong features, or the market may have changed by the time the product is launched.
Charles Suscheck compares the levels of productivity of Scrum and Kanban through a hands-on experiment that he and his team personally participated in. Learn the upsides and warnings about each practice to help you decide what might work best for you and your team on your next project.
Mike Kelly explains the following heuristic approach to help ensure your testing is roughly inline based on orders of magnitude across the various types of automation. It’s not a method for measuring effectiveness. Instead it’s simply a “smell” to tell you when you might need to take a little extra time to make sure you’re focusing your automated testing efforts at the right level.
In this personal experience story, Daryl Kulak relates the day he spent behind bars. He was there to participate in a program that pairs prisoners with software developers “from the outside” to explore the art and science of agile software development. “It’s like a code retreat,” Kulak notes, “except it’s inside a prison.”
Jonathan Lindo describes examples of automated test infrastructure utilizing both open source and traditional, independent-software-vendor-sourced software. In addition, he discusses new techniques for extending the value of automated testing by transforming the process from defect finding to defect resolution by reducing the effort required to document, reproduce, and troubleshoot the defects generated from automated tests.