How often to do impact mapping? Should it be done for every team?

[Benjamin Brachert]

Hi,

how often do you do impact mapping sessions?

Let's imagine you are part of an internal IT department with 7 cross functional cross component teams within a larger Organisation. The organisation works in Scrum mode.

When I have a look at the Impact Mapping book, it is a kind of Milestone activity. But what would you do when you don't have milestones but only Sprint Reviews.

Would you create one impact map per team? Or even pick a bigger goal? Or would you create a "Large-scale map" like the book describes?

Would be happy to hear some experiences of your daily work.

Thank you

Benjamin

[drob...@gmail.com]

Hi

If you got Feature Teams (Crossfunctionall and Crosscomponent) then when it  is about scaling:

Multi Team Refinement in Large Scaled Scrum is a nice place.

Check this video out:

Outcome based Product Backlog
https://www.youtube.com/watch?v=kEZIMzIXMmc 

 If you're still not there for e.g you still got component teams with "product owners" per each team then you have to try to move to feature teams.

Meanwhile what I do is introduce the practice to highlight all the sprint goals of all teams in impact mapping form

https://www.linkedin.com/pulse/power-sprint-goal-examples-b%C5%82a%C5%BCej-drobniuch?trk=related_artice_The%20power%20of%20a%20Sprint%20Goal%20(examples)_article-card_title

BR

Błażej Drobniuch

[Benjamin Brachert]

Yes, we are Feature Teams.

Sounds like you have some experience with LeSS. Do you work with all Teams on one goal or do you work on goals in parallel?
I can imagine when you define smaller WIGs that you work on WIGs in parallel.

Is that true?

Thanks

[Benjamin Brachert]

Would you say those WIGs which are mentioned in the video https://www.youtube.com/watch?v=kEZIMzIXMmc

are the measurements like described in chapter "Preparation step 2: Define good measurements" of the Impact Mapping book?

Some kind of milestone measurements.

Otherwise if you define a WIG and your able to deliver one "What" after one sprint, you wouldn't see that the WIG is getting affected (either positove or negative) So, when is the best time to have a look at the WIG or the measurements again?

[drob...@gmail.com]

You're right!

Product Backlog Goal (simplified):

Increase transparency on near future (about what we're going to build in the Product)

So if you use Outcome Based Backlog a nice way to increase transparency would be:

When we are working on multiple business goals/milestones simultaneously is to add them as W.I.Gs and define measurements for them.

Agile Goal (simplified):
Always work on what's most important (valuable).

What supports this is to serial WIGs (aim to work at one WIG at a time) a nice article from Gojko on that topic

https://gojko.net/2017/12/11/christmas-prioritisation.html

BR 

Błażej

https://pl.linkedin.com/in/drobniuch