Here is some in-game footage of Gravity Wave Premium in Action.  Three levels are featured with the game being played in Hyper Mode, the hardest difficulty setting.  It takes a little getting used to, but the Hyper setting is actually very straight forward once you've mastered it.  It does take a while though.  The easier play modes (Rookie / Normal / Master) should cater to more casual players.  The trick is to apply only short bursts of power.

The video quality degraded quite a bit in the upload to YouTube.  The game performs well on-device: a clean, constant 60fps on second gen iPod Touch and iPhone 3GS with full effects, and near 60fps on gen one iPod Touch and iPhone 1G/3G.  You can get performance up to a clean 60fps on the latter by turning off warp effects.  The warp effects are used in various places to deform space, for example around a worm hole or black hole, or when an explosion occurs.

For the last year, I've been using SCRUM at Pocket Kings here in Dublin. Although I finish up at Pocket Kings on the 28th of this month, I fully intend to continue using SCRUM for my own projects at Ideal Binary.

Version One is the SCRUM tool I've been using at Pocket Kings so that's what I'm familiar with. Once up and running it's relatively straightforward to use. It is an enterprise level tool though and if all you need is to track your own work (and not that of a team or group of teams), it may be overkill setting it up and hosting it.

My requirements are pretty simple. Essentially, I want a way to store my task estimates and also track my progress from the beginning to the end of each sprint. I also want to be able to get visual feedback (a Burndown chart) so that I can see how accurate my estimates are, and to what degree discovered tasks are entering the sprint, if at all.

Tracking discovered tasks can help identify improvements that can be made with future estimates. Also, being able to show a client discovered tasks on a Burndown graph can help them understand what can cause a project to overrun a due date, or why they may need to consider removing a feature if they want the project to be completed on time.

My team lead at Pocket Kings showed me how to get started implementing a simple system that can provide this with none other than Google Docs.

What I've implemented here is somewhat different from what I was shown, but it provides me with everything I need. Below is a snapshot of the spreadsheet with data from a hypothetical sprint. One quick point about this hypothetical data - in general I try to produce task estimates that are around one to two hours in duration. If I find I've estimated a task at more that this, I like to break it up into smaller tasks. For demo purposes, I haven't broken up the large tasks into smaller ones.

Anyway, to set the spreadsheet up, you enter a start date and an end date. Then you enter your tasks along with the task estimates. After this all you have to do is update the details of each task on a daily basis just like Version One. The formulas take care of the rest.

As you can see, below each task there are three rows. These are used to track changes in details relating to the task. These are:

• Estimated Remaining - This is the estimate for remaining work to get this task finished.
• Effort - The effort made to complete work that was planned for this task.
• Discovered Effort - The effort made to complete work that was not planned for this task.

Discovered Effort may be used to track required work that we simply didn't anticipate or it may be used to track feature creep. This happens when we or the client decide to add functionality during a sprint that wasn't planned. This isn't necessarily a bad thing, so long as it is understood that there is a cost associated with it.

Data from the rows described above are gathered from each task and totals are presented at the top of the spreadsheet. It's these totals that we use to produce the Burndown graph.

The Burndown graph for our hypothetical data is shown above. You can see we're a few days from the end of the sprint. Our Estimated Remaining work is burning down and is inline with the Target Burndown. You can also see we've hit some discovered tasks on the 4th and 7th day of the sprint. Regardless, visible effort is being made and we're burning down nicely. This sprint looks good.

The above system is relatively simple. I'll most likely end up installing Version One when my tracking requirements become more complex. The reason I'm using Google Docs and not Microsoft Excel is that I work with both Apple and PC platforms and it's nice to be able to access this stuff in an easy consistent way no matter what platform I'm using. Google Docs lacks some features present in Excel, but there are no show-stoppers here. Google Docs is also free.

I'm very impressed with what can be achieved with Google Docs.

The free version of Gravity Wave, our first game for the iPhone using UtopiaGL, is now available for download from the iPhone App Store.

The free version features the first four levels from the game, and gives a taste of what's in store in the premium version. The premium version will be submitted to Apple this week.

If you would like to find out more about Gravity Wave, why not try out the free version. You can also check Kevin's Blog where you'll find more technical details about the game.

Gravity Wave FREE was approved yesterday, after only a week in the submission pipeline!  This was my first submission to Apple, so I was a little apprehensive about it.  After living through the ordeal that was NSTL Brew App submissions in a previous life (and conquering it), this was a breeze.

The current release only has one difficulty setting, which more casual players might find a little tough.  I'm about to submit an update that adds two more, easier settings (Rookie and Normal) on top of the current one (Master), which is left as the most difficult. 

Here is the iTunes link, Gravity Wave FREE.  Go check it out!

I submitted Gravity Wave FREE to Apple earlier this week.  Since then I have been putting the finishing touches to the premium version, and that work is coming along nicely.  Hopefully I'll be ready to submit it next week. 

I opted to have one difficulty setting, because production was very time constrained.  I felt that the game play was reasonably simple, but after getting some fresh eyes on the game and some constructive criticism (much appreciated Dave!), I decided to add easier game modes, so now there are three difficulty settings.

Here's a quick peek at some of the premium levels.