Skip to main content

Dragonvale, bringing the Fun; yet a poor simulation of markets

I had a wonderful Christmas.  My nephews got me addicted to the Dragonvale game.  A land where one breeds dragons of various types - did you know, dragons are very hybidizable (I'm sure that's not a standard dictionary word).

Dragonvale - iOS simulation game.
To build up to a high enough level to purchase a breeding cave one must build treat farms, dragon habits and grow crops.  For this there is an internal game monetary market.  The prices of these goods are set by the game designers (I'm assuming it is not a true "free market").  The game does not have a sane and balanced market pricing system.

The objective of any game designer is to get you to play and have fun.  That is objective number one - design in the fun-factor (see MIT Technology Review's Exploiting the Fun Factor).  A secondary objective is to build a game where people will spend money - real cash in exchange for virtual goods.  This is one technique for the game company to make money (in app purchases of virtual goods).  Luckily the iOS designers created a way to protect my mother's credit card from her grandkids desire for dragon gem stones.  This game market place is big business $16 billion in 2010, quite a bit larger than the movie ticket sells for the same time, $10.6 billion.  This is perhaps one of the fastest growing industries, starting in the early 1970s (Pong by Atari was a 1972 game smash hit).

Dragon Habitats
"Why are games important? Because people will reward businesses that cater to their appetite for fun, providing commercial incentives for every incremental improvement in the technology that delivers that entertainment. And game designers are masters at stoking that appetite. Every designer from Pong on has deliberately tried to make their games addictive, with a grab bag of psychological tricks that include humor, storytelling, and reward systems similar to the payoff schedules that lure gamblers. And some designers succeed, serving up jolts of pleasure in such a way that users can't stop coming back for more."                                      -- Stephen Cass  "Exploiting the Fun Factor"
An example of the unbalanced game market pricing is that a treat farm cost $100 (coin of the realm).  With this treat farm a land owner such as myself may grow crops to feed dragons.  Now at a sufficient level (experience points) an owner is given the opportunity to upgrade the treat farm to a larger farm, capable of growing the same crops but with an even larger selection of crops costing more and providing various levels of food.  The cost of the upgrade is $25,000.  The cost of purchasing out-right is $25,000.  This unbalanced transaction in the economic system of the game concerns me.


The net effect after the upgraded transaction is a large treat farm with total cost of $25,100 (100 original cost + 25,000 upgrade).  The net effect of purchasing two separate farms one small (100) and one large (25,000) is that the owner is capable of producing twice as much food, for the same fixed cost (excluding real estate area which is a limited supply).  However after the purchase of a second treat farm if the owner wished to recover land area they may sell the smaller treat farm and recover 1/2 of the original purchase price of the farm ($50).  Making a true apples-to-apples comparison then one has an upgrade option of $25,100 versus an option of purchasing and selling cost of $25,050.  I call this an unbalanced market price for the farms.

Why would the game designers create such an unbalanced system.  They are encouraging the land owner to use limited resources money and land space in unnatural ways.  There is both a monetary reason to consume more space (purchasing two farms vs upgrading a farm) and poor land use practice to purchase two farms rather than upgrade.

Now some people will see this as an opportunity to game the system.  To take advantage of this inequity in the economic system to make more money on similar capabilities of production.  Yes this type of inequity exist in all markets.  Yet my concern is that if we are teaching our young children to make poor (non-sane) economic decision at such a young age, what will become of these children when they have they own credit cards.  Will they believe they can take a cash advance from the card and put it in the bank to earn interest at say 4% and then pay back the credit card company?  A system of kiting loans rarely works out for the credit card customer, banks are not as nieve as young people some times believe.

The book that started an economic reasoning
nation, published in 1776 by Scottish economist
and moral philosopher Adam Smith.
I believe that the game designer have not purposefully made this inequity in their game's economy.  They have just made simplifications and nice "round" numbers for the market place.  Thereby creating these non-sensical opportunities to teach poor money management techniques.  Now some people will believe that the young people who play these games may not be learning these poor finical lessons.  I do not.  I believe that the best way to learn something is to make it fun.  This is an area the game designers have excelled.  Their game is fun.  It teaches some good lessons and some poor lessons.  The thing with these fantasize world simulations is that they are very good at teaching lessons, I just wish they taught lessons Adam Smith could be proud of.


Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …