This is an old revision of the document!
Back to 2014-proposals
Title: Software Quality Dashboard for Agile Teams
Proposer: Alexander Bogush
Type: Case-Study
Duration: 45 mins
Description:
It is common knowledge that prevention is better than cure—built-in quality and good design is more
efficient than thorough regression testing and bug fixing at later stages of development cycle. Yet it is not
uncommon to see complex code that has gone well beyond the point of no return, when it’s no longer
feasible to support any further development.
This presentation will describe a system for continuous monitoring of software quality metrics that we
have built on top of CI server, and how it is used to effectively manage technical debt and external quality
attributes in an agile environment, keeping it within healthy boundaries and avoiding degradation.
We will discuss code metrics (test coverage, c. complexity, code coupling, etc.) that we monitor and
what ranges and trends we found useful for a software house with a number of relatively small and
often independent C#/C++ projects. We will also review Lean and Agile techniques and freeware tools
(CruiseControl.NET, SourceMonitor, FXCop, Atomiq, internet TV screens, etc.) that we employed in the
development process.