2014:software_quality_dashboard_for_agile_teams
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2014:software_quality_dashboard_for_agile_teams [2013/11/04 08:40] – created jonjagger | 2014:software_quality_dashboard_for_agile_teams [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| **Duration**: | **Duration**: | ||
| **Description**: | **Description**: | ||
| - | It is common knowledge that prevention is better than cure—built-in quality and good design is more | + | 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 | 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 | + | 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.\\ | feasible to support any further development.\\ | ||
| \\ | \\ | ||
| Line 17: | Line 17: | ||
| what ranges and trends we found useful for a software house with a number of relatively small 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 | often independent C#/C++ projects. We will also review Lean and Agile techniques and freeware tools | ||
| - | (CruiseControl.NET, | + | (CruiseControl.NET, |
| development process.\\ | development process.\\ | ||
| \\ | \\ | ||
2014/software_quality_dashboard_for_agile_teams.1383554443.txt.gz · Last modified: 2016/06/11 14:05 (external edit)