Handling bugs in Agile - Bradley Bug Chart

Should be this.

1. Is it a bug? If yes, proceed and fix it first based on priority, else get it into the product backlog.
2. If it is a bug, can it be deferred to next sprint? If no, proceed below, else move to next sprint. If it is a bug and needs to be addressed in the current sprint, then proceed below.
3. Can the bug be fixed within 2 hours? If yes, fix it and forget rest.
4. If no, then get it into the current sprint backlog and remove another item of approx size.

Mulesoft - Eric Stahl on Youtube

Shamrock Mapping - Mike Coon

1. You may use the Shamrock mapping for retros, or to elaborate on an Element's Dynamics along Autonomy and Mastery.
2. This is probably derived from Daniel Pink's Drive -- Autonomy, Mastery and Purpose. 
3. Place an element (as in this case "Compile") along Autonomy - Y Axis, and Mastery - X Axis. 
4. Then, identify the "accentuators" and "Drags" on both axis. 
5. Lift are those that allow the element to move to greater autonomy, whereas weight brings it down. 
6. Likewise, Thrust propels the element along Mastery, while Drag hold it back.

Changing Organisational Culture - Michael Sahota

http://agilitrix.com/2018/07/change-organizational-culture/

Wardley Maps

Wardley maps (by Simon Wardley) have been in for a while. I have attended a session too by Neil Killick in Melbourne (shall upload the slides / snapshots).

https://blog.gardeviance.org/2015/02/an-introduction-to-wardley-value-chain.html