RE: Enterprise 2.0 Use Cases

communities@jivesoftware.com — Wed, 30 Jul 2008 23:30:16 GMT

I'd add Enterprise Architecture (or Central DevTech) cases to this list. From my own experience:

1. Shared code initiatives across a large pool of developers working on different projects, using an internal wiki to collect requirements and then post reusable software libraries for other development groups to use (once they pass though a central fitness review by a board of architects for performance, security, testability, etc.).

2. Technology Policies: using an internal wiki to collect the expertise around technology policy and governance questions -- like figuring out when will be ready to upgrade an IT infrastructure item to the next version. A wiki collects the issues by the many stakeholders to create a plan that works for everyone.

3. Technology How-Tos: using a topical discussion forum to allow developers to ask and answer questions about development issues, installation procedures, and best practices.

Plenty more like these -- all have the underlying features that:

1. You don't mind if the information is shared and that people you don't know might see it. It's not private to your work team.

2. Adding multiple perspectives make the content better suited for more people.

3. The information is not static or definitive by nature, rather it changes over time.

4. The information is intended to be consumed by people in different groups anyway.

RE: Enterprise 2.0 Use Cases

steve@fg2.com — Fri, 19 Sep 2008 06:02:18 GMT

Hi Barry - hope I get to work with you in Atlanta or Austin. Anyhow, I wanted to point you to this post which talks about the incredible success that Clearspace has has helped me unleash within FG SQUARED

http://www.fg2.com/clearspace/blogs/squared_root/2008/09/17/are-you-in-the-zone

Internal Collaboration : Enterprise 2.0 Use Cases : Comments

RE: Enterprise 2.0 Use Cases

RE: Enterprise 2.0 Use Cases