Everyone loves a wish list?

Sometimes the only ones enthusiastic about methodology sit on the vendor side. What do you do if you get that 1000-yards-stare back when you mention "agile" or even try selling the idea of using "Scrum"? For sure you don't start talking in detail about building product backlogs and items making it into a future sprint backlog!

What I have found may work in such settings, though, is introducing the concept of a wish list and some very simple rules to govern it. YMMV, of course, but something along the lines of:

- Every suggestion or idea, no matter how great, goes into the wish list right away
- At certain points the wish list is reviewed and the highest value items are scoped for delivery

Of course there is the risk of being perceived as a stubborn bastard, but maintaining such a wish list can help you structure a "backlogish" approach even where no-one wants to hear about it and it can be good for business (on both sides, actually -- as it makes priorities clear) and often separates what is included from what is paid for. Give it a try.

WeVideo got the time to succeed - and boy they seem to use it

WeVideo just raised $19M from a venture capital firm. Knowing these VC guys are not playing the 50% increase game, this certainly raised the bar for WeVideo - I guess to be a real success now by their definitions, we are talking $250M+ valuation or so... Crazy. And crazy exciting. I do of course know that the reason for such multiples is that the likelihood of going to a $0 valuation is also very real. Any way you put it, this is a huge compliment to the team lead by Bjørn and Jostein and a great opportunity to take a real shot at being and staying number one video editor in the cloud.

Just after the news about the funding, WeVideo announced their extended partnership with Google (they are already on YouTube.com/create) and that WeVideo was compatible with Google Drive from launch day. And this week, Disney launched their Avengers Remix campaign powered by WeVideo. And not long before that, WeVideo launched their first mobile app that seemlessly let you add clips from a mobile device into a collaborative video project. Busy bees indeed.

And a last quick note: This week a book co-authored by Andreas Goeldi, who I went to MIT Sloan with, came out; Video Marketing for Dummies. Reportedly he says about WeVideo that it is "Likely the closest thing to a full-blown video editing application in the cloud". Couldn't agree more!

Full disclosure: I am not exactly neutral to WeVideo. I am a member of the board of Inspera, the company that developed the technology in WeVideo and spun it off as a separate company. That being said, my very tiny stock ownership in Inspera (that is now a minority shareholder in WeVideo) is not likely to make me truly rich, even if the ball flies totally out of the park. But rich on experiences for sure! Through my company Innovation Consulting I am playing a modest role in making WeVideo tick and appreciate both the forward looking days and the more firefighting-style we might have from time to time in the run-up to a big launch.

Competing with "Free"

My company has spent the last two and a half years developing what we think is a kick-ass publishing tool (authoring tool) for apps in general, and school book apps in particular[1]. About a month ago iBooks Author was launched by Apple, with no cost for the product itself.

Having a competitor launch a free product, aimed right at the niche where you have invested thousands of hours, is seldom good news. And when the competitor is possibly the world's most admired for innovation (I for one find it absolutely stunning that they still grow almost like a startup and with profits the size of Google's revenues!), and at times the most valuable company in the world, is all lost? As it turns out: No.

I will freely admit that I was nervous before the product launch, given the rumours (which were true). And five minutes into the launch video, I was scared. But five hours later, some analysis helped calm the nerves. I created this little matrix, you can click to enlarge it, showing that the lunch was clearly not free this time (either):

So for the time being, I see the launch as positive. The product and the marketing around it clearly highlights the need for innovations in apps for school books (and maybe broader in learning) and with the product's current shortcomings, it is not that hard to still try to sell "an expensive alternative". But if iBooks Author's output products ran smoothly on Android with no restrictions on the content produced, I would probably go back to being scared. Or maybe just work even harder on the online-collaborative angle. Go David against the innovation Goliat!

[1] - This sketch, again click to view larger version, shows the principle of how the system works:

A more technical version is that the core is HTML5-based. When building the app we pull out the HTML5 content, wrap it with a set of native extensions (using PhoneGap) and build for the relevant iOS (mostly iPad, but also iPhones for books for children) or Android platform.

The response of a potential customer being shown it live in a meeting previous week was "Magic!". I smiled.

The App Store review process and queue theory

The last weeks I have had the mixed pleasure of pushing 19 apps through the App Store approval process for a client. Some updated to improve iOS5 compatibility and some brand new. It might be bizarre that this gave me associations to queue theory, but it did and I will explain why.

I won't claim that I remember much details from the queue theory I had at NTNU exactly a decade ago, in the context of building scalable web apps, but I remember this: If you have a mixture of a few large jobs and a lot of small jobs, you can improve the throughput a lot by introducing two queues[1] - one for the small jobs and one for the large. That way the small jobs can flow through quickly, while the big beasts naturally take some more time, but that is hardly unexpected.

An extension of this principle is exactly what Apple should do. I find it slightly ridiculous that an unchanged app (apart from the fact that it does no longer crash on startup with the combination of iPad1 and iOS5!) can take a week to review, going from version 1.1 to 1.2... So, Apple: Get that high pri queue for small jobs (i.e. minor bugfixes etc.) going and the perceived throughput from the job's (app submitter's) point of view will increase greatly! In practical terms, get dedicated teams (or time) to review updates of existing apps and make them flow through the review process on a less than two day average, compared to taking maybe the bulk part of a week today.

[1] - Or a variant thereof with allocating slices, as in a time sharing system like in modern computers - which de-facto will make small jobs flow through quickly if each job gets an equal amount of time "each round" and the big is not served again before every small job gets its share.

Adobe acquiring PhoneGap - for better or worse...

