This will be an interactive workshop where the Scrum Masters will be able to share their frustrations and experiences with others in a similar situation. The main purpose is to help Scrum Masters to work systematically with process improvement. One key point here is to understand the difference between “a real problem” and compliance with a model. Removing impediments may be seen as the main task of the Scrum Master, but how do we ensure that we attack the most important ones? How do we avoid sub-optimization? What kind of fact should we collect to understand the severity of the problem?

All good developers love writing code, but quite few of us take any pleasure in reading it. However, reading code has a lot of positive effects not many people are aware of. In this talk, I will tell you why and how you should use code reading to improve your coding skills.

Agile development requires trust, but will also create trust. Agile is a positive trust spiral. Non-agile development is based on distrust, and will create distrust. Agile development cannot happen until all stakeholders have turned the trust spiral around. In this workshop we will explore techniques to initiate trust in a not yet agile organisation. Using ideas from appreciative inquiry, we identify situations that initiated trust in us. We discuss the prerequisites, properties and results of the techniques used. Then we explore other situations where the techniques also could be applied.

I want to share why I think play and fun are critical parts to the culture that agile teams need to be grown and nurtured in.