{"id":8090319,"date":"2019-08-11T13:42:55","date_gmt":"2019-08-11T20:42:55","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=agile-games&p=8090319"},"modified":"2024-07-18T10:27:49","modified_gmt":"2024-07-18T17:27:49","slug":"art-gallery-retrospective","status":"publish","type":"agile-games","link":"https:\/\/agilealliance.org\/agile-games\/art-gallery-retrospective\/","title":{"rendered":"Art Gallery Retrospective"},"content":{"rendered":"\n

This is a retrospective technique I learned from Esther Derby and Jerry Weinberg. I’ve extended it a bit differently into the analysis and deciding what to do portions as they were using the technique as a debrief mechanism for an activity in the PSL course. This technique is particularly useful for multi-team\/large groups. It will take about 120 minutes to run in full. One may notice it has similarities to the Sprint Mural<\/a> written up by Geoff Watts.<\/p>\n\n\n\n

Gathering Data<\/h3>\n\n\n\n

After opening the retro, have everyone stand and get close to those with whom they work most closely. This creates clusters that may cross teams or groups or you may find some people working in isolation (a cluster of one). As the facilitator, have these clusters get a flip chart and markers.<\/p>\n\n\n\n

In these clusters, the group represents how they see the work processes of the group from their perspective. They may draw a picture that metaphorically represents what they see, a diagram that describes the process, or if they are more comfortable, simply let them use words.<\/p>\n\n\n\n

At the end of this portion, let people wander the art gallery (so they can see what was created as for large groups the diagram may become far away and details will have been missed). Then each cluster debriefs what their ‘art’ represents. (This is where the portion at PSL stopped and then moved into a learnings debrief.)<\/p>\n\n\n\n

Gain Insights<\/h3>\n\n\n\n

Now each group returns to their art and annotates a few problems they see as well as a few items that worked well. They can make these additions to the drawing\/diagram or written words that tie to portions of this. If the latter, it may be helpful to have them as sticky notes of a particular color, particularly if the first piece of art was all words. Again, debrief these items collectively.<\/p>\n\n\n\n

Decide What to Do<\/h3>\n\n\n\n

At this point, allow each cluster to go around to each piece of art and offer up ONE idea they think will help this other cluster. These get written on a different color sticky than any used for identifying the problems. (In a retro I held, I had a problem with the collective team working together, so it had to help that the offering cluster would do for the other.) Think of this moving around to each piece of art as sort of a world caf\u00e9 visit with the art serving as the topics.<\/p>\n\n\n\n

Then each cluster returns to their own piece of art and decides which of the offered ideas they will use or if the offers inspire something else they want to try. The clusters report on what each one will collectively do. At this point, I generally have them make them SMART: Specific, Measurable, Attainable, Relevant, and Timely (when they expect to report it being done). <\/p>\n","protected":false},"excerpt":{"rendered":"

This is a retrospective technique I learned from Esther Derby and Jerry Weinberg. I’ve extended it a bit differently into the analysis and deciding what to do portions as they […]<\/p>\n","protected":false},"author":5055153,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","game-category":[],"game-tag":[2139,1881],"class_list":["post-8090319","agile-games","type-agile-games","status-publish","hentry","game-tag-art","game-tag-retrospectives"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\n\t\t\n