Quote:
Originally Posted by Ed Law
I agree 100%. During the build season, the scouting team meet and propose what scouting information to collect. It is then reviewed by the whole team. After it is finalized, programmers update the Android scouting app and the Tableau person prepare the graphs and work with the game strategy team to finalize the graphs.
The other nice thing about Tableau is once you have the data collected, you can look at it other ways on the fly relatively quickly if the graphs you prepared ahead of time is not as useful as you expected.
It works for us because it is a team effort. I hope more teams will try the software. It is great.
|
Our team met during build season, too. Our software team was able to make a sample dummy data set of 24 teams with different Stronghold abilities. I had my scouts use Tableau data to strategize for different red and blue alliances like we do in a real competition. They were able to get used to how the data looked in Tableau and we were able to make changes to the categories of information we looked at. We also did sample alliance selections based on the data. Given that we were all pretty familiar with how this year's competition data looked before we even had a real competition, we were able to hit the ground running. We have had to make very few changes to our data collection after two competitions. Again, I will say that qualitative data is a necessary balance to the quantitative data.