If you are like me testing all the different types of web browsers, you will notice that Chrome releases a new version(major/minor) every 6 weeks. In Agile/Scrum based software development world, it's like two sprints or just one given the planning and testing needed.
On the contrary, IE9 and FF4 have been on the horizon forever recently hitting rc and beta. That's like a typical waterfall model trying to build a monstrous product for months together and releasing it to wild praying for adoption. Doesn't it sound like the old way of building software?
The new way is build something quick, release it and iterate quickly. This way you have something in user's hand sooner and an opportunity to twist and tweak depending on the feedback. You probably run a lot lesser risk this way than trying to build something big that finally may not take off with the user.
Build, release and iterate quick has become the norm for web portals for sure. It's agility! Is Google bringing the same to the world of desktop apps development through Chrome? Why not? After all, we know it works. And, the user feels like their browser is anew every six weeks waiting for the next 6 weeks. It's like Apple releasing something every 6 months. Doesn't matter what is released as long as something shows up to keep the buzz!!
Wait! Does Chrome releases comprise any major change to compare it with the monstrous IE9 or FF4? Not really and need not be. That's the point!
I am tired of waiting for FF4 to get released. It feels eternal! Time to change..
On the contrary, IE9 and FF4 have been on the horizon forever recently hitting rc and beta. That's like a typical waterfall model trying to build a monstrous product for months together and releasing it to wild praying for adoption. Doesn't it sound like the old way of building software?
The new way is build something quick, release it and iterate quickly. This way you have something in user's hand sooner and an opportunity to twist and tweak depending on the feedback. You probably run a lot lesser risk this way than trying to build something big that finally may not take off with the user.
Build, release and iterate quick has become the norm for web portals for sure. It's agility! Is Google bringing the same to the world of desktop apps development through Chrome? Why not? After all, we know it works. And, the user feels like their browser is anew every six weeks waiting for the next 6 weeks. It's like Apple releasing something every 6 months. Doesn't matter what is released as long as something shows up to keep the buzz!!
Wait! Does Chrome releases comprise any major change to compare it with the monstrous IE9 or FF4? Not really and need not be. That's the point!
I am tired of waiting for FF4 to get released. It feels eternal! Time to change..
