{"id":524,"date":"2009-04-24T13:38:54","date_gmt":"2009-04-24T13:38:54","guid":{"rendered":"https:\/\/twproject.com\/blog\/?p=524"},"modified":"2016-06-13T07:09:28","modified_gmt":"2016-06-13T07:09:28","slug":"the-future-of-teamwork","status":"publish","type":"post","link":"https:\/\/twproject.com\/blog\/the-future-of-teamwork\/","title":{"rendered":"The future of Teamwork"},"content":{"rendered":"
\"Teamwork
Teamwork staff with JBoss gadgets.<\/figcaption><\/figure>\n

Well, first of all, does Teamwork have a future at all? Well, version 4 has now been out for almost 3 months, and it is been an outstanding commercial success, with a growth of about 400% with respect to the same 2008 period; in countries like Germany and Turkey our growth is really impressive, and in not exactly the best economic times. Aside from sales, it is the users and reviewers reaction that has changed drastically with the release of 4, they like not only the power of the application, they like the usability and user interface. So our great effort in this direction was not wasted \ud83d\ude42 : we always got positive feedback about the power of Teamwork, but rarely about usability. The feedback service<\/a> and the Teamwork error reporting are working great, and thanks for all the feedback received!<\/p>\n

Having the money to support more and more development opens great possibilities, and we\u2019ll keep the policy of transparency of our plans, so you\u2019ll just have to read our blogs and twitter streams<\/a> to know exactly what we are doing and intend to do. It\u2019s also a good feeling knowing that Java is not going to \u201cdie\u201d any time soon, now that Oracle and Sun are merging<\/a>. Good vibes come also from the NGO which we are helping with free licenses<\/a>, and Teamwork is used as teaching tool in really a lot of universities<\/a>.
\nOther nice effects of the release of version 4 are that we have a number of software houses working on plugins on the sources, and this adds to the already unique spectrum of IT and applications integrations.<\/p>\n

Now the usability considerations do not yet apply to all sections of Teamwork 4: like the business process module can now be proficiently used only by power users, that are not scared by hand editing of XML files, but yet that too is used in quite a number of cases.<\/p>\n

So of course in Teamwork’s future you will see a lot of work done on both usability and features. The version currently in production is 4.2, and we also have some plans for future versions.<\/p>\n

Usability<\/h2>\n

A very practical and convenient way to test usability is to use the usertesting.com<\/a> service; from this feedback we collected a lot of suggestions, which are currently being developed and will be released progressively, most already in 4.2. Some things which we thought were now easy to use, actually are not, and mostly for the first time user; we improved from version 3, but still the beginning part has some obstacles which could be removed.<\/p>\n

We also got some good suggestions by watching Amy Jo Kim from Shufflebrain<\/a> work on positive feedback to the users, see Putting the Fun in Functional: Applying Game Mechanics to Functional Software<\/a>; we plan a future blog post with more details. We just became aware that the fact that version 4 gives more “positive feedback” to users is probably an important factor of its success. Already 4.2 will be more reactive, we hope even more fun.<\/p>\n

Features<\/h2>\n

The main features in production for version 4.2:<\/p>\n