Are Grudin's challenges up to date?

According to Grudin [1994] there are eight main challenges that groupware developers might face. Since these were done in -94 and the application development has evolved, it is intresting to see whether these challenges still apply. I'll pick those which I feel are not as important anymore, and try to explain why that is.

1. Disparity in work and benefit. Groupware applications often require additional work from individuals who do not perceive a direct benefit from the use of the application. This might still be important to think of when developing but the effects of it has greatly reduced, due to better internet connections etc. For example, one could work with Googledocs just as he would on an offline text editor, since most groupware parts of the application like saving and showing it to other group members, is done automatically.

2. Critical mass and Prisoner's dilemma. Groupware may not enlist the "critical mass" of users required to be useful, or can fail because it is never to any one individual's advantage to use it. Like I mentioned above, the groupware applications have evolved a lot, and most of them are usually just as useful to use for one person than they are for many, which is why the "critical mass" is so small that it can be reached even with one user.

6. Difficulty of Evaluation. The almost insurmountable obstacles to meaningful, generalizable analysis and evaluation of groupware prevents us from learning from experience. Sure, the evaluation may take longer than normal application and it might be needed to look from different perspective and concentrate on different issues, but I feel that Grudin's explanation of this issue is more of an excuse to "I don't want to learn new techniques and change my viewpoint", and thus I don't see how this has ever been an issue.

I feel that rest of the challenges Grudin presented are still more or less accurate and should be taken into consideration when developing groupware applications.

References:
[Grudin, 1994] Jonathan Grudin, Groupware and social dynamics: eight challenges for developers. Comm. ACM 37, 1 (Jan. 1994), 92-105.

Fruits of the first lecture

When I came to this course my idea of groupware was that it was something that multiple persons could work on simultaneously. Usually the picture in my head was something like a table with a huge touch screen on it and group of people using it at the same time.

However, our first lecture introduced to me a much wider and specific definition. According to Ellis, Gibbs and Rein (1991), groupware are "Computer-based systems that support groups of people engaged in a common task (or goal) and that provide an interface to a shared
environment."

Another thing that our first lecture clarified to me was that groupware doesn't need to be simultaneous. Multiple people can work on something at different times. Or even at different places. (Ellis, Gibbs, Rein, 1991; originally, DeSanctis & Gallupe)

Nice observation was also that many of the programs and tools I use daily, are actually groupware. For example Dropbox - which Aleksi tells more about here - is an excellent tool. I don't actually use it as groupware, but rather as a small, free backup tool. Also Google Docs is quite handy at times. And of course, Wikipedia.

Groupware & Small Businesses

Groupware or CSCW tools are a big business for corporate giants like IBM and Microsoft. However, the products like IBM Lotus Notes or MS Sharepoint are expensive and too wall-to-wall solutions for small (or micro) businesses. The Open Source project Liferay also seems a bit over-sized for (e.g.) a consult office of six people. Still, many of such companies could, unquestionably, benefit from the use of groupware.

Companies of, let's say, 5-10 employees rarely have PC advisers or extensive computer support services. Thus the easiness of installation, use and maintenance of the groupware is crucial. They also seldom have the time or the money (or the desire) to really focus on the procuration process of such tool.

Luckily enough, there are options beyond Lotus Notes, Sharepoint or self-tailored wiki mash-ups. One risk-free example is TeamWox Collaboration Software, which is specifically designed for small businesses. It holds all the essential features (such as HR, documents management, e-mails, discussion board, task management, accounting etc.), but requires no outside integration or maintenance. And for ten users or less, it is free.

Round up of collaboration platforms

I decided to take a look of currently offered collaboration platform products. The list is not exhaustive, but my opinion is that these are notable players in the field.

What is collaboration platform then? My understanding is that collaboration platforms are software platforms that offers common functionalities and interfaces  for building applications targeted for user groups and communities.  These server based applications have usually some built in features  like user management,   fine grained access control, messaging  and file sharing. Application interface and data layer is usually offered for  building  new applications.  Some standardisation efforts exists to make and applications api vendor neutral, I think most important one regarding this is JSR168 / 286, but maybe more about this later.

Licensing cost of these products are high,  as it is actually possible to use the products as a base for  company wide application infrastructure and messaging. however,  Liferay is available as free community edition as  alternative for commercial products.

IBM Lotus Notes.  Notes uses Client / Server based architecture. Client program installed for workstations allows access for applications, email and includes developer tools. Browser access is also supported . Data is saved  non-sql databases suitable for multimedia and web based application development.  Applications can be replicated between servers and organisations. Notes has built in email and  instant messaging.  Wide selection of  OSes is supported, and communications can be strongly encrypted. Newer versions supports JSR -standards. 

Microsoft Sharepoint Competitor for Lotus Notes offers integration for office products
and file sharing.  MS SQL server is  used for data storage. Applications  are called web parts.  Windows is only option for OS. 

IBM Websphere Portal server  IBM's Java based offering for groupwork, collaboration and integration. Platform offers standardized JSR 168/286 application interface. Applications are called  portlets, and they can be arranged to web interface. Portlet library contains  huge selection of applications ready for installing.  Primary data store is IBM DB2.  Available for  many operating systems.

Liferay Similar to IBM portal server, but open source. JSR 168/286 Portlet apis are fully supported  and product supports many commercial and open source databases including Oracle, db2, Mysql, Postgres and many more. JSR 168 / 268. Many ready made portlet -applications are bundled  with product. All operating systems are supported where java is available. Side product Social office is "Liferay distribution" bundling common collaboration portlets together.

What is Groupware?

Groupware, collaborative computing, workgroup computing, multiuser applications, computer-supported cooperative work applications… A dear child has many names. I decided to create the first groupware blog entry simply defining what is meant by term groupware.

As mentioned at first lecture, groupware is software for groups that is designed to support group work and help groups of people to achieve their common goals by communication, collaboration and coordination [Ellis, Gibbs, Rein, 1991]. Examples of groupware include desktop- and videoconferencing, coauthoring features and applications, email, bulletin boards, meeting support systems, voice applications, workflow systems and group calendars, among others [Grudin, 1994].

In conclusion, according to Grudin when defining the meaning of groupware, it would be useful to consider questions “Was this software designed to support groups?” and “Is it being used to support groups?” [Grudin, 1994].

References:
[Ellis, Gibbs, Rein, 1991] Clarence A. Ellis, Simon J. Gibbs, Gail L. Rein, Groupware: some issues and experiences. Comm. ACM 34, 1 (Jan. 1991), 38-58.
[Grudin, 1994] Jonathan Grudin, Groupware and social dynamics: eight challenges for developers. Comm. ACM 37, 1 (Jan. 1994), 92-105.

- Minna