Tuesday, October 27, 2009

A Different Route to the App Store

Young couple holding hands in record store, low section

Good stuff at the first day of MonoSpace. A definite highlight was the two sessions on MonoTouch. In case you're wondering, Mono is a framework that allows you to develop .Net applications for more than Windows- you can target Linux, OSX, Android, and Amazon's EC2, among others. And, using MonoTouch, you can build .Net applications for the iPhone. So, you can leverage your C# (or, at least some instances using F#) knowledge and skills, rather than learning Objective-C. Of course, there is still a learning curve- you're designing an iPhone app not recreating a Windows form on a different platform so there are different usage patterns and there are extra steps in wiring everything together, as you'd expect. Still, seems well worth using it for .Net shops looking to reuse code and leverage existing skills. Plus, it is actively being developed and keeps getting better- they announced today the release of a debugger to run on the iPhone.

The team that developed MonoTouch had several members present - they are justifiably proud of their achievements and looking for feedback, bugs and real test cases so they can tackle new improvements.

Friday, October 16, 2009

Taking Innovation Games for a SPIN

Friends Playing a Board Game
I'm a big fan of Luke Hohmann's Innovation Games. They are a fun way to gather qualitative information about your products from your customers. At last month's Austin SPIN (Software Process Improvement Network) meeting, I had the privilege to help facilitate some Innovation Games. Jeff Brantley did the heavy lifting and presented an overview of the games included in Luke's book. Then, we divided up the group and played a couple of games.

My group played Speedboat to get some ideas around what things were slowing down people's process improvement efforts. I chose this topic since it had been mentioned at last month's meeting that the officers were soliciting ideas for topics at future SPIN meetings. Instead of waiting for folks to email items in, playing Speedboat gave us a chance to quickly get ideas and conversation from a dozen people all at the same time. As we looked at similarities between items, two areas that stood out to me were "people issues"- getting and keeping commitment from people at different levels in the company and cumbersome change processes (ie- Change Control Boards (CCBs)). Plus, everyone got some experience with a game.

I've been impressed with the Austin SPIN meetings I've been to recently. The group is energetic and engaged and the officers seem very focused on bringing in topics and presenters that have something to give. I've learned new things at each one and this professional development focus differs from the SPIN meetings I'd been to previously. Admittedly, those meeting were over 10 years ago, but they seemed to feature a speaker trying to sell a tool and a bunch of people looking for jobs. Neither is a bad thing, in and of itself, but the mismatch between presenter and audience made for a depressing evening. Not so anymore!

Another thing that this meeting reinforced was the flexibility of the games. Besides being great for getting qualitative market research, I've used them for retrospectives, community learning around Agile requirements, and process improvements. Jeff mentioned using them with churches and community groups for planning. And now for generating program ideas. Leave me a note with any other uses you've found for Innovation Games.

Now, get out and play!

Tuesday, October 6, 2009

Looking Back to Move Forward

Retrospectives are certainly a central part to the way most people adopt Agile. Similar to previous incarnations, like Lessons Learned and Postmortem sessions, one improvement is they are held frequently and not just at the end of a project or, even worse, just when something has really gone wrong. I'm a fan of them and of having them with different scope- not just focused on the last iteration, if you're doing time boxed iterations. I presented an experience report at Agile 2008 on holding release level retrospectives.

Tonight, I get to participate in a panel discussion of Borland's time in Austin at Agile Austin. It is a retrospective about a period in the company's history when we were doing a lot of work to adopt agile and what lessons we can learn from that.

Come by if you get a chance!