{"id":3760,"date":"2024-02-11T08:20:54","date_gmt":"2024-02-11T07:20:54","guid":{"rendered":"https:\/\/berlin2.davidweb.pro\/?p=3760"},"modified":"2024-04-16T10:24:30","modified_gmt":"2024-04-16T08:24:30","slug":"dysfunction-mapping-michael-lloyd-58-hands-on-agile-meetup","status":"publish","type":"post","link":"https:\/\/berlin2.davidweb.pro\/de\/dysfunction-mapping-michael-lloyd58-hands-on-agile-meetup\/","title":{"rendered":"Dysfunction Mapping \u2014\u00a0Michael Lloyd\u00a0at the 58. Hands-on Agile Meetup"},"content":{"rendered":"

TL; DR: Dysfunction Mapping w\/ Michael Lloyd<\/h2>\r\n\r\n

In this fascinating talk, Michael introduced the concept of dysfunction mapping, a tool developed over years of trial and error aimed at creating a repeatable way to find, theme, and ultimately solve organizational dysfunction.<\/p>\r\n\r\n

\"Dysfunction<\/p>\r\n\r\n

???? Watch the video now<\/strong>: Dysfunction Mapping \u2014\u00a0Michael Lloyd\u00a0at the 58. Hands-on Agile Meetup<\/a>.<\/p>\r\n\r\n\r\n\r\n

???? Your single best investment to improve your professional standing<\/strong>; order the Scrum Anti-Patterns Guide book<\/a> now!<\/p>\r\n\r\n

\"Master<\/a><\/p>\r\n\r\n

The most popular discussion on LinkedIn last week was<\/strong>: Looking to Get Hired as a #ScrumMaster or #AgileCoach<\/a>?<\/p>\r\n\r\n

???? Shall I notify you about articles like this one? Awesome! You can sign up here for the \u2018Food for Agile Thought\u2019 newsletter and join 42,000-plus subscribers<\/a>.<\/em><\/p>\r\n\r\n

???? Join Stefan in one of his upcoming Professional Scrum training classes<\/a>!<\/p>\r\n\r\n\r\n

Abstract<\/h2>\r\n\r\n

Dysfunction Mapping is a tool developed over years of trial and error, aimed at creating a repeatable way to find, theme, and ultimately, solve organizational dysfunction. By following these steps, you can more quickly identify the biggest wins, develop a solid action plan, and measure if you're really achieving outcomes that matter. It's not a silver bullet, but it can give you some structure to creatively solve problems while also making your value visible and your goals clear.<\/p>\r\n\r\n

During the Q&A part on humble planning, Maarten answered the following questions, among others:<\/p>\r\n\r\n

    \r\n
  • What about other common iterative change management strategies? Which have you tried & why have they failed for you? Why do you think they failed in your experience?<\/li>\r\n
  • Curious why the mapping moves from Right to Left (+2)<\/li>\r\n
  • A system diagram of influencing factors often contains reinforcing loops - how do we make that work with dysfunction trees that do not allow for loops?<\/li>\r\n
  • Do you worry when you have identified a \u201cdysfunction\u201d that you could go deeper into and perhaps get more possibilities? I am thinking of \u201cThe Dangers of the 5 Whys\u201d and the advantages of systems thinking instead of reductionist cause-effect models.<\/li>\r\n
  • This seems focused on practices\/processes. What is your approach to the foundational issues of mindset, values, behavior & culture?<\/li>\r\n
  • Are the symptom cards available on the Honest Agile website?<\/li>\r\n
  • How do you define a purpose statement for dysfunctions? How do we get the team\u2019s buy-in for these statements?<\/li>\r\n
  • How do you prioritize what to pick up first\/next?<\/li>\r\n
  • I am curious about the clustering of symptoms and finding the real causes. Is it a typical root cause analysis?<\/li>\r\n
  • Do you identify impacts or the symptoms\/dysfunctions or do anything else to understand how to prioritize which to address? Understanding the impact seems to be a missing piece.<\/li>\r\n
  • Are you sharing all your written-down symptoms with the team? \u201cThis all is what you are doing wrong\u201d...<\/li>\r\n
  • The mindset-values-principles-practices slide could be interpreted as there is only one mindset.<\/li>\r\n
  • Do you think the Scrum anti-patterns Stefan identified could automatically fill your diagram?<\/li>\r\n
  • How do we order the implementation of the solutions?<\/li>\r\n
  • Is it, in your opinion, reasonable to include the DM in the OKRs?<\/li>\r\n
  • Symptom metrics are mostly output metrics? Could we also measure against the root cause?<\/li>\r\n
  • How do you create a single Sprint\/cycle goal when doing Kanban with, e.g., 4 product goals?<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n\r\n

    Watch the recording of Michael Lloyd\u2019s dysfunction mapping session now:<\/p>\r\n\r\n