Teams, and Scrum Masters often want to “hide” the problems they face by fear of upsetting the stakeholders. But is that really how you foster change? In this episode we listen to a story where showing the problem to all involved helped create the necessary change.
About Mark Thuun
Mark started as a software developer when he learned some basic PASCAL from his dad taught. He was then 7-8 years old. Mark has been working as a Scrum Master since january 2015. For 2 years he worked with teams in the biggest telco in Denmark, and currently works for the danish national lottery.
You can link with Mark Thuun on LinkedIn
I have an idea for you. Every day of the week, your podcasts are on different things, e.g., Wednesday’s theme is change. Why not add a tag for each day’s theme? So if I listen to today’s podcasts, and I want to see what others have said about managing change, I could just click on the tag.
PS “Pascal” isn’t an acronym, so it should be in proper case, not upper case.