SCORE 2018 SNA4Slack

SCORE Guidelines subtly mention the following to include the following in summary report:

Graphs or analyses of repository activity i.e. GitHub contributions, PR and issues page
Growth of user story base i.e. user stories, iterations, release plan and completion of at least two release iterations
Project velocity graphs over iterations i.e. use github project boards for each iteration and release; have a working release for each commit
Other such data analysis i.e. wiki page documents detailing architecture and design, code quality and coverage metrics, acceptance tests

Basic Requirements Checklist

Visualize and analyze social networks built upon Slack conversations
Visualizations should provide a way to show the network graph, without node overlapping, using one or more layout algorithms.
Set filters for pruning the graph by keeping only nodes and edges that satisfies filters conditions
Most common metrics for social network analysis (SNA), including metrics to assess the overall structure of the network (e.g., measures for density, path length, and overall connectedness), centrality metrics (e.g., degree for undirected graphs and indegree/outdegree for directed graphs) and metrics the assess the level of clustering within a network (e.g., clustering coefficient).
Automated test is required. Unit tests must be created as each new code unit is added. Systems tests should be created as each new feature, or user story, is created. All tests should be run after any change, and 100% success rate is expected.
Graphs should interactively explored through visualization and analyzed to identify central teammates and clusters.
The system must come with at least one social network (may be the mention graph), one layout algorithm and three SNA metrics
Slack messages will be accessed through the Slack export archive or, better, the Slack API.

16 to 22 Dec, 2017: Infrastructure creation, enumeration of user stories, architecture and design finalisation, REST API design, selection of technology stack
22 to 28 Dec, 2017: Release Plan spanning 4 months, Design artifacts completion, Creation of working, but hallow client-server REST framework, client and server-side functional tests in place (UML diagrams - CRC cards, component diagrams, deployment diagrams, package diagrams, class / object diagrams, collaboration diagrams, and activity diagrams)
29 to 7 Jan, 2018: Verification of design artifacts, Hallow modules and interfaces with unit and integration tests in place
7 to 15 Jan, 2018: Finalisation of design documentation, Video of the mock application, project report submission
Beyond 15 Jan, 2018: XP Iterations with code coming from IRC and Mailing List projects