Software Selection Tutorial

bas says : For more information about Software Selection visit my
Software Selection Tutorial at
http://www.softwareprojects.org/software-selection-intro1.htm

Cheers
Bas

salcorp says : Nice... I think a few people will benefit from this text.

=)

Bernard says : Ah, but what about business applications that solve problems the company is not even aware that they have? Ie. step #1 "Defining needs" is not always something that those ingrained with a particular business culture are capable of determining IMO.

I think that a previous step might prove beneficial:

- research available solutions on market (compare benefits/features)

Sometimes, this process will spark one to identify business needs that they would not otherwise have considered.

Alf says : I will definitely second that, Bernard.
Great new SW opens opportunities for those who are told AND understand the benefits. They are not necessary aware of the possibilities on beforehand..

bas says : Must have been magic ;) I just started this weekend with a kind of approach for small and medium size businesses on how to asses their needs themselves (and yes comparing existing products to spark ideas is one part of it).

The fifth discipline by ??? Senge is the spark of this idea. He describes some archetypes mechanism with a company that can describe common problems. (problem can also be growth). I'll write some stuff about it when i have time (hmmm when will that be?) and put it online.

It should be a better start for the software selection process.

But for those new to it... it still helps if you read it :D

Cheers
Bas

ross_valusoft says :

Bernard>Ah, but what about business applications that solve problems the company is not even aware that they have? Ie. step #1 "Defining needs" is not always something that those ingrained with a particular business culture are capable of determining IMO.

I think that a previous step might prove beneficial:

- research available solutions on market (compare benefits/features)

Sometimes, this process will spark one to identify business needs that they would not otherwise have considered.

Bernard,

I would go back one step, although this selection of software activity may already be the result of this process. The process I am referring to is "Business Process Re-engineering" (BPR).

In my experience, this process is best undertaken by "outsiders". Those inside are too close to the situation to be able to apply fresh eyes to the status quo. An inside guide is always needed to introduce the consultant around and provide evidence that the top management want this guy treated fairly in his/her investigation.

The result may be new software, and / or a new way of doing business with existing systems.

So simplify before computerising.

dossana says : mybe? ok onswer ===> www.procosavi.net

pmkb says : We have set up a system where members may post project management software reviews. Members have already started posting reviews and as more are posted, it may help anyone who is evaluating said systems for their particular needs.

bas says : Hi PMKB,

Your reviews look interesting... well actually the entire site does :)

The software selection we discussed in this thread was mainly about the process in general and not specific for PM software.

What is your opinion on the matter?

Cheers
Bas

pmkb says : Ah.. sorry about that. I'd agree with the earlier comments that it is important to take care with defining the needs. In larger companies, sometimes the end users are not the ones with the strongest voices in the process and it ultimately leads to failure.

P.S. Thanks for the kind words!