Technical Debt as a Preferred Indicator for Software Quality

When talking about software quality, most of articles cover best practices and development process to implement, such as identify risky components, do frequent code reviews, refactor complex artifacts, check coding rules, etc. However, few guidelines can be found around the project itself. Yet, deploying a solution for software quality management should be considered as a project, with its stakeholders (project manager, developers, QA manager, subcontractors), milestones and - like any other management project, the common traps to avoid. Thus, like in any other management project, indicators are strategic and will reflect your quality approach by making it concrete. Indicators are the main expected deliverables, and this is especially true for a Governance Program of your software developments.

ファイルサイズ : 152.54 KB
MD5 hash : fc5769e0f7e832c1f464adf6062a39bd


* 必須