In 3 steps to agile software selection – 1. The stakeholders and their stories

Listen to that topic within my podcast:

DAM Evangelist by Ulrich Leidl

Agile Software Selection Stakeholder
The stakeholders and their user stories is the first part of my three-part series on agile software selection. In my following posts, I would like to go into the three phases that are passed through in this process. Since my blog is known as a DAM blog, I will of course do this on the basis of the selection of a DAM system. The start of this selection process presupposes that the need for a DAM system has already been recognised. In practice, this part, convincing companies and users that they need a DAM system, is often the most difficult, but here I assume this hurdle has already been taken.

For many companies, it is a big step to find a “handy start” to a software selection process.

For many companies it is a big step to find a “handy” entry into a software selection process

Wie soll vorgegangen werden?

Do I just invite the usual suspects that I find through the first Google search (thus finding the providers that are happy to pay a lot for Google AdWords, but not necessarily the one that is best for me)?
For example, do you use the environment of your CRM/ERP partner (usually SAP…), or do you even write long lists of requirements that usually make little sense?
Definitely none of these methods are effective and efficient!
Manufacturers or future partners such as integrators are not invited to an individual demo until they are clear about the path they want to take with the new system and the core benefits they want to derive from it. Drawing up lists of requirements, on the other hand, is a pure time killer that unnecessarily delays a project. Moreover, these lists usually contain requirements such as “It must be possible to load files in the original.” A necessary and important function, but a DAM that does not fulfil this, is not a DAM.

From my years of practical experience in agile software development, I decided some time ago to adapt parts of this process for the selection of a DAM system. Regardless of the industry and the requirements, this selection process can always be used, it is goal-oriented, takes little time and is implemented very quickly.

The first step in this process is the selection of stakeholders. Stakeholders are persons/users who want to/will benefit directly or indirectly from the use of the DAM system.

On the side of the future DAM client, there should also be a role similar to that of the product owner in the Scrum process. It makes sense to complement the internal product owner with an external partner who has sufficient experience in the selection of a DAM system, who knows the DAM market well enough, who can accompany and evaluate the introduction of the system and who, above all, has knowledge of the “usual” pitfalls of such a process.

Identification of the stakeholders:

An immensely elementary and important point. The stakeholders will later work with the system or want to see that time and money can be saved by using the system. This choice has to be made very carefully.

Here, too, is the question at the beginning:

2 thoughts on “In 3 steps to agile software selection – 1. The stakeholders and their stories

Leave a Reply