Tommy (someone for whom I have the greatest respect) made some very interesting comments in his posting: Corporate mass & inertia prevents agility.
Now, I have also had some experience sailing and that certainly helps me relate to the metaphor he uses. Sometimes I like the slow boat and sometimes the fast one – it really depends on what you want to accomplish. However, in this age where “internet time” is what companies have to worry about, agility is what is needed for the complete delivery of products. There has already been a lot of talk about agile development for quite a while – and that is certainly a great thing for the software industry, but development is just a part of the product delivery, one has to embrace the complete lifecycle and think about agile product management (check out the front end of SAFe) and agile DevOps.
But then, there’s also some benefits to sometimes take a slow boat to China…just not when you need to deliver a product to your clients!
IBM Curiosity Shop
A fun side of IBM where the road to a smarter planet is paved with stories supported by pictures, animations, illustrations, and animations.
The serious side of comic books!
IBM is still serious about dealing with all aspects of systems development. In the past, this was mainly seen as developing embedded software. More recently, with the rise in popularity of SysML, there have been added capabilities to support systems engineers’ needs for architecture modeling and development tooling. Now, IBM is taking the rest of the tools into consideration by attaching systems development to the Jazz platform:
Jazz Community Site – Expanding horizons: systems engineering and software development
Interesting read and, perhaps more importantly, the start of discussions related to this topic!
If you have any interest in systems engineering (not just embedded software development), please respond to Greg’s invitation to talk and discuss about it!
Matt Gemmel has a very interesting blog entry on the iPad. He makes some good points about a lot of people missing the point of the device and helps clarify some of my questions in my previous post regarding what market Apple wants to define.