Comments on: How (not) to evaluate project management software http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/ work management software Tue, 23 Feb 2010 16:08:01 +0000 http://wordpress.com/ hourly 1 By: JP Elverding http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/#comment-337 JP Elverding Tue, 26 Jan 2010 14:28:34 +0000 http://blog.twproject.com/?p=496#comment-337 After some trying I have been testing several products. As I'm an Apple user I was pleased having XP as well on it as some programs were not Mac-savvy. I could even find out a lot without RTFM. Needed it though! Imagine my surprise finding that TW worked at my Mac, with far less IT-skills than I had feared were necessary. I liked the way I could use IT-related projects as well as non related projects, like a major trade fair in march. After my own consideration, consulting other potential users at my customer and cracking some fine nuts today the company that hired me has bought the first batch of licenses. Apart from the product it was the support that made my day and made my propose teamwork. For after all, even interactive manuals cannot replace a skillful person. After some trying I have been testing several products. As I’m an Apple user I was pleased having XP as well on it as some programs were not Mac-savvy. I could even find out a lot without RTFM. Needed it though!
Imagine my surprise finding that TW worked at my Mac, with far less IT-skills than I had feared were necessary. I liked the way I could use IT-related projects as well as non related projects, like a major trade fair in march. After my own consideration, consulting other potential users at my customer and cracking some fine nuts today the company that hired me has bought the first batch of licenses.

Apart from the product it was the support that made my day and made my propose teamwork. For after all, even interactive manuals cannot replace a skillful person.

]]> By: Wil http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/#comment-193 Wil Thu, 18 Jun 2009 06:51:43 +0000 http://blog.twproject.com/?p=496#comment-193 I agree in part. One can unfortunately not "test drive" all available options out there to start off with. I started with more than 150 possibilities. I've now brought this number down to 4 by using "elimination lists" which in part relied on feedback I got from websites, vendors, and even users. With 4 in hand, I've started testing on trial versions of the software. I've learnt, yet again, how important it is to really listen to what it is the possible client is asking, instead of trying to tell them what they should allow you to tell them... By the way, Teamwork will be tested next - based on what is available on your web site, the things you've said on your blog, the methodologies you subscribe to as an organisation, etc. Well done! I agree in part. One can unfortunately not “test drive” all available options out there to start off with. I started with more than 150 possibilities. I’ve now brought this number down to 4 by using “elimination lists” which in part relied on feedback I got from websites, vendors, and even users. With 4 in hand, I’ve started testing on trial versions of the software.

I’ve learnt, yet again, how important it is to really listen to what it is the possible client is asking, instead of trying to tell them what they should allow you to tell them…

By the way, Teamwork will be tested next – based on what is available on your web site, the things you’ve said on your blog, the methodologies you subscribe to as an organisation, etc. Well done!

]]> By: ziobrando http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/#comment-62 ziobrando Thu, 16 Apr 2009 10:01:20 +0000 http://blog.twproject.com/?p=496#comment-62 I think the whole stuff of software selection is incredibly context dependent. Every tool has pros and cons, but these have bigger benefits and drawbacks depending on the context. Moreover, I started to consider usability as one of the key factors (I am tempted to say THE key factor, but that would not be context dependent...). Simply put: you can't ask companies about usability of their product. The only way to address usability is just try the typical task and see how it fits with the typical person doing that task in your context... (you van obviously do a lot more, but that's step number one). I think the whole stuff of software selection is incredibly context dependent. Every tool has pros and cons, but these have bigger benefits and drawbacks depending on the context.
Moreover, I started to consider usability as one of the key factors (I am tempted to say THE key factor, but that would not be context dependent…). Simply put: you can’t ask companies about usability of their product. The only way to address usability is just try the typical task and see how it fits with the typical person doing that task in your context… (you van obviously do a lot more, but that’s step number one).

]]> By: Pietro Polsinelli http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/#comment-58 Pietro Polsinelli Wed, 15 Apr 2009 08:29:58 +0000 http://blog.twproject.com/?p=496#comment-58 Fixed, thanks. Fixed, thanks.

]]> By: enki http://blog.twproject.com/2009/04/14/how-not-to-evaluate-pm-software/#comment-56 enki Tue, 14 Apr 2009 16:19:49 +0000 http://blog.twproject.com/?p=496#comment-56 Hey was checking out your site and noticed: "Are you a Twitter addicted that traces all activities with twits? You can import all of those or only the relevant ones as timesheets in Teamwork. You can also send all your Teamwork worklogs to Twitter!" I think you mean "Are you a twitter addict". I do dig the idea of the twitter integration though! Hey was checking out your site and noticed:
“Are you a Twitter addicted that traces all activities with twits? You can import all of those or only the relevant ones as timesheets in Teamwork. You can also send all your Teamwork worklogs to Twitter!”

I think you mean “Are you a twitter addict”.

I do dig the idea of the twitter integration though!

]]>