Story Development & Scenarios
A little while back one of our agile coaches was shown a you tube video, it was of a gamer that had been up for 24hrs straight, and out of the blue appears something most unexpected. Is it a deer, is it a donkey, no ladies and gentleman it is indeed a ladder goat. You see a goat appears in the middle of the battle field, after the game has been played for 24hrs continually.
When the same agile coach studied with the master of story development Robert McKee, in London, to their surprise a number of software developers from a game house in the Netherlands were also learning the craft of story elicitation. Game developers take their stories seriously, and Hollywood take their successful stories from computing games even more seriously.
So when you’re in the midst of your story development BA’s, testers, & Product Owners determining your scenarios, asking why do I need to do this, and wondering why do I need to learn this? Just think Ladder Goat. Especially when you’re getting your head around the concept of Happy Sad, Mad & Bad and why they are important for your narratives.
Warning this video below is contagious, and a couple of words are considered adult content & controversial for the work place environment a couple of minutes into the video, watch it long enough and you too will be laughing, but when we look at this from the Agile perspective, how did the story development for this feature of the game take place? How were the scenarios developed?