Agile development starts with small Scrum teams tackling small problems. After some initial successes the organization gets more ambitious, and tries to scale Agile, getting more teams tackling bigger problems. At some point these endeavors run headlong into finance and governance structures from a different era, designed with huge projects in mind, and it usually doesn’t end well.
For decades, product development has been focused mostly on the speed and efficiency of delivery. So now we are stuck in the quagmire of talking about the methods and activities of delivery rather than focusing on the actual goal – delivering high value to the customer.
Gojko Adzic is known in the Agile software development world for his work on requirements presented in his book “Specification by Example – How successful teams deliver the right software”. In this small and easy to read book, he focuses on a single tool that could be very useful for Scrum teams: impact mapping.
Scrum Expert Copyright © 2009-2024 Martinig & Associates