I just wanted to write a really short note on the news two days ago that Adobe is acquiring Nitobi, the makers of PhoneGap.

I have been using and talking PhoneGap for about a year and a half now, building a rather powerful authoring tool that uses PhoneGap with some native extensions to build apps for iOS and Android.

Anyway, I am thrilled with the prospect of one of the industry giants, with excellent track record on the tool side, supporting PhoneGap. I also feel this gives a certain approval of PhoneGap as a serious tool. On a related note, I have had clients that I held presentations for about cross platform mobile development in 2010 come back the last months and say "we were wrong, there is actually a use for PhoneGap". Since it is hard to plot a graph safely from a random subjective data point or two, having Adobe "stamp the whole chart right there" - saying there is room for this technology for sure, was really a energy boost for me.

On the other hand, I am slightly skeptical based on Adobe's (lacking) track record on mobile devices. As I have noted before, I feel that the really great mobile platform from Adobe has been only months away since I tested an early Flash Lite edition in 2002. I am also not sure if I view the split with the ASF taking care of the OSS version as a good one. Does this mean there will be a split of versions and functionality also in the core product and APIs? For me, that would be a huge disappointment (while I find it perfectly fine that the PhoneGap Build service will be developed as a closed proprietary Adobe product and of course that tools like Dreamweaver and Photoshop gets export wizards and whatnot!). And damn, PhoneGap is a better name than Callback. :-)

In any case it is exciting times for mobile apps development in the space, literally, between HTML5 and native apps.

And on a day like this I cannot end without (even though I am not generally a fan of throwing around either "R.I.P." or "awesome" all the time): R.I.P. Steve Jobs, AWESOME innovation legacy you leave behind - and you changed a generation's view of product development and importance of design in innovation.

WeVideo Champagne Supernova

Yeah, we[1] have launched WeVideo! The US team even won a prize for their presentation at Demo 2011. Congratulations! I must I admit I am sometimes that boring realistic and analytical engineer - how refreshing then to have someone else to bluntly say "we will revolutionize social video editing".

We have been thinking hard around pricing, technical architecture and countless details before the launch. I might write something on that later. But now, a more practical test. People often say "eat your own dogfood" or, as I will insist on phrasing it in this case, "drink your own champagne". Anyway - use your own tools if you believe others should.

I've gone ahead and done just that. I just drove from New Orleans to NYC for my August holiday and now I created a short summary of the trip. I am a total amateur, like most of our users will be, so you will maybe not be that impressed by the resulting video itself. But I was, honestly, impressed by the tool when using it for real, not just testing some boundrary case for technical reasons.

For this 3 minute movie, it was uploaded videos and photos from 2 cameras (one mid-range SLR, the Nikon D90 and one Nikon point and shoot from 2007) and 2 iPhones, put it together in a timeline and slotted in some mp3s[2] - then uploaded a screenshot of a google map and added some transitions and texts in the tool to end up with this video:

What struck me was that after getting the raw material into the tool, the rest was really easy. Imagine how disruptive this can possibly be as bandwidth continues to grow exponentially...

The launch seems to have gone well technically so far and it has gotten nice reviews. Of course the sign-up rate (4 digit number of sign-ups in the first few days) is not quite up where we had dreamed. On the other hand if it keeps groving at a steady rate we will have the whole world as users by Christmas. :-)

Now go on to WeVideo.com and invite some friends to edit video collaboratively - good luck! And drop me or the WeVideo team a note if you have a suggestion or find a bug - we are now in what we have defined as a public beta version and need all input we can get to get this right.

[1] - Full disclosure: I am a member of the board at Inspera, that holds a majority ownership position in Creaza AS and (directly and indirectly through Creaza AS) controls 52% of WeVideo Inc. I have also played a relatively modest role in the more practical matters of making everything you don't see (clusters of web servers, rendering farms and the like) work and scale, as a consultant.

[2] - Forgiveness, not permission. Pretty-please. The album Fuzzy by Grant Lee Buffalo is one of my all time favorites. If you do not own it in at least two formats already, go ahead and buy it in the iTunes store (or your favorite equivalent) right away!

Make the desire to win bigger than the fear of losing

I was recently made aware of some research about penalties in football (soccer, for any US readers). How can this be relevant in project management? Maybe it is a stretch, but I think it can learn us a thing about motivation. Let's see.

I cannot find the original Norwegian source now, but the basic content was this: When the last penalty is taken in a football penalty shootout, the likelihood of scoring is almost twice[1] if your team will win if you score than if your team will lose if you miss[2].

Even though generalizations from non-related fields is risky and I am a fan of brutal honesty[3], I will take my chance on this one: This can learn us to make the desire to win bigger than the fear of losing. If your project team feels scoring that goal (be it completing their component, polishing that presentation, or something else) will win the game, it is better than if they fear their mistake will drag the entire project to a failure.

So making each team member feel that their contribution is essential, but creating an environment where everyone is sure someone else will pick up the ball (!) if he fails his current task, sounds like the winning formula. Maybe not rocket science (it is football science, after all!), but a good reminder?

Now go on and win your game.

[1] - Again I didn't manage to find the original numbers, but they were something like 40 % and 70 % likelihood of scoring. Will update this blogpost if someone pings me with a link to data or original article. The source is as credible as it gets in Norwegian mass media, at least (A-magasinet from Aftenposten) - and it seemed to reference valid research.

[2] - I.e. the statistics were for the tenth penalty, and equal score before the penalty will give the first situation and the team not having the shooter being one goal up would be the second.

[3] - For the record I am also a fan of a lot of praise. But being direct about the negative also gives credibility to the praise. Maybe a separate blog post on this later!