Gojko Adzic is a partner at Neuri Consulting LLP. He is the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. Gojko’s book Specification by Example won the Jolt Award for the best book of 2012, and his blog won the UK Agile Award for the best online publication in 2010.
As a consultant, Gojko has helped companies around the world improve their software delivery, from some of the largest financial institutions to small innovative startups. Gojko specialises in are agile and lean quality improvement, in particular impact mapping, agile testing, specification by example and behaviour driven development.
Presentations by Gojko Adzic:
Agile Israel 2018 Conference, Tuesday, June 19, 2018, 09:15
Agile Israel 2018 Conference, Tuesday, June 19, 2018, 10:15
Have you struggled to split user stories into small but valuable chunks? Do you have problems prioritising stories or getting a commitment from business stakeholders on what they want to achieve? Do you have issues deciding when a story is done or how many other stories you really need to achieve a business objective? Are you managing large amounts of stories that are problematic to estimate, prioritise or plan for? If so, join this interactive workshop and bring your product owners and business sponsors to learn how to get the most out of user stories.
The participants of this interactive workshop learn about the basics of Impact Mapping, and try it out in practice on several realistic examples to understand the key facilitation techniques and learn how to run and apply Impact Mapping sessions in their organisations.
Impact Mapping is a strategic planning technique that helps organisations manage flexible roadmaps for iterative delivery, by clearly communicating assumptions, helping teams align their activities with overall business objectives and make better delivery decisions. Impact mapping can help you build products and deliver projects that make an impact, not just ship software.
Key learning points
- Fight a huge backlog with 500 crap stories
- Prioritise with multiple competing stakeholders
- Avoid a user story stream of consciousness and create a big picture for prioritisation
- Establish a good reporting structure on outcomes rather than just monitoring velocity and activity
- Get agreement from the whole team and the business sponsors about which user stories are useful and which are just noise
- Enable business sponsors to benefit from flexible scope and avoid water-scrum-fall
- Effectively prioritise based on value
- Avoid pet features
- Run impact mapping sessions