Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update sizing to use fibonacci sequence. #285

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

aminomancer
Copy link
Member

Fixes #284

@aminomancer
Copy link
Member Author

  • Ron said we could add back XL but give it 20+ for potential future use. Didn't check if Bugzilla has points that go that high, I'll probably just give it the max number Bugzilla supports
  • We have "Remaining work per person" on iteration views, but it's empty for finished iterations, so it's hard to retrospectively get information on capacity for a given iteration. Would be good to add "Total work per person" showing finished bugs (including the total for the whole team) in addition to the one showing unfinished bugs
  • On the Engineering Allocation view, we could consider adding a section at the bottom showing the same stuff. But instead of remaining/total work per person, per iteration, it would probably be per release, as the Engineering Allocation view is per release.

Copy link
Contributor

@AllegroFox AllegroFox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is straightforward! Thanks :)

@aminomancer
Copy link
Member Author

Thanks for reviewing!

@AllegroFox
Copy link
Contributor

AllegroFox commented Dec 8, 2023

To your point about the XL: looks like the max number of points in Bugzilla is 15; which we could just use for XL regardless despite it not being in sequence (that would leave us 8 & 13 for L). Seems reasonable as a workaround for 20+ not being in bugzilla, since we would end up with 2 point amounts for each "level" (1 & 2 for SM, 3 & 5 for MD, 8 & 13 for L) and then just max value for XL.

I like the idea of "total work per person/per iteration" esp. since the pointing is meant to be a little retroactive, relative to previous amounts of work. We can give this change a little time to percolate and see what people think, and see if that would make the process a little clearer for folks

@aminomancer
Copy link
Member Author

Yeah that makes sense. Sounds good!

@aminomancer aminomancer merged commit c1b0ec0 into master Dec 8, 2023
@aminomancer aminomancer deleted the aminomancer/issue284 branch December 8, 2023 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update sizing to use Fibonacci sequence
2 participants