CurtinNet308

The authors examine uses of instant messaging in a high-tech firm to illustrate how knowledge workers use this tool to collaborate with co-workers. According to Quan-Haase et al., the objective with the study was to 1) identify the collaborative practices of individuals in mediated work environments by looking at use of IM, 2) discern what social processes are reflected in employees' use of IM, and 3) investigate how visibility, awareness and accountability are used in an IM system. The research found that IM is used extensively to exchange work-related messages, coordinate and arrange meetings, and inquiry about colleagues' availability for discussion. IM was used as much for internal communication as for external communication. The authors also found that IM functions as a barrier in some cases as some employees use IM as a way to create distance between them and their superiors. Quan-Haase et al. suggest that this is particularly useful when difficult decisions have to be made or sensitive topics discussed. Quan-Haase et al. examines how workers in a small high-tech organisation manage their IM use for the purpose of information exchange and collaboration. The article is interesting as it is based on a case study of an actual organisation. However, it is written 6 years ago so employees' willingness to adapt to instant messaging may have changed as collaborative tools are more common today. Still, most of the findings are still applicable today. References Quan-Haase, A., Cothrel, J. & Wellman, B. (2005). Instant Messaging for Collaboration: A Case Study of a High-Tech Firm. Retrieved from http://jcmc.indiana.edu/vol10/issue4/quan-haase.html

This article explores how a world-wide furnishing store (IKEA) used their already existing culture to guide the production and implementation of their intranet to ensure the technology was the right fit for them. With a very strong focus on teamwork, community and collaboration already recognised in the IKEA business-model, IKEA were well aware that a strong corporate culture does not guarantee user-acceptance of information systems. "Rather than forcing its corporate culture to bend to accommodate a technology-based system, IKEA used its firmly established culture as the foundation for its IT solutions." (P. Chin, 2009) And something must have worked. In 2008, IKEA Inside (their intranet) was listed in the world's ten best intranets by well-known user-experience research firm Nielsen Norman Group. IKEA were mindful of not letting the technology they introduce ruin an already well-established human focussed corporate culture. They said their culture gave them the framework to introduce new things to the business - including information systems and technology. As Beth Gleba, Internal Information Manager for IKEA North America points out, "Before, during and after [intranet implementation], our culture is our culture." In my experience as an intranet manager, I definitely agree that a company's already existing culture will influence the final state of a technology. In organisations that don't focus on people or put staff at the front, there will often be a "disconnect between the technology-based systems and the people they're meant to support." (P. Chin, 2009) It is because the people who've made the technology haven't taken into consideration the end-user, or worse, just don't care - and where that happens that attitude is often supported by the already existing corporate culture. Reference Chin, P (2009) Inside IKEA's Human Intranet Approach Retrieved from http://www.intranetjournal.com/articles/200908/ij_08_21_0

Thank you for this article. I leaned something very interesting. "I do a little, you do a little, and together we do a lot" (Chin, 2009) This could well be the mantra for IKEA. As a company with a strong brand identity and customer-focus, here we see how important it is for IKEA staff to have the right tools and platforms to allow them to find the information they need, quickly and easily. At the same time Beth Gleba, Information Manager of IKEA North America, is aware that tools are only part of the story. It is people who make IKEA what it is. It is a place where children are free to jump on the beds, while their parents browse. Part of the success of IKEA is it's strong brand focus and supporting charities is one very important way corporations are building on their social capital by bringing attention to issues close to the hearts of customers and staff alike. In one of my shared articles Mangold & Faulds (2010) point out "organisations can leverage emotional connections by embracing one or more causes that are important to their customers." Such practices give staff and customers a sense of 'belonging". Here IKEA goes one step further by not only providing products and issues to discuss but also provides them with the tools they need to do it. One interesting point I noticed was IKEAs use of Social Media tools to create employee profiles. This aids in fostering group cohesion and allow staff to get to know one another and feel a part of the IKEA family, which for a large firm, can be very difficult to do. They also make very nice meatballs! Reference: Mangold & Faulds (2009, July-August). Social media: The new hybrid element of the promotion mix in Business Horizons. 52(4) 357-365

