Requirements Engineering Game in Action
In my last post, I told you about the rocky road to creating a game < Requirements Engineering Game - Theory is dead, long live the game! >. I'm sure you're all eager to see how it fares in the real world!
The game begins with the participants setting requirements for each other. This is done verbally, through hand-drawn sketches, and in writing. Just like it often happens in 'real' life, without further instructions and with plenty of room for interpretation. It's always interesting to see how much the documented requirements deviate from the original vision after three rounds of submission.
Even the participants of the Full Stack Developer Program in the news - TechFace could hardly hide their astonishment. Highly motivated to improve in the future, we jumped into the game. We formed two groups of three participants each.
In total, we played four full rounds in four hours. Each round consists of the following four moves:
- Understanding the context
- Identify and define requirements
- Visualize
- Validate
In each round of the game, you not only attract new stakeholders but also unplanned events that can sometimes throw a wrench in the works.
However, supporting methods can always be used to avert impending disaster. After five intensive hours, the participants not only learned a great deal about requirements engineering, but also had fun learning!
Are you interested in improving your RE skills while having fun? Then the RE Game might be just right for you:
- Number of participants: Minimum 6, Maximum 20
- Time required: 4-5 hours, the game can also be played longer to learn even more.
- Prior knowledge: None required. The game adapts to the participants' prior knowledge.
Interest aroused!
Contact us via our contact form
