Agreed. Agile needs to be for developers first and foremost, not the management.
At least, in Scrum, from my experience so far: pointing is about measuring the uncertainty to delivery, but should healthily include learning, tech debt refactors,testing, q/a, even unexpected stuff like dev churn (i.e shoot under always, over estimate slightly).
But if individual performance is measured by velocity and points, you will just get devs badly cutting corners and gaming it while project & product will never get accurate measurements they can tie time based business outcomes to (especially as you get further out and short term corner cutting starts to rear it's head as brutal Tech Debt and time sinks)
>> trying to solve with innovation would just go away for at least 20 years.
Interesting! But wait... wouldn't that mean everyone would save effort and potentially money by hooking up to the national grid? One that has way more people working on innovation + a 20 year time line for it?
Honestly that sounds way more simple, straightforward, and literally more innovative than "let's just all turn our temps down when peaking" lol.
I'd trust FB with my data over say.. Equifax, and they have way more important data than my pulse. But they also got hacked for bad software maintenance and no one is constantly shitting on them.
Not that I use it, but idk FB is a scapegoat if anything.
...Also I know it's whataboutism but common lol. People are so entitled with their privacy when it means nothing to their actual safety. Comes off so weak and whiny.
Lmao yeah like all the terrorists that stormed the capitol.
Given this logic, we should charge all ppl with guns and other stock piles who wave confederate flags as potential terrorists who want to overthrow the government too?
At least her cause seemed legit (racism). Also she is reformed now? Still a terrorist though I guess, just like all those neo-nazis who are "reformed".
Edit: I realize I'm being biased here, but trying to point out your own (strawman) bias lol.
All protests can attract bad actors that take advantage of the emotion and pain. This is honestly a non-sequitur argument unless you apply it to the "other side" as well.
At least, in Scrum, from my experience so far: pointing is about measuring the uncertainty to delivery, but should healthily include learning, tech debt refactors,testing, q/a, even unexpected stuff like dev churn (i.e shoot under always, over estimate slightly).
But if individual performance is measured by velocity and points, you will just get devs badly cutting corners and gaming it while project & product will never get accurate measurements they can tie time based business outcomes to (especially as you get further out and short term corner cutting starts to rear it's head as brutal Tech Debt and time sinks)