ScrumLint: Identifying Violations of Agile Practices Using Development Artifacts

September 03, 2018 Β· Declared Dead Β· πŸ› IEEE/ACM International Conference on Connected Health: Applications, Systems and Engineering Technologies

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Christoph Matthies, Thomas Kowark, Keven Richly, Matthias Uflacker, Hasso Plattner arXiv ID 1809.00634 Category cs.SE: Software Engineering Citations 11 Venue IEEE/ACM International Conference on Connected Health: Applications, Systems and Engineering Technologies Last Checked 4 months ago
Abstract
Linting tools automatically identify source code fragments that do not follow a set of predefined standards. Such feedback tools are equally desirable for "linting" agile development processes. However, providing concrete feedback on process conformance is a challenging task, due to the intentional lack of formal agile process models. In this paper, we present ScrumLint, a tool that tackles this issue by analyzing development artifacts. On the basis of experiences with an undergraduate agile software engineering course, we defined a collection of process metrics. These contain the core ideas of agile methods and report deviations. Using this approach, development teams receive immediate feedback on their executed development practices. They can use this knowledge to improve their workflows, or can adapt the metrics to better reflect their project reality.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted