improvement of old development forms

This is a vague question, but I will answer the key points because I have something to feel.

Other improvement points

What is the ruler of your organization?
First, let's define anything here.I'll think of ways to improve it.

However, I have never worked in another software development company before, and I don't know what to do with it like this or develop it like this these days, so I'm not sure if there's a better way to do it.

Anxiety means that the purpose is unclear or that there is not enough evidence to accomplish it.Even if I try to explain it, it's not convincing.

If it is accepted as "normal" or "fashionable," it should have become a "normal" and "fashionable" development style.
Think it's difficult if you can't explain exactly what's good about your organization.

I often hear the word DevOps when I look into various development methods.

You should learn why teams that hire DevOps and others do that.As you may feel, it may be a completely different purpose.

Source Review: Not
version control software:not used
Test Code: Do not write
bug management:Excel

Now let's analyze the reason why the work came around.I think there will be various keywords such as personification.
It's realistic to put together one keyword at a time to see if you need to improve it (manager will be happy), how to improve it, and how to persuade them.

For simplicity,

• Deploy a challenge management system (de-Excel, easy to collaborate with!)
• Leave the change history to the version control software (it's troublesome to manually keep the change history!You're wrong!)
• Associate changes to the challenge with the above two

I think it's okay to start with these.