Groupware
Implementing Groupware: Comparing Costs and Benefits
There are many varying definitions of groupware yet all share a common attribute or characteristic of enabling collaboration, sharing knowledge and providing work teams with greater insight and intelligence into operations. The intent of groupware is to create a scalable, reliable and agile platform for sharing information and knowedlge, both tacit and implicit, throughout distributed enterprises (Kline, 2001). Best practices in groupware encompass interdepartmental, intradivisional and enterprise-wide integration of content and knowledge management processes and systems (Corbitt, Martz, 2003). The benefits of such a pervasive platform for information and knowledge sharing has shown to deliver quantifiable gains in corporate-wide productivity and performance, leading to greater profitability as well (Lukosch, 2004) (Merono-Cerdan, 2008). With so many benefits and contributions of groupware, it's surprising that more organizations don't adopt these series of technologies to attain their corporate-wide information and knowledge management strategies. In reality implementing groupware is exceptionally difficult because it forces people in companies to change how they work (Chen, Hao, 2002) (Ellis, Gibbs, Rein, 1991). It takes an exceptional level of trust in the implementation and leaders of the implementation to make groupware projects translate into long-term change within any enterprise (Corbitt, Martz, 2003). The technology is the easy part; getting people to change is hard. This paper compares the costs and benefits of groupware, deciding if it is worth it as an enterprise strategy.
With all of these points of validation showing why groupware is such an excellent investment from a process automation and technology standpoint, there are just as many factors that make groupware one of the most difficult to implement.
The most costly component of any groupware implementation is change management, or the ability to get people to change how they do their jobs (Wallace, 1997). This is the Achilles' heal of any enterprise software implementation and is particularly problematic for groupware implementations as those in any company with the greatest level of information are often the most reluctant to let go of it (Corbitt, Martz, 2003). As the economy has progressively gotten worse, it is common to find knowledge workers continually hoarding information and not sharing it, for fear of…
What's becoming the collaborative catalyst of making teams work more efficiently together has been the transparency and immediacy of information now available in these collaborative workspaces, creating increased trust throughout groups in the process. Development teams no longer have to rely on just a single team person to gain access to a drawing or document, these collaborative workspaces or portals can provide check-in/check-out functionality for any document a team
Soft Systems Techniques in the Preparation of Information Technology as a Systems Manager Company Systems Consulting process and model Systems approach, client relationships Company Culture Client defenses, attachments to existing systems Interaction with the company culture in order to facilitate change System and Culture working together Dependancy issues Lewin Company Systems Consulting process and model Systems approach, client relationships Company Culture Client defenses, attachments to existing systems Interaction with the company culture in order to facilitate change System and Culture working together Dependency issues Lewin's model of
The following diagram represents the structure of the idea. Figure 2. Project flow pursuant to Plan Abu Dhabi 2030: Urban Structure Framework Plan Objectives of the Study The overarching objective of this study is to build a solid portfolio management application that connects all the local governments of Abu Dhabi emirates in ways that will allow them to collaborate on various projects pursuant to Plan Abu Dhabi 2030 through one unified system
Knowledge Management Toolkit A data warehouse encompasses and provides access to all the company's information to whoever needs access to it. A warehouse literally means a storehouse, and the information within an organization may be distributed within one computer or with many computers, form one single warehouse. They may contain several databases and all types of information, and in a large variety of different formats. However, all the above information and
Project Management: Case Study in Managing a Complex Shipyard Project in Singapore Background of Complex Shipyard Construction Project Company background Project Overview and Objective Work Process of Building Construction Issue Analysis in Shipyard Construction Project Management Literature Review of Project Management Issues in Scope Management Methodology of Scope Management Lessons Learned from Scope Management Issues in Cost Management Methodology of Cost Management Lessons Learned from Cost Management Issues in Human Resources Methodology of HR Management Lessons Learned from Human Resource Management Case Study in Managing a
This is why a Learning Organization will always be very competitive on the market. It will be able to adapt to the changes in the said market and thus profit. Also, a very important element in a Learning Organization is the fact that it and its members share a vision. This is why they are learning and evolving, because they have a goal. Unlike other companies where the employers
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now