This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Part of project management is technology independent. For example, you have to manage requirements, time, ....
A few important things for a tool perspective: 1) Source/version control - CVS (integrated in WSAD/RAD), Subversion, Clearcase, etc. Note that this can track individual contributions on a source code level. Not sure if I see the value in that though. 2) Task tracking - spreadsheet, MS PRoject, tracking tool, index cards, etc
The only thing I can think of that is different on a J2EE project is defining roles. For example, you should be aware of the J2EE roles (developer, assember, deployer, etc) even if one person does them all.
Originally posted by Vin Kumar: Especially tracking an individual's activities and contributions!
Software development is a team effort, so it's much more important to track the team's activities and progress. It's also much more important to have that data in everyone's head than in some database, so a big chart on the wall can be much more effective than a software tool. (You will still need some numbers for accounting. Often a simple spreadsheet is fully sufficient for that.)
Actually tracking individuals can easily damage the team.
I higly recommend reading the book "Peopleware".
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Mar 10, 2005
Hi Jeanne and Ilja, Thanks for your insight and suggestions. I really appreciate that.
I was just curious and wanted to evaluate one for future project, if I can!