1. CCT 355: E-Business Technologies Class 10: Enterprise 2.0

2. Test 10 MC questions 6 short answer questions, all building on each other Point form, scannable text encouraged Lecture notes as guide, change management information also included

3. Enterprise 2.0 - the IT “flower” (Boothby) Old enterprise software does not leverage power of connectivity and mass collaboration Generally conceived for individual use, centralized management and control Emergence of Web 2.0 apps (examples?) has given rise to new branches of enterprise applications (hence the flower.)

4. SLATES (McAfee) Search Linking Authorship Tagging Extensions Signals McAfee, A.P (2006). Enterprise 2.0: The Dawn of Emergent Collaboration. Sloan Management Review, 47(3), 21-6. http://sloanreview.mit.edu/smr/issue/2006/spring/06/

5. Another take (Carr) Carr, A. (2007). Designing for Sustainable Conversations. InteractionCamp 2007. http://www.slideshare.net/acarr/designing-sustainable-conversations-with-social-media-59204

6. Limits of “MS Office” Model Confusing to coordinate and share Confusing version and shared access controls Limited shared searching, confined mostly to desktop and search tools Not strongly related to transactional or structured processes Perhaps a dated productivity model - seems as much since Microsoft itself is extending it (e.g., SharePoint)

7. Solution #1: Web-based Office Collaborative shared web-based documents vs. individual authorship on individual machines Increasingly done by others - e.g., Google Docs and Spreadsheets

8. Solution #2: New Tools Feed aggregators, blogs, wikis - an explosion of information A move from managing old knowledge to facilitating new knowledge creation (and certainly managing infoglut) Activity- vs. document-centered work - a move away from individually authored documentation towards leveraging network effects

9. Solution #3: Open transactional systems SaaS - “software as a service” model - new markets for web-based services and modules Open architectures (e.g., OpenBravo ERP, OpenID) and open APIs (application programming interfaces) leverage network effects in transactional/structured processes

10. Solution #4: Structured Tools for Ad-Hoc work Knowledge work is chaotic - infoglut common (e.g., popularity of lifehacker.com, lifehack.org) Some emergent tools (e.g., Yahoo Pipes, Facebook apps) look to add some structured process to what otherwise might be information overload

11. Google’s Vision “applications that are pieced together” Small, fast, customizable applications Distributed virally Ubiquitous data Platform independent