Damn! Team Just do it!!!
Belle! Stop saying “I do declare” for your constants! It’s not valid syntax!
Here is an alternative Piped link(s): https://piped.video/watch?v=hkDD03yeLnU&
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
There was a lot wrong with VB but I miss being able to WYSIWYG together basic UIs and get back to Real Coding™
Thanks i hate it
joke aside, story point can be quite arbitrary
My team has being trying an approach where instead of story pointing, we break everything down into the smallest incremental tasks we reasonably can and use number of tasks overall as the metric instead of story points.
In theory it’s meant to be just as accurate on larger projects because the larger than normal and smaller than normal tasks all average out, and it save the whole headache of sitting around and arbitrarily setting points on everything based mostly on gut feeling.
When I teach story points (not in an official Agile Scrum capacity, just as part of a larger course) I emphasize that the points are for conversation and consensus more than actual estimates.
Saying this story is bigger than that one, and why, and seeing people in something like planning poker give drastically differing estimates is a great way to signal that people don’t really get the story or some major area wasn’t considered. It’s a great discussion tool. Then it also gives a really rough ballpark to help the PO reprioritize the next two sprints before planning, but I don’t think they should ever be taken too seriously (or else you probably wasted a ton of time trying to be accurate on something you’re not going to be accurate on).
Students usually start by using task-hours as their metric, and naturally get pretty granular with tasks. This is for smaller projects - in larger ones, amortizing to just number of tasks is effectively the same as long as it’s not chewing away way more time in planning.
Haha they’re just different ways of estimating the difficulty of a work task. Story points are a kind of estimate that are represented by a number. The larger the number the more difficult the task.
My company uses WAG (wild ass guess) time estimates where we have to actually say how long we think a task is going to take in a matter of days or weeks. It sounds fine but programming tasks are notoriously hard to estimate since you have to consider so many different factors. I’m especially bad at it so I’d much prefer just saying “this task is an 8 because it seems hard”
Who’s gonna reverse-sort that kanban into a linked list b-tree?
