COMMUNICATION
       IS THE KEY



                Support Durable Knowledge
                     Sharing in Software
    ...
WORKSHOP: #SENSE09
Tuesday, March 3, 2009
Background         Communication   Microblogging

                         AGENDA


Microblogging in
                     ...
CONCEPTUAL BACKGROUND

Tuesday, March 3, 2009
SOFTWARE ENGINEERING IS...


    •a      social activity
    • knowledge              work of individuals in organisations...
KNOWLEDGE CHARACTERISTICS

    • knowledge               is a rational capacity, hold and applied by individuals
    • kno...
KNOWLEDGE SHARING
                      tacit knowledge      tacit knowledge


                                           ...
ARTEFACTS IN SE

    • artefacts          serve as external memories (Keil-Slawik, 1992)
    • SE        is not a solely t...
COMMUNICATION IN SE

Tuesday, March 3, 2009
COMMUNICATION IS...
    • is     essential for successful software engineering
    • an       important factor for co-loca...
FORMAL VS. INFORMAL
                           COMMUNICATION
    • informal            communication
         • explicit c...
AD HOC COMMUNICATION


    • spontaneous      interruption of team-mate with question or
        unsolicited information
 ...
COMMUNICATION AND
                  KNOWLEDGE ACQUISITION
                                                                ...
WHAT IS MICROBLOGGING?

Tuesday, March 3, 2009
WHAT IS MICROBLOGGING?


    • Templeton             (2008):
         • „small   scale form of blogging, generally made up...
TWITTER IN REALITY
            icon               username   user infos




     latest                                   ...
TAGGING MESSAGES



    • tagging            messages via the # symbol
    • proves   useful when sharing information in g...
ADVANTAGES OF
                               MICROBLOGGING

    • fast  exchange of thoughts, ideas and information sharin...
MICROBLOGGING IN SE

Tuesday, March 3, 2009
WHY NOT USE INSTANT
                              MESSAGING?

    • many    SE teams use IM for exchange of thoughts, info...
Tuesday, March 3, 2009
ADDED VALUE OF THE
                              APPROACH ?

    • virtual            ad hoc communication where it takes ...
ADDED VALUE OF THE
                            APPROACH ?
                                                               W...
SO NO MORE SPOKEN WORDS?

    • NO



    • Face-to-Face       is the optimal communication method
    • facilitate the an...
DEMO
                         a short one

Tuesday, March 3, 2009
WHAT‘S NEXT?

Tuesday, March 3, 2009
WHAT‘S NEXT?

    • Usage              of the presented prototype in classes next summer
    • Ethnografic             stud...
LAST PAGE



    • THIS               IS JUST THE DESCRIPTION OF AN IDEA
    • FROM THE                  REVIEWS
         ...
Wolfgang Reinhardt
                           http://twitter.com/wollepb




                         THANK YOU
Tuesday, M...
USED GRAPHICS

        Hand with key: http://www.sxc.hu/photo/1066202
    •

        Hand with business card: http://www.s...
Upcoming SlideShare
Loading in …5
×

Communication is the key - Supporting durable knowledge sharing in software engineering by microblogging

2,125 views

Published on

These are my slides from the SENSE09 workshop, held in conjunction with the Software Engineering conference at Kaiserslautern.

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Useful information! Interested people can check out the online application of QBreaker. It’s really helpful for students and teachers. For more information, visit http://www.qbreaker.com/why-qbreaker
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
2,125
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide
  • will present an approach that argues for the use of microblogging in SE to support information sharing and present an early prototyp
  • if you like to twitter about this talk, please use this tag, it allows me to filter your comments more easily
  • let me give you a brief overview about what i will be talking today... 1) conceptual background 2) communication in se 3) short intro to microblogging and microblogging in SE 4) i‘ll give a short demo of the prototype developped and a outlook on our next steps
  • in the context of knowledge work we need to define and delimit some terms in order to be specific. these definitions build the conceptual framework of this approach
  • we are in the domain of software engineering so let‘s have a look on what SE is...
    software engineering as social knowledge work requires
  • we need to be clear on what knowledge and what information is, so
    KM --> misleading because rational capacities are not manageable
  • information sharing in order to gain knowledge
  • the technology triangle presented here shows the regulation and inference of artefacts, the according knowledge and social norms and rules












  • first prototype screenshot. added view in eclipse, send messages invokes the API of twitter and sends message. in the meantime we did further development --> more in the demo









  • Communication is the key - Supporting durable knowledge sharing in software engineering by microblogging

    1. 1. COMMUNICATION IS THE KEY Support Durable Knowledge Sharing in Software Engineering by Microblogging Wolfgang Reinhardt, wolle@upb.de, http://twitter.com/wollepb 03.03.2009 Tuesday, March 3, 2009
    2. 2. WORKSHOP: #SENSE09 Tuesday, March 3, 2009
    3. 3. Background Communication Microblogging AGENDA Microblogging in Demo What‘s next? SE Tuesday, March 3, 2009
    4. 4. CONCEPTUAL BACKGROUND Tuesday, March 3, 2009
    5. 5. SOFTWARE ENGINEERING IS... •a social activity • knowledge work of individuals in organisations • production of artefacts by people for people •a highly communicative process • dependent on individual and organisational knowledge • based on information sharing 5 Tuesday, March 3, 2009
    6. 6. KNOWLEDGE CHARACTERISTICS • knowledge is a rational capacity, hold and applied by individuals • knowledge cannot be transferred, placed or distributed easily • need to distinguish between tacit and explicit knowledge knowledge: embodied knowledge of a person • tacit knowledge: artefacts using codified symbols can serve • explicit as explicit knowledge based on implicit knowledge of the subject • knowledge management is somewhat misleading 6 Tuesday, March 3, 2009
    7. 7. KNOWLEDGE SHARING tacit knowledge tacit knowledge • SECI modell of Tonaka and Socialisation Externalisation Takeushi (1995) explicit knowledge tacit knowledge • continuous cycle of transforming tacit in explicit knowledge • sharing information, creating explicit knowledge tacit knowledge artefacts, discussing and transferring, absorbing of artefacts Internalisation Combination explicit knowledge explicit knowledge 7 Tuesday, March 3, 2009
    8. 8. ARTEFACTS IN SE • artefacts serve as external memories (Keil-Slawik, 1992) • SE is not a solely technical process of creating artefacts • people, people, people Artefacts • creation of artefacts depends on cognitive and social aspects Inf tion ere De • artefacts generate new knowledge a n gul si nce sig Software gn Re De Development and necessitate reflection of Project Creation of socio-facts Technology Socio-facts Knowledge Regulation Inference 8 Tuesday, March 3, 2009
    9. 9. COMMUNICATION IN SE Tuesday, March 3, 2009
    10. 10. COMMUNICATION IS... • is essential for successful software engineering • an important factor for co-located and distributed teams • an activity that is needed to manage dependencies between actors (Malone and Crowston, 1994) • affecting coordination as well as control World activities Organisation • taking place in all domains of knowledge work within a software project Project Indi- vidual 10 Tuesday, March 3, 2009
    11. 11. FORMAL VS. INFORMAL COMMUNICATION • informal communication • explicit communication via phone, video or audio conference or other verbal conversations • formal communication • explicit communication via documents, reports, status meetings, e-mail or source code • need for informal communication if developers are to carry out their tasks adequately (Seaman, 1996) 11 Tuesday, March 3, 2009
    12. 12. AD HOC COMMUNICATION • spontaneous interruption of team-mate with question or unsolicited information • most often analogue, verbal communication • can take up to 41% of the developers time (Robillard and Robillard, 2000) • bolsters information sharing and indivdual learning 12 Tuesday, March 3, 2009
    13. 13. COMMUNICATION AND KNOWLEDGE ACQUISITION tacit knowledge tacit knowledge Socialisation Externalisation explicit knowledge tacit knowledge • written artefacts (source code, documents, wiki pages ...) are important sources for individual knowledge acqusition explicit knowledge tacit knowledge • spoken communications are very good problem Internalisation Combination explicit knowledge explicit knowledge solvers in intra- and inter-project settings • information is fleeting • need to be externalised to serve as artefact in other settings, projects or by other people 13 Tuesday, March 3, 2009
    14. 14. WHAT IS MICROBLOGGING? Tuesday, March 3, 2009
    15. 15. WHAT IS MICROBLOGGING? • Templeton (2008): • „small scale form of blogging, generally made up of short, succinct messages, used by consumers and businesses to share news, post status updates and carry on conversations“ • micro-messages can be sent exclusively to specific contact or made public • Twitter is the most well-known service for microblogging 15 Tuesday, March 3, 2009
    16. 16. TWITTER IN REALITY icon username user infos latest friends message 16 Tuesday, March 3, 2009
    17. 17. TAGGING MESSAGES • tagging messages via the # symbol • proves useful when sharing information in groups or contributing to specific topic, event or project • simple way of aggregating multiple messages via search 17 Tuesday, March 3, 2009
    18. 18. ADVANTAGES OF MICROBLOGGING • fast exchange of thoughts, ideas and information sharing (Ebner and Schiefner, 2008) • persistent storage of all messages sent • powerful component in personal networking activity • relevant part in one‘s informal learning • Open Source Frameworks available • easy to integrate in own applications via API 18 Tuesday, March 3, 2009
    19. 19. MICROBLOGGING IN SE Tuesday, March 3, 2009
    20. 20. WHY NOT USE INSTANT MESSAGING? • many SE teams use IM for exchange of thoughts, information or shouts for help • messages are fleeting • not usable in a downstream information search • need for tool switching • no RSS or simple API 20 Tuesday, March 3, 2009
    21. 21. Tuesday, March 3, 2009
    22. 22. ADDED VALUE OF THE APPROACH ? • virtual ad hoc communication where it takes place • liberation from writing formal mails to inform team about stuff • integration into the IDE • communication where knowledge work takes place • easy integration into own applications • persistent storage of all messages • easy use for downstream searches and aggregations 22 Tuesday, March 3, 2009
    23. 23. ADDED VALUE OF THE APPROACH ? World Organisation • intra- AND inter-project Class Main ready exchange of ideas Project B • get help from members outside Project A Take a How does look at it work? Project A own project Need I come some help around here! Project D Project C 23 Tuesday, March 3, 2009
    24. 24. SO NO MORE SPOKEN WORDS? • NO • Face-to-Face is the optimal communication method • facilitate the anyway happening virtual communication with a durable channel • provide a flexible communication channel usable for many purposes 24 Tuesday, March 3, 2009
    25. 25. DEMO a short one Tuesday, March 3, 2009
    26. 26. WHAT‘S NEXT? Tuesday, March 3, 2009
    27. 27. WHAT‘S NEXT? • Usage of the presented prototype in classes next summer • Ethnografic study (acceptance, usage, enhancements) • integration of microblogging as essential part of social software engineering platform • maybe enhancement of Trac, maybe own development • analysis of communication networks and emerging patterns • SNA like seen in Talk of Tommi Kramer at SENSE09 • Artefact Network Analysis 27 Tuesday, March 3, 2009
    28. 28. LAST PAGE • THIS IS JUST THE DESCRIPTION OF AN IDEA • FROM THE REVIEWS • provide evidence that the approach works • later ;) 28 Tuesday, March 3, 2009
    29. 29. Wolfgang Reinhardt http://twitter.com/wollepb THANK YOU Tuesday, March 3, 2009
    30. 30. USED GRAPHICS Hand with key: http://www.sxc.hu/photo/1066202 • Hand with business card: http://www.sxc.hu/photo/627728 • Bag icon: http://www.iconspedia.com/pack/email-me-1786/ • Mail icon: http://vande-mataram.deviantart.com/art/Windows-Outlook-akkasone-82408022 • Twitter icon: http://www.smashingmagazine.com/2008/09/23/practika-a-free-icon-set/ • Demo icon: http://www.everaldo.com/crystal/ • Calendar icon: http://wilsoninc.deviantart.com/art/Green-and-blue-104029981 • Microblogging icon: http://www.afmnet.ca/research/researcher.html?pid=297 • 30 Tuesday, March 3, 2009

    ×