Corporate memes (Devs edition) mega compilation - Tiktok - Anthony Sistilli 

I'll put a meeting on your calendar for a review

Real thing

We use sprint points. 1 point is roughly 1 hour. We use points because it helps us to not be restricted to time. If I take 1 hour for a 8 hour task, I can chill the rest of the time. If I end up taking longer without realizing it, I don’t get yelled at.

Story points work quite well for their intended purpose: giving an idea of relative complexity. Planning poker also works well - you avoid juniors just hiding behind the seniors estimates, and it gives you an idea if everyone understands what needs to be done. If the estimates are very far from each other the chance you are not on the same page. Don't do it religiously of course, not worth it on every single story. And as implies in the name: do it at "story level", not at task level. And do it in self managed teams where no one tried to manage by the numbers. If you try to use them to measure performance (they can't be used for this, but idiots who have no idea what scrum is keep trying) then they can no longer be used for estimating. The numbers are only for the team. The tasks you create are only for the team. If you are creating tasks the team does not need, then you are not following scrum recommendations.

"Number of days" estimates in my experience are always wrong. Using something like story points means that you have a measure of the size of the task and there is some variability built into the estimate. Over a number of sprints you will get an idea of how many points the team usually completes, which allows the team to work out how much they can deliver and plan over the long term. Using git commits as your only log of progress is a terrible idea in a team. Try communicating progress made with a client when all of your commit comments are "made a change" or "fixed bug". I'm a software engineer, and have worked alongside plenty of other software engineers, and getting people to change their committing habits is very difficult.

It’s not too bad if it’s applied correctly but in my experience that’s rare. Agile with scrum most of the time it’s the opposite to “agile” and too “short-sighted”, without mention all the overhead costs that comes with project managers with fancy and cheesy titles. Unless the company charge clients for developing hours, then works wonderfully haha

That's basically corporate

@@eyeofthepyramid2596 not with our corporation