Friday, September 28, 2007


Teamwork 3.2.1 is out: what's next?

This latest release contains an expanded agenda management, which now includes meeting management, and a lot of fine tunings; in particular, we worked on improving character encoding compatibility both in input data and in document names. Much help came from feedback of users of the online version.

So, what's next? Well, we are architecting and doing first draft development of Teamwork 4. Actually, more than a "4" version, we will create a new front end application, of which what is now Teamwork will be a sort of "backoffice". I can't reveal what the front end idea is, but we are aiming at drastically lowering the adoption barrier, which in our opinion is still the stumbling block of this kind of software.

Teamwork currently has an advantage over competitors in the refined model and in the "IT-biocompatibility" side; but we want it to become much friendlier on the interface side.

For the first time, Teamwork development may not be entirely self founded; we are having first contacts with investors (actually, being contacted by VCs after the Jolt Award gave us the idea of searching external founding), and if you want more information, write me (ppolsinelli at open - lab [dot] com) and we'll get back to you.

Pietro Polsinelli


Teamwork as tool for Project Management courses

Given its refined modeling capacities, Teamwork is often chosen by universities as supporting application for project management courses.

It is currently used in universities located in Germany, Austria, Spain, Portugal, Denmark, USA, Africa (Monash University), Chile, Saudi Arabia.


Wednesday, September 26, 2007


Teamwork video


Friday, September 14, 2007


Audit trail

We updated the audit trail module for 3.2 releases; it gives a complete and readable audit of all the "auditable" objects. It doesn't seem to impact performance too much, and results are optimized for inspection.

We used Hibernate's interceptors at session level, so the module has garanteed completeness: there is no "hand-maintenance" to be done on persistent objects, which is a further guarantee for certification purposes.


This page is powered by Blogger. Isn't yours?