Known as 'social media marketing, viral marketing, buzz, and guerilla marketing' Word Of Mouth Marketing has become an important feature of marketing online. This article is a fairly in-depth study looking at issues of shifting narratives, practices and theories in WOMM, particularly in the face of growing social media communities. The article looks at ways social - media marketers are dealing with "networked coproduction of narratives" made possible by the affordances of social media tools and the Internet (Kozinets, 2010). Kozinets et. al. argue the evolution of word-of-mouth marketing is marked by 3 stages: First, the Organic Interconsumer Influence Model, or simple word-of-mouth, which is not directed, promoted or directly influenced by marketers; Second, the Linear marketer Influence Model, sees marketers seeking to influence and guide WOM by focusing on so-called "opinion leaders" who are able to influence others. This the of marketing will be familiar to Facebook or Twitter users, who may be used to seeing products recommended by well-known celebrities; Third, is the Network Coproduction Model. This refers to "managed one-to-one seeding and communication programs". As Marketers and consumers often have very different goals, such a strategy is not without risk. As Kozinets et.al. point out (2010) "consumers are regarded as active coproducers of value and meaning, whose WOM use of marketing communications can be idiosyncratic, creative, and even resistant". The main challenge in Word Of Mouth Marketing (WOMM) online is that marketers typically have less control over the content and direction of the campaign or opinion (see Mangold and Faulds, 2010). According to Kozinets et.al (2010) the key to successfully engaging large and often disparate groups is building network of "one-to-one" personal relationships, which allow individual members to become involved and feel a part of the process of narrative building and meaning creation. References: Kozinet

Available online via Curtin Library Catalogue (see below) This article stresses the importance of social media in the promoting of a company's brand or products. Social Media collaboration, according to Kaplan, enables 'the joint and simultaneous creation of content by many end-users'. For advertising social media provides platform which enables customers to partipate in the creation of the brand by generating feedback and product reviews. Mangold and Faulds argue that, for potential customers, online content which is generated by other consumers is typically regarded as more trustworthy than traditional advertising messages. Essentially, social media messages are more likely to be believed and responded to than direct-marketing on the other hand, social media also means companies have less control over the course of discussion. They argue,'while companies cannot directly control consumer-to-consumer messages, they do have the ability to influence the conversations that consumers have with one another'. Mangold and Faulds argue, used correctly, social media has become an important tool, which allows companies to not only talk to customers but also allows customers to talk to each other. Social tools, they suggest, provide customers to obtain information about companies and products and can aid them in the decision making and purchase process. Creating networks of social relationships with potential customers is a strong tool, which aids in the promotion of a brand but it also provides important tools to help managers achieve the company's missions and goals. Some tools companies can use to communicate with customers include company websites, YouTube, eNewsletters, message boards and blogs. References: Kaplan, A. & Haenlein, M. (2010). 'Users of the world, unite! The challenges and opportunities of Social Media" in Business Horizons (2010) 53, 59-68. Retrieved via Curtin library catalogue. Mangold, W. & Faulds, D. (2009, July-Augus

Apologies. Reposted the article but the link still doesn't work. You can access the full article in the Curtin library catalogue: Mangold, W. & Faulds, D. (2009, July-August). Social Media: The New Hybrid Element of the Promotion Mix in Business Horizons. 52(4) 357-365

This article published in the First Monday Journal provides a case study of how video conferencing was used by teachers for education purposes. Lessons learnt from this case study can be implemented by a business looking to establish a collaborative team communicating through the use of video conferencing. The case study segmented the benefits into four areas, other places, other times, other senses and other brains. The teachers found that videoconferencing was effective in motivating its students as they were communicating with people around the world. Organisations can take this learning and use it in the workplace by connecting like-minded individuals who are located in different offices/countries. This has the ability to motivate and inspire other team members and will potentially lead to more successful outcomes being achieved. Members of the project found that sometimes it was more convenient to videoconference as each member could suggest a suitable time to meet. However this would not always benefit teams communicating with people in other countries as they could be affected negatively by time differences. However team members were able to use the recording function to ensure information was always accessible in the future. The case study found that video conferencing gave team members the ability to use other senses other than just hearing to experience the communication. By being able to see people reactions, facial gestures and body language the communication process was improved and collaboration was easier. As the saying goes "many hands make light work" with the more brains included in the collaborative process different ideas and approaches can be discussed. With increased focus on cost saving, video conferencing provides a cost effective way to ensure that the best employees are included in the collaborative process.

Subject: How online collaboration has affected the software development industry Reference 4 Shared Waypoints and Social Tagging to Support Collaboration in Software Development By Margaret-Anne Storey, Li-Te Cheng, Ian Bull, Peter Rigby (2006) ABSTRACT This paper presents the conceptual design of TagSEA, a collaborative tool to support asynchronous software development. Our goal is to develop a lightweight source code annotation tool that enhances navigation, coordination, and capture of knowledge relevant to a software development team. Our design is inspired by combining "waypoints" from geographical navigation with "social tagging" from social bookmarking software to support coordination and communication among software developers. We describe the motivation behind this work, walk through the design and implementation, and report early feedback on how this lightweight tool supports collaborative software engineering activities. Finally, we suggest a number of new research directions that this topic exposes. (Rigby, 2006) Full document available from http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.136.3988&rep=rep1&type=pdf TagSEA software/code available from http://tagsea.sourceforge.net/download.html Bibliography Rigby, P. S., Margaret-Anne; Cheng, Li-Te; Bull,Ian. (2006). Shared waypoints and social tagging to support collaboration in software development. Paper presented at the CSCW'06, ACM http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.136.3988&rep=rep1&type=pdf

