Internal resources related to TEAMSCOPE project
- Some interesting related work
- Slides from Armando’s summary of one of the related papers (“Using surveys, tutors, and software to assess scrum adoption…”)
Ongoing Internal Work
Over the summer, 3 high school interns supervised by Armando (Vasuman Moza, Rushil Kapadia, Jerry Qing) examined four Agile/XP processes related to the use of Pivotal Tracker for tracking the lifecycle of user stories in agile projects. They proposed specific conformance definitions for these processes that can be computed from data available via Tracker’s remote API.
AgileVentures.org is helping us develop a “dashboard” to deploy in CS169 to track conformance of various aspects of projects in CS169 and elsewhere. Each conformance template gets incorporated into its own Ruby gem (“plugin”) to be added to the dashboard. From an early prototype of this idea in CS169 Spring16, we already have simple conformance metrics for GitHub pull request behavior and CodeClimate
- ProjectScope GitHub repo
- Staging server (don’t populate with data we care about, it’s wiped regularly)
We have the potential opportunity to observe how project teams communicate. Most teams in CS169 already use Slack for communication (and we can require it), and we can submit an IRB to have the text from those Slacks analyzed after the fact.