In my last post about Demeter I was discussing shot priorities. Since then, Demeter has improved a lot (some are saying that soon, she will be having conversations with us). As we’ve been using and improving Demeter, I noticed that the shot priority wasn’t being set all of the time and therefore was doing nothing for us. When we’re busy with many shots across more than one project, we don’t have the time to meddle with the priority of each shot.
So the other day as I’m researching graph theory, I have a “eureka!” moment. Because shots have relationships to each other, i.e. shot one could be a part of shot two which is a part of the final piece, I could visualize the project of shots as a graph. But it doesn’t stop there, I can use this “shot network” to calculate many different things about these shots.
Using an algorithm similar to the ones used by Google, Facebook, and other websites that have mass amounts of information in a graph-like network, I can determine what the priority of a shot is. I’m basing this off of a lot of different factors, one of the more important factors being how many shots a certain shot can influence.
This means that at any given time, Demeter can tell us what the most important shot to be working on is. Because we can assign shots to different people, each person can know what they should be working on. This is even more powerful whenever you look at all of the projects at once and can easily tell which shot is the most important and why. This takes into account the projects due date as well.
Here’s an example of a few projects we’re working on visualized by Demeter. Each circle is a different shot. The big blue circles represent projects, and the lines between the circles are relationships. Shots that are green have been completed, and shots that are only small dots are shots that do not belong to me. The shots that belong to me are big and red in relation to their priority, so bigger, redder ones are higher priority.