5 Practices for Making Your Agile Feedback Loops Work
The following is an excerpt from Gil Broza’s new book, The Agile Mind-Set: Making Agile Processes Work.
Do you ever get asked to do something, and when you show your results the response is something like, "That's not what I meant…"? Do you sometimes pour your heart and soul into an amazing idea you've had, only to discover people don't even understand what you're talking about?
Agile thinking came about in the mid-1990s as a response to the troubling success rate in software development. Across the industry, many features went unused and entire products fell flat. How could intelligent, well-meaning professionals produce such grim results?
The answer to that was relatively simple: Their methods didn't allow for timely, actionable feedback. Core beliefs in the reigning methodology of the time (waterfall) were that users know what they want and need, you can get that information usefully out of their heads and it will remain relevant once you're ready with the solution. That might be true for constructing the Golden Gate Bridge, but not in many development situations.
Actionable feedback loops are at the core of agile
A central principle of the agile mindset is to have short, actionable feedback loops, and then to tighten them over time. How do agile teams typically implement this principle? Work closely with your
Please log in or sign up below to read the rest of the article.
|
"Judge a man by his questions rather than his answers." - Voltaire |




