User Tools

Site Tools


Sidebar

projects

hfi0 (due 20200123)
wcp1 (due 20200123)
wpf1 (bonus; due 20200123)
wcp2 (due 20200129)
wpf2 (due 20200129)
wcp3 (due 20200205)
wpf3 (due 20200205)
wcp4 (due 20200212)
wpf4 (due 20200212)
wcp5 (due 20200226)
wpf5 (due 20200226)
bwp0 (due 20200226)
fom0 (ongoing)
eoce (due 20200513)
haas:spring2020:hpc0:projects:sll1:metrics

sll1 Project Class Status Summary

Provided as a means of better understanding trends, the following charts and tables will visualize various indirect data points that, while not indicative of success (or deferrance thereof), may well correlate with such. Plus, being able to see trends on a large scale can aid in better decision making and planning.

sll1 lifespan

Projects are typically released on Tuesday, and are due by the end of the following Wednesday. This allows for at least nine days to work on the project without penalty.

Following the due date, there is a period of three days (the late, or past due period), where 25% is docked each day, after which the project neither has nor can earn any value.

Here is a table with the pertinent dates for this project (the day number is the one that is also found on the x-axis of the graphs.

20150929 20150930 20151001 20151002 20151003 20151004 20151005 20151006 20151007 20151008 20151009 20151010
0 1 2 3 4 5 6 7 8 9 10 11
start date due date late day 1 (25% off) late day 2 (50% off) late day 3 (75% off)

Typically, any and all activity taking place to the left of the due date is preferable; it tends to indicate less procrastination and has the likelihood of involving better time management.

Progress By Day (Individual)

<charter> title = sll1 Individual Progress size = 600×400 align = center type = bar XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,17,0,0,0,13,65,34,0,0,0 0,6,23,11,31,55,34,50,25,0,1,0 0,0,0,1,0,0,0,0,0,0,0,0 0,0,9,0,19,0,4,1,7,1,0,0 0,0,22,21,0,0,23,89,3,0,0,0 0,7,22,11,0,0,15,1,52,0,1,0 0,0,19,18,0,0,14,14,30,1,0,0 0,0,0,0,0,11,1,1,0,0,0,0 0,1,38,0,61,34,60,32,2,2,0,0 0,0,0,0,2,0,0,17,10,0,0,0 0,0,0,0,9,0,0,33,57,0,0,0 0,0,40,0,66,0,25,37,13,0,0,0 0,0,0,0,0,0,5,1,24,35,0,0 0,0,36,0,0,0,8,32,42,15,0,0 0,31,0,0,0,0,0,0,1,0,0,0 0,0,0,0,0,0,0,0,1,0,0,0 0,0,37,0,0,2,68,17,33,4,0,0 0,0,0,0,60,0,0,15,35,1,0,0 0,0,0,0,0,0,0,0,0,0,0,0 </charter>

Each line represents an individual class member's progress on the project. The more active they are, the higher the bar will rise.

The busier the day looks, the more active a development day it is by more of the class. And the more left shifted the activity, the less procrastination (lefter is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

NOTE: As of sll2, activity is measured in units of partial project builds. Prior to sll2, only full project builds were counted.

Progress By Day and Quantity (Together)

<charter> title = sll1 Class and Quantity Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,17,0,0,0,13,65,34,0,0,0 0,6,23,11,31,55,34,50,25,0,1,0 0,0,0,1,0,0,0,0,0,0,0,0 0,0,9,0,19,0,4,1,7,1,0,0 0,0,22,21,0,0,23,89,3,0,0,0 0,7,22,11,0,0,15,1,52,0,1,0 0,0,19,18,0,0,14,14,30,1,0,0 0,0,0,0,0,11,1,1,0,0,0,0 0,1,38,0,61,34,60,32,2,2,0,0 0,0,0,0,2,0,0,17,10,0,0,0 0,0,0,0,9,0,0,33,57,0,0,0 0,0,40,0,66,0,25,37,13,0,0,0 0,0,0,0,0,0,5,1,24,35,0,0 0,0,36,0,0,0,8,32,42,15,0,0 0,31,0,0,0,0,0,0,1,0,0,0 0,0,0,0,0,0,0,0,1,0,0,0 0,0,37,0,0,2,68,17,33,4,0,0 0,0,0,0,60,0,0,15,35,1,0,0 0,0,0,0,0,0,0,0,0,0,0,0 </charter>

Each line represents the total class activity on the project for the given day. The higher and more colorful the line, the more activity by more people took place (upperer as well as lefterer is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

NOTE: Activity is measured in units of partial project builds. Prior to sll2, activity was measured in terms of full project builds.

Class Member Activity Per Day

<charter> title = sll1 Class Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,10,0,0,0,10,10,10,0,0,0 0,10,10,10,10,10,10,10,10,0,10,0 0,0,0,10,0,0,0,0,0,0,0,0 0,0,10,0,10,0,10,10,10,10,0,0 0,0,10,10,0,0,10,10,10,0,0,0 0,10,10,10,0,0,10,10,10,0,10,0 0,0,10,10,0,0,10,10,10,10,0,0 0,0,0,0,0,10,10,10,0,0,0,0 0,10,10,0,10,10,10,10,10,10,0,0 0,0,0,0,10,0,0,10,10,0,0,0 0,0,0,0,10,0,0,10,10,0,0,0 0,0,10,0,10,0,10,10,10,0,0,0 0,0,0,0,0,0,10,10,10,10,0,0 0,0,10,0,0,0,10,10,10,10,0,0 0,10,0,0,0,0,0,0,10,0,0,0 0,0,0,0,0,0,0,0,10,0,0,0 0,0,10,0,0,10,10,10,10,10,0,0 0,0,0,0,10,0,0,10,10,10,0,0 0,0,0,0,0,0,0,0,0,0,0,0 </charter>

Each day shows the quantity of project builds per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of a user building, and counted once per user per day.

Project Lifecycle Stats (Individual)

<charter> title = sll1 Individual Project Duration size = 600×400 align = center type = bar XAxisName = Person YAxisName = Minutes shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

9448 10747 8558 9434 9488 0 10727 9467 10059 8834 6899 11210 8951 3491 9587 11625 3533 9798 9484 12366 </charter>

Each bar represents the number of minutes taken from initial upgrade to project through project submission (final submission).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Obtains/Upgrades/Updates/Submits By Day

<charter> title = sll1 Lifecycle Progress size = 600×400 align = center type = barStacked legendEntries = obtain, upgrade, update, submit XAxisName = Day YAxisName = Activity shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

10,0,0,0,0,0,0,0,0,0,0,0 20,60,90,10,10,0,10,0,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,10,0,0,0,0,0,10,140,80,0,0 </charter>

Each day shows the quantity of project obtains, upgrades, revision updates, and submissions per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of specific actions taken (upgrading, submitting, etc.), and counted once per user per day.

Status Page last updated: Tue Oct 13 16:42:57 EDT 2015

haas/spring2020/hpc0/projects/sll1/metrics.txt · Last modified: 2015/10/13 20:42 by 127.0.0.1