BlueBridge Technologies AG

Size: px

Start display at page:

Download "BlueBridge Technologies AG"

Logan Thompson
9 years ago
Views:

1 BlueBridge Technologies AG Sind die Wikis in SharePoint nur ein Spielzeug oder können sie einen echten Mehrwert für mein Unternehmen bringen? BlueBridge Technologies AG November 2010 Frankfurt am Main

2 About Us

3 Key Facts BlueBridge Technologies AG Founded December 2000 Privately held company Named after the Blaues Wunder bridge in Dresden 20 employees in 2009 Main focus is on large enterprises Microsoft Gold Partner

SharePoint History 2001 2002 First SharePoint project in Germany for Microsoft SharePoint 2001 Volkswagen,

Infra Bayer BBS MOSS 2007 Siemens MasterPage Product Wiki Product Operations Records Archiving NWA

4 SharePoint History First SharePoint project in Germany for Microsoft SharePoint 2001 Volkswagen, Kali SharePoint 2003 Launch Partner PoC Bayer WSS 2003 Siemens Menu Product WSS Infra Bayer BBS MOSS 2007 Siemens MasterPage Product Wiki Product Operations Records Archiving NWA Extranet MySite 2008 List2PDF Extranet Product 2009 BBS Save2Disk 2010 SAP Query Wiki Product PDF Social Networking

5 Publications Einfach online zusammenarbeiten mit den Microsoft Online Services SharePoint/Exchange Hosting with Microsoft BPOS SharePoint 2010 Handbuch für Anwender Official User Manual for SharePoint

6 Wikis in Enterprises

7 Buzzword Wiki Wiki best known thanks to Wikipedia Wikis are a popular buzzword at the moment Wiki as a synonym for glossaries or lexicons Wiki as a basis for Web 2.0

8 Wikis vs. Conventional Tools Conventional Tools (e.g. Microsoft Word) Easy to edit and format Structured approach Advanced system for reviewing changes Focus on layout and format No mistakes allowed The Wiki Method Everyone is an author and a specialist Information is shared and linked instantly Documents are embedded in sites and do not have to be opened Cross-document search capabilities Changes tracked for individual pages and roll back if necessary Simultaneous editing of content (each author writes their own chapter) Notifications and RSS feeds No time spent unnecessarily on formatting

9 Wikis in Enterprises Why use Wikis? On the fly editing ensures information remains up to date Greater feeling of ownership contributes to higher levels of motivation Why SharePoint Wikis? Seamless integration with existing systems Fast, WYSIWYG editing Customisable notifications PDF Export Robust version control and reviewing, workflows Semi-structured approach Sophisticated permissions management

10 Internet vs. Intranet Wiki Internet The content is decided upon mutually by the editors The amount of documentation and its detail depend on the interests and participation of the editors Everyone is an editor and a reader at the same time Intranet Standardisation is the key. The use of templates is encouraged. Exception: structure can/should in many cases by defined by the users Managers decide on clear guidelines and goals There is often a differentiation between authors and readers Participation is voluntary and is down to individual motivation Participation is part of the employee s job (how can they be motivated?)

11 Usage Scenarios Documentation & Specifications Each author concentrates on their own chapters fosters specialisation and collaboration Dynamic and hierarchical navigation PDF Export inc. customisations to reflect corporate identity Knowledge Bases / Glossaries Fast data entry with no IT know-how necessary Support for discussions, workflows, tag clouds and ratings Everyone can contribute and correct errors immediately Training plans, projects, presentations Easy to update dynamic content Intuitive navigation based on high quantity of links to related pages

12 Demo

13 Wiki Extensions I: Enhanced Editor

14 Wiki Extensions II: Navigation

15 Wiki Extensions III: PDF Export

16 Example: Pharmaceutical Industry Project Specification 40 Pages Small Teams Versions Navigation Editors spread across the globe Guidelines 250 Pages Word Import Large number of readers Navigation

17 Example: Industry

18 Example: Industry

19 Example: Industry

20 Survey about the usage of wikis Quelle:

21 Why do wikis fail? Poor launch strategy Too much/too little control No integration of processes Lack of incentives/role models Lack of involvement Short-term or egocentric culture (often linked with a lack of trust)

22 Key Reasons for Choosing SharePoint Wikis Technical Arguments User Arguments Single-Sign-On Fewer support calls with familiar system Integration with other systems & processes More control for admins Metadata support Robust infrastructure Integration with Office Communicator Define notifications for others Users stay on single platform Auto Thumbnails Workflows Solid task management Simple to use Versatile feature set No code Approval processes Flexible Views Integration with Live Meeting

Thank you for listening! Host TwoDo Kommunikation-Management GmbH Rotlintstraße 66 H, 60316 Frankfurt www.two-do.

23 Thank you for listening! Host TwoDo Kommunikation-Management GmbH Rotlintstraße 66 H, Frankfurt Supported by: IP ShareMedia / IP Sem Organiser: SharePoint User Group Frankfurt [email protected]

24 BlueBridge Technologies AG Steven Greenhill T: + 49 (9545) F: + 49 (9545) M: +49 (151) E: [email protected] Stockgasse Buttenheim T: + 49 (9545) F: + 49 (9545) Schumannstr Bonn T: + 49 (228) F: + 49 (228)

Collaboration. Michael McCabe Information Architect [email protected]. black and white solutions for a grey world

Collaboration. Michael McCabe Information Architect mmccabe@gig-werks.com. black and white solutions for a grey world Collaboration Michael McCabe Information Architect [email protected] black and white solutions for a grey world Slide Deck & Webcast Recording links Questions and Answers We will answer questions at