Review of article - Shared Waypoints and Social Tagging to Support Collaboration in Software Development This article reviews the development and purpose of TagSEA and gives us an understanding of the technology and why it is useful for software development collaboration. This is software that is designed to allow developers to place collaborative annotations attached to specific locations in source code. This is a professionally written article that looks at both why the software was developed and how it works, including a trial evaluation of the software. It also includes information on what it is written in (java) and what it works as part of (eclipse IDE). The article reviews what it can be used for and includes images displaying the look and feel of the software but does not explain how to use the software itself or provide a link to further information. However research on the internet has provided a link http://tagsea.sourceforge.net to where the software is available. The site where the software is located provides further information on how to use the software and links for downloading it as well as information about further developments. Both the article "Shared Waypoints and Social Tagging to Support Collaboration in Software Development" and the website appear to be written/designed to be read/used by people with technical skills i.e. developers and tends to use a significant amount of specialised terminology. Rigby, P. S., Margaret-Anne; Cheng, Li-Te; Bull,Ian. (2006). Shared waypoints and social tagging to support collaboration in software development. Paper presented at the CSCW'06, ACM Retrieved from http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.136.3988&rep=rep1&type=pdf

Subject: How online collaboration has affected the software development industry Reference 3 Continuous Coordination: A New Paradigm to Support Globally Distributed Software Development Projects by David Redmiles , André Van Der Hoek , Ban Al-ani , Tobias Hildenbr , Stephen Quirk , Anita Sarma , Roberto Silveira , Silva Filho , Cleidson De Souza , Erik Trainer ABSTRACT Along with the rapid globalization of companies, the globalization of software development has become a reality. Many software projects are now distributed in diverse sites across the globe. The distance between these sites creates several problems that did not exist for previously collocated teams. Problems with the coordination of the activities, as well as with the communication between team members, emerge. Many collaborative software engineering tools that have been used to date, in global software development projects, exhibit a fundamental paradox: they are meant to support the collaborative activity of software development, but cause individuals and groups to work more or less independently from one another. The underlying issue is that existing software engineering tools, such as configuration management repositories, issue trackers, and workflow engines, separate time and tasks in concrete but isolated process steps. Designing tools based on the premise that human activities can be codified and that periodic resynchronization of tasks is an easy step reflects poor understanding human nature. We therefore propose a new approach to supporting collaborative work called Continuous Coordination. Underlying Continuous Coordination is the premise that humans must not and cannot have their method of collaboration rigidly dictated, but should be supported flexibly with both the tools and the information to coordinate their activities and to collaborate in their activities as they see fit. In this paper, we define the concept of Continuous Coordination, introduce our work

Review of article - Continuous Coordination: A New Paradigm to Support Globally Distributed Software Development Projects This is quite a useful paper about current issues relating to the collaboration of software development and though it does not appear to have been published it is still a well-researched review of the topic. It focuses on the developing technology and changing methods of collaboration when developing software. It reviews a number of issues such as coordination issues that may arise between different sites that are working on a collaborative project together and looks at why these issues arise when developers and designers are working with current versions of collaborative software. It further focuses on why these issues arise and then reviews some of the software that is currently under development that may fix these issues. The software that it reviews includes YANCEES notification service that is an automatic publication/subscribe service for keeping software collaboration coordinated; Palantir workspace awareness tool that is an enterprise-level integrated analysis platform that works on a client/server model; Ariadne that is a tool for the collaborative searching/analysis of databases/source code and the graphical visualization and tracking of such searches; the TriVis which is a utility for graphically tracing collaborative software development and interactions and finally WorldView which is similar to TriVis but can extend from visualising design models to high level representations of development team interactions. Overall this is a very interesting article about the future direction of software development collaboration Redmiles, D. V. D. H., André; Al-ani, Ban; Hildenbr,Tobias; Quirk, Stephen; Sarma, Anita; Silveira, Roberto; Filho, Silva; De Souza, Cleidson; Trainer, Erik Continuous Coordination: A New Paradigm to Support Globally Distributed Software Development Projects. Retrieved from http://citeseerx.ist.psu.edu/viewdoc/dow

