Preparation for survey on devonfw-ide usage

[mustafaokyay]

devon-ide is evolving very fast. There were a lot of new features and quality of life improvements done in the past which really helped the users to efficiently use their valueable time. Nevertheless there still might be some features (and maybe bugs, or unefficient workflows) which prevent developers from adapting the devon-ide.

Our first step is to brainstorm and come up with questions which we could ask the users about their experience with the devon-ide and the non-users about why they do not use it.

An example question could be: In your opinion, which key features are still missing in the devon-ide?

Use the comment-section below to brainstorm

[CREITZ25]

Which components are preferred or used the most? Which component has never been used? What could be improved on existing components? Which components are still missing, with a weighting in terms of urgency?

[Ttring]

• Is there a problem navigating the devonfw-ide documentation?

• What hinders you from using devonfw-ide in your team?

• What's your biggest concern of using devonfw-ide ?

• How did the installation of devonfw-ide go?

• Do you find it easy to integrate with other software ?

• What problems did you often encounter while using devonfw-ide?

• How likely are you to recommend this software to others ?

• Do you get enough support from community ?

• What do you like the most about devonfw-ide ?

• Did devonfw-ide improve your team's efficiency in setting up the environment ?

[hohwille]

For the questions we should also start thinking about the answer options. For some questions we may need to allow free text input via text-area but in most cases we want radio-selection from a given option or rating, some might be multiple choice...

[hohwille]

Options for a survey tool to implement the survey would be lime-survey or microsoft forms.

[cinnamon-coder-hub]

The questions look well.

Regarding the answer options I wanted to mostly sum up our thoughts from todays refinement meeting now.

We could divide the questions into questions of type

1. with answers: yes/no/does not concern me/no response
2. with answers on a scale from 1 to 5, or even 0 to 5 with 0 as "does not concern me/no response", 1 as most negative and growing to 5, the most positive response.
3. With a block for a written answer. This block could also be combined with type 1 and 2 in some cases.

Also it could be useful to start with a question like "Have you been using the devonfw-ide before?" and after that a second and last question "What hinders you from using devonfw-ide in your team?" (as mentioned above), if the first answer was negative.

Regarding the answers "does not concern me" and "no response" we should maybe consider to only give these options if we think that in some cases a question can't be answered. Otherwise there could be query results with an "overdose of no response" as answer.

Another idea from the team was to give the answering person the voluntary option to leave an e-mail or similar behind for us. This could be especially usefull if someone gives an interesting or concerning answer to a question of type 3.

[alfeilex]

Here are some idea's for open questions:

• How can devonfw ide be improved to provide a better experience in your development process?
• What is your favorite feature of devonfw ide?

and for questions with radio selections:

• Do you use devonfw ide for your private projects?