Closed jeffreywescott closed 7 years ago
update language and then move to RFI
Builds towards goal: !Learner stats match our subjective reality, elicit honest feedback, and promote self-directed, collaborative growth
related #68
updated description
ready for review @shereefb + @LearnersGuild/software
Love it. One suggestion is to show the math behind how XP was calculated. Which contributes to: - !Players know how to increase low stats
**Stats earned for this project:**
Experience Points (XP): 11.12 ( (40+45+10) * 0.14 * 0.89 * 0.94)
Culture Contribution: ${stats.cc || 0}%
Team Play: ${stats.tp || 0}%
incorporated @shereefb's suggestion
For each project, use the following data from retro (note: depends on #68):
- Actual Contribution
- % of project completed by learner (mean of all teammate's evaluations, incl. self)
- Internal project review scores (i.e. those submitted by the team members)
- Project Completeness
- Project Quality
- Hours contributed to project per team member
I thought we had moved away from project reviews being used as part of XP? Is the description out of date?
Moving back to Review.
@jeffreywescott it depends on having https://github.com/LearnersGuild/game-prototype/issues/68 complete, which is why it specifies internal reviews (i.e. those submitted with the team retros).
Got it. Thanks for the clarification, @tannerwelsh.
Cannot move this over to implementation because it depends on #68.
@jeffreywescott I'm not sure I understand why the inter-issue dependency is blocking movement of this card. Does every issue that gets moved to RFI need to have zero dependencies on other issues?
@tannerwelsh how can something be "ready for implementation" if another issue is not yet "ready for implementation" and it is a dependency? I look at "ready for implementation" as a signal that it can move to the implementation board and be prioritized, but if it is dependent on issues that aren't also ready ... that's not the case, right?
How do you look at RFI?
@jeffreywescott yes I see it as the same, but in this case its dependency is in RFI also, so they could both be moved over at the same time. Might just be a case of review-lag. When you wrote that it couldn't be moved to implementation, the dependency was still in review. But now it's not. :)
Ah -- okay. Thanks ... planning to review the RFI column sometime today.
Issue moved to LearnersGuild/game #500 via ZenHub
(depends on #68)
Strategic Goals this issues impacts
Benefits
Description
Experience Points (XP) are how we measure productivity and duration of practice. They are roughly equivalent to "effective hours worked", but with more nuance.
XP are measured in hours, up to two decimal places. They can grow indefinitely, but will never recede. In this sense, they are different from a "health" stat that fluctuates.
Eventually, we'll likely introduce gating or leveling mechanisms around XP, to create semantic distinctions between a player with 50 XP and one with 5000 XP.
Data Sources
For each project, use the following data from retro (note: depends on #68):
Calculation
To calculate XP earned for a single project, use the formula:
Where:
total hours contributed
= the sum of all hours by each team member for that cyclerelative contribution
= percent of project contributed to (0..1)mean internal project completeness
= percent of specs implemented for a project (0..1), mean of internal review scoresmean internal project quality
= percent rating of project quality rubric (0..1), mean of internal review scoresFor example, given the values:
Then XP player 1 for working on this project for this cycle is 11.12
XP = ( (40+45+10) * 0.14 * 0.89 * 0.94) = 11.12
.Addenda:
UI Design
Update the post-project DM to each team member to include XP:
Original issue: https://github.com/LearnersGuild/game/issues/150