View Single Post
  #205   Spotlight this post!  
Unread 08-09-2016, 08:42
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
 
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,933
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: [FIRST EMAIL] Stop Build Day Survey

Quote:
Originally Posted by Caleb Sykes View Post
Jim shows in Point 3 of his paper that there is a reasonable correlation between OPR and team retention. Everyone knows that correlation is not causation, but the correlation does allow us to use OPR as a reasonable proxy for team retention. Teams that have low OPRs are also more likely to fold than teams with high OPRs. Likewise, teams that fold tend to have lower OPRs. Team retention data is probably near to as close as we can get to quantifying the "success of FRC teams" using publicly available data.

We can disagree about how specific policies will impact OPR distributions, team retention rates, or the correlation between the two, but at the present time, OPR does indeed seem to be a reasonable proxy for a given FRC team's success.
Nope - For exactly the reason you just gave. Correlation definitely is not causation. Both of the symptoms you mention, and more, could easily be symptoms of something more fundamental that would be essentially unaffected by the SBD. My belief is that this is the case. They are symptoms of a more fundamental problem that is insensitive to SBD machinations. In recent previous discussions I have explained that.

And
Eliminating a true- or pseudo-SBD is certainly not the only way to affect a struggling team's retention (and/or OPR); and IMO isn't the best way. For a reason to agree, see the recent post in this thread that describes some teachers' feelings.

Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Reply With Quote