I’ve got to say I have an interesting concern - but a sense of delight at the possibilities - about the speed and capacity of change of Enterprise 2.0. Let me explain…
In the world of application development, there is a serious and mounting argument from the rapid development / iterative prototyping camp versus the waterfall (requirements, design, build, test, deploy, support) purists. When it comes to applications that affect corporations - that is, across the enterprise - I am a firm believer in the latter.
Iterative development is great when there are only a few people involved - or a small point solution that only affects a few people. When you start getting more people involved, the challenges go up.
The challenges include:
Now with Web 2.0 / Enterprise 2.0, the beauty is that these applications are breaking new ground in making the process neatly tied up in the applications and making it really simple for people to follow the process without having to think too much about it - or having to refer to training manuals or help guides. However, the ease of picking one up, configuring them differently according to different needs - but at the same time missing the opportunity to apply them consistently is the challenge.
The takeaway points to consider:
All comments welcome!