More stuff about Google

Following up on my twitter post...  

on the other hand is the fact that Google will keep creating weird features in Gmail - last example is this inbox feature for slow connection... 

How many Google savvy users are still on 3200 bauds modem?  Admitedly the value of this feature is of limited reach...

There are a bunch of productivity related features that are in their funnel I am sure, I for one keep pushing features their way. 

Last one was something inspired from the Syndeo Project Server we created back in the days...  It's the ability to put email threads on a stack or on a symbolic push pin board that you can later pick and add as attachments to other emails. 

I do not know about you but I keep having to do this, digging out threads and then forwarding them arround.    Of course I can send them individually but in many cases it makes sense to keep them together to keep the context in one bundle. 

Been waiting for this and other similar productivity enhancement to gmail... Maybe I am alone with this need who knows?

 

You can contribute feature list to Google at 

http://mail.google.com/support/bin/static.py?page=suggestions.cs

Google Tasks

This is something that I have been waiting for a long time now... 

Last week Google released an update that shows your tasks in your calendar.  Kind of mandatory if you want to get them done! (granted that you at least look at your calendar once a day...)

Read more about it here. 

OSEF - Software as a Service

Yesterday was the event on SaaS, we had a very information savvy group and our panelists, as usual, have helped demystifying SaaS for the rest of us. 

A couple highlights for me from the discussion:

SaaS is raising the bar with respect to the quality of the development process.  

I was not expecting that one.  But when you think about it, delivering software (read: value) frequently puts pressure on the need for the development team to create quality software at all time not relying as much on an intense and lengthy verification process.  In this context, successful SaaS product teams have better software development processes.  We did not dive into the details of it, but risk mitigation and quality assurance strategies such as: user centered design, code review, agile methodologies, automated unit tests are certainly part of the mix.

Lesson: When building software in the SaaS model, ensuring you have a great software development process should increase your odds of getting the most returns out of your SaaS initiatives.

Your development team are on the operation team. 

We had an extensive discussion on the shift that SaaS causes on the involvement of the development team.  This is a no brainer when you think about it.   When releasing software on a monthly basis (or even faster) to your customers, you must have your development team available at all time, otherwise who's going to take care of the unexpected failure occurring on a Sunday night?  This is a clear distinction over the more traditional delivery model of shrink wrapped software.  

Lesson: Ensure you are engaging your development team for more than "simply" building the software.  They must be available to handle software failures at all time.  

Hope to see you at the next OSEF, the last of this season (for real this time!) 

If you are not member, please request membership through http://www.meetup.com/ottawasef/

Cheers!