Releasing in small batches is a good way to achieve quick feedback in your sprints, but these pieces don't have all the features users need. Providing consumable value is turning those small bites into a meal, and it’s worthwhile to estimate what it will take to deliver that—asking, “What consumable value do we expect to achieve, what duration and cost should we plan for, and how likely is it that the plan will succeed?”

When teams are transitioning to agile, making so many changes all at once can be hard. But just like with your health, in order to see progress, you have to commit, and when something starts working, you have to keep it up. Following this prescription should cure a team's agile ills and get its program on the road to recovery.

The experience of implementing agile in a company of thousands of employees differs widely from that of a company of hundreds. Although the risks can be greater, the rewards can be, too. If you work in a small company that is interested in transitioning to an agile workflow, consider these strategies for implementing agile in small organizations.

It’s the distinctions between agile and traditional software development approaches, as well as the adaptability of testers in these very different environments, that makes agile testing different from traditional testing. Agile demands more from its testers, and, in turn, it values them more, too. Let’s look at five main things that make an agile tester’s life different from that of a traditional tester.