Sprint #5.2: Pavel's 80/20 #1918
Comments
|
Err, what is this ticket waiting on? I believe the specifics of this ticket was posted on #development but I'm not sure what this ticket addressed. |
|
Are you expecting that the devs tell you what they're doing in their 80/20 time? They might not always have something to report. |
|
@zavreb I described my work within Friday's standup. Also I talked with Beng to make Friday as a day I'm working on 80/20. Btw, I don't know what is required actions for this ticket (close/re-open every Friday or create new one, etc.) |
|
@aksonov the 80/20s are 5 story points (~1 day or sometimes more) per dev, a total of 10 story points out of 50 points in a sprint. If you separate your ticket for "half" on one Friday and "half" on another Friday, feel free to keep it opened on Once you're done with your 80/20 please feel free to close. One is created for every 2 week sprint. It'd be helpful if you and @southerneer can Adding it:
|
|
Sorry, I don’t understand this “math” and how it became 1 day per 2 week sprint. As I know 80/20 means 80% of time is regular tickets, 20% own ideas, research, etc. 20% of my time is exactly one working day per week, isn’t?
… On 14 Mar 2018, at 22:18, Rebecka Z ***@***.***> wrote:
@aksonov <https://github.com/aksonov> the 80/20s are 5 story points (~1 day or sometimes more) per dev, a total of 10 story points out of 50 points in a sprint. If you separate your ticket for "half" on one Friday and "half" on another Friday, feel free to keep it opened on In Progress.
It'd be helpful if you and @southerneer <https://github.com/southerneer> can comment your descriptions in these 80/20 tickets to avoid duplicate scheduling. (Can talk about this more on Thursday)
Once you're done with your 80/20 please feel free to close. One is created for every 2 week sprint.
Adding it:
Worked on my 80/20 ticket. Discussed with react-navigation authors (Eric Vincenti and Brent Vatne) upcoming 2.0 release, start playing with it - https://github.com/aksonov/react-navigation-experiments <https://github.com/aksonov/react-navigation-experiments>, found few issues: react-navigation/rfcs#29 <react-navigation/rfcs#29> (hopefully they will fix it) - we need that to upgrade RNRF (it still depends from react-navigation betas..) that used by our app.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1918 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQpcdF403Tk5KOEOXfB1NM3AB_QpHaQks5teYk5gaJpZM4SVOix>.
|
|
@aksonov, the 80/20 is based off of the two week sprint as a whole. A sprint is capped at 50 story points including the 80/20 rule. 20% of an entire sprint is 10 total story points. 10 total story points split between you and @southerneer is 5 story points per person each 2 week sprint. If we do it the way you propose then that means it'll be 20 story points out of the Sprint. 10 story points for @aksonov and 10 story points for @southerneer. 20 story points out of a 50 point sprint is 30% of the sprint dedicated to the 80/20 rule. (cc: @thescurry) We can speak further as a group on how we want to define the 80/20 rule. |
|
@bengtan the reporting is meant so that we can make sure we don't duplicate the scheduling on the roadmap. |
|
Haha ok, so the real discrepancy is what a story point means. Up to this point I think we've all gone with the assumption that 5 story points = 1 developer day. @zavreb by your math 2.5 story points = 1 day. |
|
I second @southerneer's comment. How many story points do you think 1 developer-day is? 2.5 points or 5 points? I've been going by the latter. |
|
@zavreb 80/20 rules applies to a person, not to a team. Otherwise if we would have 10 engineers, then 80/20 (in your interpretation) means 1/10 (48 min?) of full working day... |
|
@zavreb It is interesting how you are calculating (and why you introduced story points for 80/20). Sprint has 10 working days (for each engineer), right? So 20% is exactly TWO working days, not one. |
|
@aksonov (cc: @southerneer) you are right in what you are saying. It makes sense. Time and story points aren't meant to mix, story points only focus on effort level and shouldn't be quantified along with time. If it's alright with @thescurry we'll define the 80/20 as two working days per sprint. |
|
...and 5 story points = 1 dev day and therefore we should allot a total of 100 story points for 2 devs in a 2 week sprint, correct? |
|
Our average velocity on two week sprints was 50-55 story points. But I have not been able to track our velocity lately due to shifts in Sprints. We haven't had a "perfect" Sprint in awhile and that average was taken in 2017. It is possible that our velocity has increased now that we improved the way we work (w/bugsnag + refactoring efforts + detox + having @southerneer fully ramped up). For our next Sprint Estimation we can shoot for up to 100 story points and then reflect on the weight of the sprint and see if it makes sense. Nonetheless, a 5 is not 1 dev day. A 5 refers to our effort level, it could be 1 day, 1.5 days or even 2 days. Ultimately, story point efforts should not be equated to time, but effort level/difficulty. This topic has always been an issue for all agile teams. See link. Furthermore, if we'd like to, we can try estimating in hours instead so that it makes sense with our 80/20 rule (which is measured in time). I have worked with teams that have tried this method, but though our story point estimations aren't perfect period, estimating with time is less perfect. But maybe that's what works for us. Thoughts? tldr/
cc: @thescurry, @bengtan |
|
Not suggesting changing the way we estimate time, just trying to reconcile
with
|
I don't think we need to change how we're doing the estimations. They're working fine (AFAICT) and they're a non-problem.
IMHO, the step which tripped things up was trying to equate 20% time with 5 story points. |
|
Hey guys, I think I can fix the confusion here. The 80/20 rule should be very simple, it's based on time. So regardless if a sprint is one week or two weeks long, the easiest and fairest way forward here is to give 1 day a week to dedicate to the "20%". If we can all agree with that, I think we can move forward on this particular subject. Do we all agree? :) |
|
Sounds good! |
|
I'm going to close this since Sprint 5.2 ended. I won't create future tickets for the 80/20, we'll just assume Fridays are the 20%. cc: @thescurry |
No description provided.
The text was updated successfully, but these errors were encountered: