Sunday, April 30, 2006

 

Teamwork 3 sections and features are done

We made it: teamwork 3 as an application is finished. It took about 4000 hours of development, including programming, design, promoting and supporting it (thanks to Teamwork, we can track this wery well).

In this two years we tried to develop as much as culturally as well as from the development point of view. We studied interface design, web application architecture, project management culture, workgroup software, calendar tools, and many other stuff.

Some readings and links that were important:

JBlooming framework www.jblooming.org .
Jbpm http://www.jbpm.org/
Hibernate www.hibernate.org
Gavin King, Christian Bauer, Hibernate in Action: Practical Object/Relational Mapping, Manning, 2004
JetBrain’s Intellij www.intellij.com
Microsoft Project interoperability http://mpxj.sourceforge.net
Erik Hatcher and Otis Gospodnetić, Lucene in Action, Mannings 2004
Joel Spolsky, User Interface Design for Programmers, Apress, 2001
Joel on software: www.joelonsoftware.com
Bruce A. Tate, Beyond Java, OReilly, 2005
Eliyahu M. Goldratt, Jeff Cox, The Goal: A Process of Ongoing Improvement, Gower Publishing Limited, 2004
Edward M. Reingold, Nachum Dershowitz, Calendrical Calculations,Cambridge University Press, 2001

Thursday, April 27, 2006

 

Teawork's blog

I've been posting on teamwork for quite a while on my blog, at ppolsinelli.blogspot.com. But Teamwork deserves a blog for itself.

We are on the eve of the most important release of Teamwork, 3.0. We will blog about what we are doing and how we progress in this crucial phase, about our choices, and the market and community response.

Have fun,

Pietro Polsinelli

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