Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
Circumstances for software development projects have changed tremendously during the past years. On the one hand, software is expected to solve increasingly complex problems within an ever growing number of domains. On the other hand, the advent of practices like continuous deployment allow for incredibly short release and feedback cycles.
How do we deal with these challenges from a software customer's or product owner's point of view when traditional methods of requirements analysis - possibly even the traditional definition of the term "requirement" itself - fall short?
In this session, I want to show how Impact Mapping, a technique developed by Gojko Adzic, can help us establish a view on requirements that is better suited to today's problems. By means of a concrete example I'll explain how to use this method and give some helpful advice for future practitioners.
Login to see the comments