[memracom]

Read the SWEBOK guide https://computer.centraldesktop.com/home/viewfile?guid=49744... and over time, ask the team to focus on one of those areas and decide how to improve their game. In general, get the team to discuss issues and decide on solutions. For instance, Agile. If you read the Agile manifesto, a short text that emphasizes communication, you get a very different picture of how to do Agile than you get from any Agile books or consultants.

Make sure that you have good controls in place, and in software that mainly means code reviews and QA. Usually QA is a specialist role but you may find it better to rotate people through a one or two month stint as QA people. You will likely see more automation of QA if a software developer is doing the job.