Just a Normal Sprint Planning -

Belle! Stop saying "I do declare" for your constants! It's not valid syntax!

I'll create a GUI interface using Visual Basic, see if I can track an IP address.
- 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.
- Those 2 things are not fucking related lol
  
  yeah they are. it outputs the IP address on a rad spinning dial with Sonic the hedgehog next to it
- There was a lot wrong with VB but I miss being able to WYSIWYG together basic UIs and get back to Real Coding(tm)
  
  VB was great for learning coding.
  Slap some buttons down and have them do math. I made an NPC generator for every RPG I ran in VB as a teen. I felt like I was a hero putting out something that looked "good" for the time.
- woa.

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.
  
  I remember reading a study done across some large organizations that showed this approach was more accurate than other estimation techniques. Makes sense to me.
  
  Huh. That's such a simple and obvious approach, I'm kinda mad I've never thought of it lmao. It seems like you're essentially breaking everything down to a 1 (or as close as you can get it), which is probably a more accurate measurement anyways. Neat.
  
  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.
- I'd rather story points than my company's WAG time estimates 🥲
  
  Man, this whole thread is like a foreign language to me.

Who's gonna reverse-sort that kanban into a linked list b-tree?

Let's also have you do a master rank codewars kata... on the whiteboard. You have 30 minutes.

We have been getting pressure from customers whether or not this substring is a palindrome
- SPEZ!!??!?!?!?!?!! WHAT ARE YOU DOING ON LEMMY!?!??! GO BACK TO REDDIT!!!!1!1!11!1!1!1!