Lessons learned from playing terrible games (part 2)

What do you think about when you hear the term “gamification” applied to your job? An employee-of-the-month challenge? Maybe some badges you can achieve? A public team ranking? The term “gamification” always sounded very shallow to me.

But to make work engaging and challenging (like a good game!) means true cultural change. Some of that change starts at the top, but it really is something we can all influence. Most people can spot a badly designed game without effort: it simply does not *feel* good to play. But we are not often encouraged to listen to our feelings to figure our if we’re in a badly designed job.

In this workshop, we will spend time playing games – terribly designed games unfortunately – and learn from that experience to improve our own work environment. It is aimed at developers, product owners, scrum masters and management alike because every stakeholder has a role to play in the real-world game called software development.

During the day we will cover quite a few topics: assumptions, estimations, prioritization, feedback loops and more…

Will you step up to the challenge?