We've got some great data for the SPA2012 workshop on JavaScript visualisations. Hibri has managed to obtained three years' worth of 7Digital's work-tracking data and Rob has very kindly allowed us to use it (anonymised, of course).
We're going to use this dataset to show different information using different libraries for the visualisations.
What I'd really like your input on is, what would you like to know? If this was your work-tracking data, what questions would you want it to answer?
For example, we could create a Sunburst diagram using JIT to show what proportion of total development time is spent on the four different applications. We could create an interactive line graph using Raphael to show the average time a piece of work takes, and how that average has changed over the past three years.
A little more info about the exact data is below, or feel free to skip straight to the example questions, or just go right ahead and tweet me or email me (at this domain) with what kind of information you'd want from a work log stretching back that far. You might get a great visualisation prepared for you to show just that!
Here is an example:
"Feature ID": "A-321", "Application Name": "Project A", "Type": "Bug", "T-Shirt Size": "S", "Added": "15/03/2011 12:12", "Prioritised, Awaiting Analysis": "15/03/2011 12:12", "Analysis Completed": "15/03/2011 12:12", "Development Started": "15/03/2011 13:21", "Systest Ready": "15/03/2011 16:21", "Systest OK": "17/03/2011 10:34", "In UAT": "17/03/2011 10:34", "Ready For Release": "17/03/2011 10:34", "In Production": "17/03/2011 10:35", "Done": "22/03/2011 10:48", "Lead Time": "2", "Cycle Time": "2", "Development Cycle Time": "2"
So this is a really rich dataset. We have all the dates that various stages of the release process happened, as well as some information about what application it was for, what type of work it was (e.g. Bug, Feature, Build Maintenance), what the rough estimate was (T-shirt size), and how long the whole process took, both from first raised to done (lead time) and from dev start to done (development cycle time). The log goes back to 2009.
Here are a few of the questions we've thought about answering.
We'd love this workshop to be as relevant and interesting as possible, so please do let me know what kind of information you'd like to see visualised and it may well make it into the talk! Tweet me or email me at this domain. Thank you!
If you’d like to be notified when I publish a new post, and possibly receive occasional announcements, sign up to my mailing list: