Which tool is most appropriate for a software development manager to track coding issues?

A defect log is the most appropriate tool for a software development manager to track coding issues because it specifically serves the purpose of documenting and managing bugs, errors, or defects identified in the software. This tool allows teams to capture detailed information about each issue, such as its status, severity, and the steps needed to reproduce it. By maintaining a defect log, the development team can prioritize fixes, ensure accountability, and track progress over time, which is crucial for delivering a high-quality software product.

In contrast, a risk report focuses on identifying and assessing potential risks to a project, which is broader and not specifically aimed at coding issues. A task board helps visualize tasks and workflow but does not provide detailed insights into specific coding faults. A change log records changes made to the software, such as new features or modifications, rather than tracking issues that may arise during coding. Each of these other tools serves valuable purposes in project management, but the defect log is uniquely tailored to the needs associated with coding issues.