Schedule


Loading

Koen Vastmans and Sven Cipido

Koen Vastmans

I started my career in IT in 1992 as a developer. After being involved in several development environments, using different technologies (mainly Java based) in different business entities, I switched to training and coaching in 2011, initially focusing on modeling and design, later on agile. I was full time agile trainer and coach for about 6 years, when I decided I wanted to be more involved with technical stuff again. So in 2018 I started focusing on processes in a DevOps context: just technically enough to understand what's going on, without the need to actually do it hands-on. But once agile coach, always agile coach? So in that same year I started developing my first serious game, together with a former colleague (the Scrumban simulation). At the end of 2019 I started my secondary occupation under the name SimuLearn, to offer products and services using simulations and serious games. To date I created several serious games and simulations, focusing on learnings in an agile and DevOps context. At this moment I am still working on more agile related games, some of which in co-creation with other people.

@Koen_V

simu-learn.net

simulearn.koen@gmail.com

Sven Cipido

Already been active in IT since 1995 and as Scrum Master since 2007. At this moment, besides being a Scrum Master, I'm also a trainer at Ordina and the Competence Lead facilitation and gamification. As for facilitation, I'm in the process to become a certified Facilitation trainer for ICAgile. Gamification is easy. I'm a Lego Certified Facilitator in the Lego Serious Play method. I love to use games in my daily job as Scrum Master and in my trainings. Games could be everything, from Lego to Team3 over whatever. I also brought The Serious Gamers lab to Belgium. At last, I'm the co-author of 1 book and helped with some community translations of a few books under the Guidance of Yves Hanoulle. And at this moment, together with Koen Vastmans I'm creating my first Agile game, which we hopefully can present at the XPDays.

twitter logo@cipidos

website iconhttps://www.facebook.com/svencipido/

email iconagile@svencipido.be

Session: CI-CD-QA: Continuous Interruption, Continuous Delay, Quite Annoying

A game about software delivery and the role of PO's, release managers and security officers

If I ask you what the abbreviations CI, CD and QA mean, you will probably say Continuous Integration and Continuous Delivery/Deployment, 2 terms that are key in DevOps, and Quality Assurance. Quality is very important and has many faces. Release management and information security officers have their specific view on quality. Now, if these people only fire their requirements on the software delivery teams, CI, CD and QA will have a different meaning... In this session we will let you experience using a game with cards how annoying these continuous interruptions and continuous delays can be and how you can address quality requirements differently.

Full description

In a traditional organization with a long history of calendar based software releases, quality is enforced in a very rigid way. Release managers and information security officers fire away their quality requirements. When dealing with long release cycles (waterfall-ish, project based) this could still work to some extent, but when you want to evolve to frequent deployments and release on demand, what will the impact be if these people keep firing their quality requirements from their trenches? We created a safe learning environment to experience exactly that, and also what the consequences are if you delegate (part of) these quality responsibilities to the development teams themselves. This session uses a game with cards. 4 to 5 participants per game will pick up one of the predefined roles. The aim of the game is to play your cards as quickly as possible. This goes in 2 rounds, in 2 ways: - the waterfall-ish way - the team way

Outline or timetable

This is a card game, for 4 to 5 participants. The cards will contain certain development and security related terminology. We will provide some kind of glossary per table, but prior knowledge about development and security and the terms used, is always welcome. We will be able to serve 10 games, so 40 to 50 participants should be able to join.