The 3C Approach for Agile Quality Assurance Continuous Integration, Continuous Measurement, Continuous Improvement André Janus André Janus – IT Consulting Karlsruhe; University of Magdeburg Reiner R. Dumke University of Magdeburg Andreas Schmietendorf Berlin School of Economics and Law (HWR Berlin) Jens Jäger Jens Jäger Consulting Sindelfingen ICSE 2012, Zürich 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM 2012)
26
Embed
The 3C Approach for Agile Quality Assurance - … 3C Approach for Agile Quality Assurance ... Missing QA-Tools ... Combination of agile and (traditional) MetricsAuthors: Andre Janus
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
The 3C Approach for Agile Quality AssuranceContinuous Integration, Continuous Measurement, Continuous Improvement
André JanusAndré Janus – IT Consulting Karlsruhe; University of Magdeburg
Reiner R. DumkeUniversity of Magdeburg
Andreas SchmietendorfBerlin School of Economics and Law (HWR Berlin)
Jens JägerJens Jäger Consulting Sindelfingen
ICSE 2012, Zürich3rd International Workshop on Emerging Trends in Software Metrics (WETSoM 2012)
2
About me
● Jens Jäger
● Freelance IT Consultant
● Java, Ruby, Javascript, Web,...
● Agile methods
3
Agenda
● Motivation & Goal
● Project Context● Traditional and Agile Measurement & Metrics
● Agile Metrics● Number of Broken Builds/Number-Of-Failed-Integrations
● Process-Metric/Quality-Constraint● Broken Build = found bug● Dysfunctional effects: use as KPI● Problem: Infrastructur
Checkstyle PMD
9
Number-of-Broken-Builds
10
Agile Metrics
● Number of Tests
● Test Growth Ratio● Better than number of Tests for Brownfield-Projects● testGrowthRatio = ΔsourceCode / Δ#Testswith (usually)ΔsourceCode ≥0Δ#tests ≥ 0