While the definition of Minimum Viable Product may work us into a tizzy, the goal behind it is extremely valuable for product companies: to rapidly learn what your customers want. Learning what your users want before you build it is good product development. Make sure when you do invest in a feature or solution, it’s the right one.
Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.
The concept of test management sits awkwardly in agile, mostly because it’s a construct derived from the time when testing was a post-development phase, performed by independent testing teams. Agile, with its focus on cross functional teams, has sounded the death knell for many test managers. While test management is largely irrelevant in agile, there is still a desperate need for test leadership.
When scaling agile principles through rituals it's important to constantly evaluate and evolve those rituals. This article provides examples of experiments that focus on developing team behaviors.
This article explores how the Ericsson ICT Development Center Eurolab applies Kaizen and agile to develop products with around 100 professionals from all related development and product areas. 4
In the book exploring the practice of antifragility Si Alhir and Donald E. Gould collected experiences with and perspectives on applying antifragility.
Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set.
The book Real World Kanban by Mattias Skarin provides four case studies where kanban is used to visualize, provide insight and improve product development.
The book Save our Scrum provides advice for teams to implement Scrum. It explores what teams that are having difficulties doing Scrum can do to get out of trouble find better ways to use Scrum.
This article introduces a visual modeling technique to describe and specify the application’s execution architecture, and explores the usage within Philips Healthcare. 4
How the Dutch Railways made the transition from large use cases completely written before development to Use Case 2.0 and why this helps them to deliver apps faster and with the right business value. 1
This article describes the change that was done to support growth at Seamless Payments, based on Agile and Lean values and using a slimmed down version of SAFe that still maintained its core ideas. 6