“Successful problem solving requires finding the right solution to the right problem. We fail more often, because we solve the wrong problem than because we get the wrong solution to the right problem.” (Russel Ackoff, 1974)
Unfortunately, most of the software development projects we are dealing with are so called “wicked problems”, where the definition of the problem changes with the point of view from different stakeholders, and also over time. Since the problem cannot be described definitely, there is also no point in describing a definite solution. Instead you need to optimize the solution until it is “good-enough” from all involved perspectives.
Agile projects continuously strive for optimizing the scope to reach “good-enough” solutions. They try to identify key stakeholders and their goals, and then derive useful scope to implement for supporting these goals.
There are different methodologies in agile product planning that help with deriving scope from goals. Some of them are:
SpecLog is designed to build and maintain the product backlog as more than just a list of epics and user stories: