Bluejay: A Cross-Tooling Audit Framework For Agile Software Teams
Cesar Garcia, Alejandro Guerrero, Joshua Zeitsoff, Srujay Korlakunta,, Pablo Fernandez, Armando Fox, Antonio Ruiz-Cortes

TL;DR
Bluejay is an open-source framework that integrates data from multiple development tools to audit and visualize agile team practices, making it easier to ensure compliance and improvement over time.
Contribution
It introduces a novel, extensible platform that models and audits team practices across multiple tools using SLA-like terminology, filling a gap in existing single-tool audit systems.
Findings
Supports data collection from five popular tools
Provides customizable dashboards for team practice auditing
Facilitates cross-tool compliance monitoring
Abstract
Agile software teams are expected to follow a number of specific Team Practices (TPs) during each iteration, such as estimating the effort ("points") required to complete user stories and coordinating the management of the codebase with the delivery of features. For software engineering instructors trying to teach such TPs to student teams, manually auditing teams if teams are following the TPs and improving over time is tedious, time-consuming and error-prone. It is even more difficult when those TPs involve two or more tools. For example, starting work on a feature in a project-management tool such as Pivotal Tracker should usually be followed relatively quickly by the creation of a feature branch on GitHub. Merging a feature branch on GitHub should usually be followed relatively quickly by deploying the new feature to a staging server for customer feedback. Few systems are designed…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
