Innovation Games Class in Austin

Innovation and agilist extraordinare, Luke Hohmann, will be teaching a two-day class on innovation games in Austin.

I have a copy of Luke's book, Innovation Games: Creating Breakthrough Products Through Collaborative Play. It contains the "rules" for a dozen games that you can play with your customers and design team to better understand your market and create innovative solutions to their problems.

Here are some of the details of the event:

When: March 18th-19th, 2008 (Tues/Weds)
Where: Renaissance Hotel, 9721 Arboretum Boulevard, Austin TX,
512-795-6006.
Price: $1695/person

Luke Hohmann, author of “Innovation Games: Creating Breakthrough Products
Through Collaborative Play” will be teaching an intensive, two-day class based
on the material found in the book of the same name. Used by corporations such as
SAP, Rally Software Development, QUALCOMM, Emerson Climate Technologies,
Genesyslabs, HP, Aladdin Knowledge Systems, Innovation Games® have been featured
in Software Development Magazine and Soft*Letter, numerous blogs and
conferences.

Designed by Enthiosys, the leading provider of agile product management
consulting services, this course will provide you with the tools to plan, play,
and post-process the results of the games. We’ll also provide you with
comprehensive notes, worksheets, templates, and books to help you your
learning’s into practice.

You can register for the event here.

Comments

John Hannafin said…

Is the book any good?

Sat Mar 01, 08:48:00 AM 2008

Roger L. Cauvin said…

Yes, I recommend the book. Otherwise, I wouldn't have posted information about the class :-)

Sat Mar 01, 08:57:00 AM 2008

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Cauvin

Search This Blog