A well-designed developer survey is only the first step towards measuring team health, the important part is knowing how to listen to the results.
Software teams can be a hard group to measure. Raw output metrics like lines of code written, features shipped, and bugs squashed can go some way towards telling you how a team is doing – but they leave a lot unsaid. Do your developers feel they are being used effectively? Are they able to get the focused time they need? Or are they managing to ship in spite of bureaucratic obstacles, too many meetings, and a lack of direction? To get that kind of information, you need to conduct a developer experience survey.