#agile #scrum #tech #softwaredevelopment #meme #funny
-
@ahltorp @crazyeddie @mwshook @PavelASamsonov I've worked with someone who was keen on "velocity" and quite unreasonable about sticking to it. Fortunately I haven't encountered anyone else who used the term, let alone is that unreasonable about sticking to it. I'd probably end up a nervous, twitching wreck if I did!
@geoglyphentropy @ahltorp @mwshook @PavelASamsonov Why?
What's upsetting about it?
1. Come up with some metric you use to measure task difficulty. Establish criteria.
2. Practice estimating tasks by estimating tasks.
3. Graph results.
4. Meet occasionally to discuss ways to improve your task estimates. Try to eliminate variance.This causes seizures?
-
@geoglyphentropy @ahltorp @mwshook @PavelASamsonov Why?
What's upsetting about it?
1. Come up with some metric you use to measure task difficulty. Establish criteria.
2. Practice estimating tasks by estimating tasks.
3. Graph results.
4. Meet occasionally to discuss ways to improve your task estimates. Try to eliminate variance.This causes seizures?
@crazyeddie @geoglyphentropy Graphing made-up values is a/the problem.
-
@geoglyphentropy @ahltorp @mwshook @PavelASamsonov Why?
What's upsetting about it?
1. Come up with some metric you use to measure task difficulty. Establish criteria.
2. Practice estimating tasks by estimating tasks.
3. Graph results.
4. Meet occasionally to discuss ways to improve your task estimates. Try to eliminate variance.This causes seizures?
@crazyeddie @ahltorp @mwshook @PavelASamsonov It was that my initial estimate was treated as set in stone and any failure to ahere to it was blamed on me. Granted, this is probably a boss being a bully rather than an issue with velocity.
Also, I probably phrased things badly wrt the outcome, I was thinking more of being hypervigilant and very nervous rather than seizures.
-
@crazyeddie @ahltorp @mwshook @PavelASamsonov It was that my initial estimate was treated as set in stone and any failure to ahere to it was blamed on me. Granted, this is probably a boss being a bully rather than an issue with velocity.
Also, I probably phrased things badly wrt the outcome, I was thinking more of being hypervigilant and very nervous rather than seizures.
@geoglyphentropy @ahltorp @mwshook @PavelASamsonov Yeah. I keep running into this. It's pretty common. People really hate on various bits of agile methodology but when you ask them why it's a complaint about some horrible nonsense someone did one time.
Agile methodology is quite clear here. You're supposed to try getting better at estimates, not bitch slap people for not meeting bad ones or making bad ones to begin with. Agile doesn't fix bad management that points fingers.
-
@woe2you It’s not only ”we suck at gathering requirements”, it’s also ”it’s often not meaningful to gather requirements in a vacuum”. Those are actually among the good parts, having stakeholder representation in the team. ”Fancy name” is among the bad parts.
@woe2you @ahltorp I first came upon scrum under “extreme programming” -we used it when things went wrong in emergency-replacing the weekly team leader meeting with daily stand-ups -mainly to demonstrate to managers we were working even when we weren’t typing - what they thought we should be doing -not the talking.about requirements which was the real necessity. Management never truly trusted thinkers -hence the lines of code then the burn down- then the tickets-trust zero
