Social Project Management20.05.2014, Continental AG, Regensburg

Agenda

� Introduction

� Why project-oriented KM?

� Social Media

� Social Project Management

2

http://bit.ly/blp12Bericht

Simon Dueckert

� 1994 Study Electrical Engineering

� 1998 Engineer at Fraunhofer IIS, Implementation of a KM Approach at Fraunhofer IIS

� 2001 Establishment of Cogneon

� Knowledge Management

� Knowledge Work

� Learning Organization

� Enterprise 2.0 &Management 2.0

Member of Society of KM, New Club of Paris, VDI KM Expert Group, Association of Community Management, Chaos Computer Club

3

http://knowledge-on-air.de

or iTunes Podcast Store

Our Passion4

Examples5

Examples6

Examples7

Rupert Stadler, CEO, Audi AG

Examples8

Examples9

Examples10

Zeit

~10000 v.Chr. 1800 2000

Megatrend Knowledge Society11

Agrarian

Society

Industrial-

Society

Knowledge

Society

Quelle: nach Zukunftsinstitut. 2010. Eigene Darstellung.

Knowledge Society in Numbers 1/212

15%

35%

50%

Worker

Knowledge

Worker

Service

Worker

1930 1960 1990 2000 2020

Quelle: nach Zukunftsinstitut. 2010. Eigene Darstellung.

Knowledge Society in Numbers 2/213

Source: OECD.

Times are changing …14

1908 1969 2007

Organization 1.0: Hierarchies15

Source: OECD.

… we all feel this!16

Organization 2.0: Hierarchies AND Networks17

Source: Forbes, Kotter International.

Organizational

Units

Communities

of Practice

Projects

e.g.: my „performance network“18

Social Media19

Source: Ethority.

Social Media in Organizations20

2005 2007 2010

Weblogs

Wikis

Social Networks

…

2014+

Collaboration, CSCW

1984 1997

Social Media in the Project Life Cycle21

Source: PMI PMBOK.

„Working Out Loud“

Reusables

Lessons Learned„Socializing“

Social Media in Project Process Groups22

Source: PMI PMBOK.

10 Concrete SPM Ideas

1. Virtual Community: use a community space inside a social network as„virtual obeida“. Make it as open as possible.

2. Socialize: perform kick-off meeting for team building, socializing andexplanation of knowledge infrastructure. Distribute tasks for first virtualsteps (e.g. write a blog to introduce oneself and reflect own role).

3. Adoption: define the role of a „knowledge coach“ for the project.

4. Working out loud: animate team members to write short statusupdates on a daily basis. Use a (2nd?) weblog for communication withproject external stakeholders.

5. E-Mail-Detox: use weblogs, follow-functions, and @mentioning toreplace (reduce) e-mail traffic.

6. Planning: document milestone plan and working packages in a wikiinside the project community.

7. Meeting Management: use a wiki for collecting agenda topics, live writing meeting minutes, and task lists.

8. Responsibilities: create a RACI matrix in a wiki linked to teammembers profiles and area of responsibilities.

9. Structure: define Tags for reusables, lessons learned, work packages, teams, milestones, products, components, customers, technologies, methods, tools etc.

10. Reflection: perform a AAR/LL-Workshop/Project Retrospective to collect, refine, and distribute experiences. Use process to publish reusables.

23

Thank You! Questions?

Unsere Materialien zu öffentlichen Auftritten finden Sie unter slideshare.net/cogneon

Wir freuen uns über Kommentare, Likes und Weiterleitung.