Earlier this week I’ve had a chance to present WebCollage’s agile development methodology at a local Agile Practitioners meeting.
At WebCollage, we are releasing a new version of our SaaS based solution to our customers every two weeks. We released 23 versions in 2011, and will be releasing the 6th version of our software over this upcoming weekend. In other words, we are firm believers in agile development and in its ability to help obtain continuous market feedback (here’s a previous post on this topic).
For various reasons, though, agile development has become somewhat synonymous with one specific approach, namely Scrum. Realizing that Scrum is widely accepted, I previously expressed an opinion that Scrum is perhaps an interesting recipe, but is far from being the best approach to SaaS agile development (and web application development in general). I have received quite a lot of feedback on that other post, some with contrarian views arguing that Scrum is perhaps a silver bullet after all.
There’s always something to be said for using the most popular approach. As an old IT saying goes, no one ever got fired for buying IBM. In this regard, there are intrinsic advantages to using Scrum, most notably the industry ecosystem: ability to easily find knowledge, share best practices, etc.
Insomuch as the actual methodology goes, though, there are simply better alternatives for many software development scenarios. Here’s a sketch of how we at WebCollage develop software, and the advantages it has over Scrum. Our approach is an adaptation of Kanban/Lean software development.
Posted in Agile, Agile Software Development, ALM, Application Lifecycle Management, Future of Software, Iterative Development, Kanban, Product Roadmap, SaaS, Scrum, Software, Software as a Service, Software Engineering, Software Updates, Web Applications, Web User Experience, Website Creation
Tagged agile development methodology, Agile Software Development, development scenarios, web application development
Last month, Microsoft announced that it would start to automatically upgrade Internet Explorer on users’ PCs, essentially following the route Google Chrome has taken.
This announcement has gained publicity in the Internet-related software community as it was evident that this action was taken to react to Google Chrome’s increasing market share. Within a few years, Google Chrome usage has grown, and it is now not only the second most popular browser overall (surpassing Mozilla Firefox), but also similar in popularity to Internet Explorer 8.0, hence essentially (in a tied race) the most popular specific-version browser overall.
But, the significance of this release transcends the browser war. It highlights that long development cycles are becoming a thing of the past.
Posted in Agile, Agile Software Development, ALM, Application Lifecycle Management, Browser War, Cloud Computing, Distruptive Technology, Enterprise Software, Future of Software, Google, Google Chrome, Internet Explorer, Iterative Development, Oracle, Product Design, Product Management, Product Planning, SaaS, Software, Software as a Service, Software Engineering, Software Marketing, Software Methodology, Software Updates, Web Applications, Web Browser
Tagged Agile Software Development, Cloud Computing