Heatmaps are a great way to visualize large blocks of data. In this case we are looking at the amount of work a team of individuals worked on completing a project. This is for purpose of an SRED audit.
Objective: The team was attempting to develop an operating system which would be stable on non-durable memory.
WORK PERFORMED
2012 – 2nd half
Programming: Brandon 90%, Chris 90%, Jeremiah 75%
Project Management: Mike 75%
Support: Mahshed 40%
Heatmap Purpose: Over 50,0000 log entries were made – chatter between the programmers, the project manager, and support. Some of the chatter was superfluous. The “bad” data, plus the sheer size of data, would be difficult to get a suitable summary document for purpose of audit.
Heatmaps helped to show which tests we concentrated on the most, as well as provide a person-by-person breakdown showing each person’s work as it relates to the test locations.
Feb 2012 to July 2012 – Jeremiah
Feb 2012 to July 2012 – Brandon
Feb 2012 to July 2012 – Mahshed
Comments for purpose of audit: We are being conservative with our numbers. During these years we wound down our website business and concentrated nearly solely on attempting to overcome a major technical obstacle. Mahshed Hooshmand worked during office hours mostly on the test sites. We are nonetheless reducing her to 40% to acknowledge she also worked in the evenings on graphic design during 2011-2012. Her revenue, along with investment from our close friends and families provided the cash flow for completing the project.
2012 – 1st half
Programming: Brandon 100%, Chris 100%, Jeremiah 75%
Project Management: Mike 75%, Taryn 75%
Support: Mahshed 40%
Aug 2011 to Jan 2012 – Brandon
Aug 2011 to Jan 2012 – Jeremiah
Aug 2011 to Jan 2012 – Mahshed
Comments for purpose of audit: At one point we thought the read/write errors were related to wrong data formats. We brought in a couple of outside experts, Daniel Cutler and Ashley Maclean. They worked specifically on the test locations. We are requesting 75% of their time, recognizing both also worked on our videos and blogs to document the progress. Testimonials from the test sites are available.
2011
Programming: Brandon 100%, Chris 100%, Jeremiah 75%
Project Management: Mike 75%, Taryn 75%
Support: Mahshed 40%
We pulled the data for the 2nd part of the year in order to show the USB keys were we testing and that each person was closely involved in the project. These were the same test locations for the first part of the year as well. Testimonials from the test sites are available.
Feb 2011 to July 2011 – Brandon
Feb 2011 to July 2011 – Jeremiah
Feb 2011 to July 2011 – Jeremy
Feb 2011 to July 2011 – Mahshed
Comments for purpose of audit: Prior to February 2011 we were testing the operating system using CF cards. The USB keys started in earnest in February 2011. The CF card data can also be pulled if required. When looking at the hours worked, the claimed hourly incomes for the team members is extremely low.
Summary: Heatmaps can help organize complex project timelines into a viewable format. Viewing the data in this fashion helped ENS to:
1. Show how each team member was involved.
2. Understand which tests were most emphasized.
The audit indirectly helped our business. It was the catalyst for our discovering heatmaps, which in turn provided better visibility as to which tests garnered our greatest attention. We then obtained testimonials from the most active test sites (and their firsthand experience of the failures) to support the audit. This would have been impossible to otherwise obtain from 50,000 lines in a log file.





