Subject: How online collaboration has affected the software development industry Reference 1: Online Collaboration and Agile Software Development By Doug Poirier, January 11, 2007 ABSTRACT Agile software development requires input from all team members, and such collaboration is most effective when everyone participates. (Poirier, 2007) Full document available from http://drdobbs.com/architecture-and-design/196900197 ThinkTank software is available from http://www.groupsystems.com/ Bibliography Poirier, D. (2007). Online Collaboration and Agile Software Development. Dr.Dobbs Retrieved from http://drdobbs.com/architecture-and-design/196900197

Review of article - Online Collaboration and Agile Software Development This article is in an online magazine http://drdobbs.com and is aimed at software developers. The article is not peer reviewed but is by a software developer writing for other software developers in a well-respected magazine. It does not initially focus on using collaborative software development tools but looks at the issues and problems that affect remote groups attempting to collaborate on developing software without the assistance of collaborative software. It is written in an easy going manner and the author talks about issues that he has personally experienced. It then starts to focus on the issue of collaborative software and on the online collaboration tool called ThinkTank that is available from GroupSystems (http://www.groupsystems.com) and reviews details the use of the software in a trial setup. At this point a number of features of the software are outlined and screen dumps showing some of the features of the software are also included. A review of the article and a latter review of the GroupSystems website did make it clear that the ThinkTank software is more of a collaborative meeting software rather than software that developers use to collaborate when doing actual programing, but it is still a useful piece of software for developers to use when communicating between multiple sites. Poirier, D. (2007). Online Collaboration and Agile Software Development. Dr.Dobbs Retrieved April 8, 2011, from http://drdobbs.com/architecture-and-design/196900197

This article stresses the importance of social media in the promoting of a company's brand or products. Social Media collaboration, according to Kaplan, enables 'the joint and simultaneous creation of content by many end-users'. For advertising social media provides platform which enables customers to partipate in the creation of the brand by generating feedback and product reviews. Mangold and Faulds argue that, for potential customers, online content which is generated by other consumers is typically regarded as more trustworthy than traditional advertising messages. Essentially, social media messages are more likely to be believed and responded to than direct-marketing on the other hand, social media also means companies have less control over the course of discussion. They argue,'while companies cannot directly control consumer-to-consumer messages, they do have the ability to influence the conversations that consumers have with one another'. Mangold and Faulds argue, used correctly, social media has become an important tool, which allows companies to not only talk to customers but also allows customers to talk to each other. Social tools, they suggest, provide customers to obtain information about companies and products and can aid them in the decision making and purchase process. Creating networks of social relationships with potential customers is a strong tool, which aids in the promotion of a brand but it also provides important tools to help managers achieve the company's missions and goals. Some tools companies can use to communicate with customers include company websites, YouTube, eNewsletters, message boards and blogs. References: Kaplan, A. & Haenlein, M. (2010). 'Users of the world, unite! The challenges and opportunities of Social Media" in Business Horizons (2010) 53, 59-68. Retrieved via Curtin library catalogue.

My topic is advertising and social media. I am specifically looking at the way companies are using social media tools to build connections and promote their brands and their products via company controlled crowd-sourcing and customer-driven discussion.

My topic is the collaboration practices of open source software development. You can access this article by logging into ACM via the Curtin Library website.

OVERVIEW: Open Source Software is software, built largely by volunteers, for which the source code is publicly available (p. 310). Such an approach is useful as a cheaper, high-quality alternative that can compete successfully with commercial products (p. 309, p. 343). This resource delves into the intricacies of Open Source Software (OSS) development by examining two prominent OSS projects: the web server Apache and the Mozilla web browser. In addition to providing detailed findings on the development processes that led to the early releases of both products, this comparative case study gives useful insight into the working practices and organisational structures of open-source developments, along with the tools that shape (and are shaped by) these working practices. As outlined in this paper, "decentralized workspaces" and "asynchronous communication" are very significant concepts in relation to OSS development (p. 317). Because there is no set schedule and contributors can do as much or as little as they like, constant communication through email and USENET groups is identified necessary to keep all contributors up to date. Other key tools used in the development of OSS are Concurrent Version Control Archive or CVS, which keeps track of each change made to the source code (comparable to wiki software); and bug-reporting databases, which enable the wider community to submit reports. The specialised nature of these tools suggests they are often purpose-built for the project, and the paper gives three examples from Mozilla - Bugzilla, Bonsai, and Tinderbox - which support this. In short, both through examining the control mechanisms, contributor involvement, and defect control practices; and through outlining specific tools that are invaluable in OSS development (and how they are used), this paper provides valuable insight into the nature of OSS development processes.