IDEA: automated standup script. It would gather the git diffs from each team member & any changes to Jira since yesterday.
By the way, was #ChatGPT trained by listening to your standup briefs? Check here to see if you can find your words
https://chat.openai.com/share/c5005e9a-848f-49d5-9b42-8d58e34559a8
#Agile #Scrum un-#SAFe
Sprint velocity shouldn't be confused with a time card or itemized bill for tasks
Let's imagine it was. First off, it will be the worst, most inaccurate ever because you're making guesses about the unknowable future, not commitments. Real time cards are recorded *as it happens* for this reason.
Point estimates are self declared by individual contributors. If there are $ penalties to not reaching velocity, you merely keep your job if you hit velocity, lose your job if not
When team velocity is treated as a 12 week pre-committed time card, itemized bill, then when a team member is out sick or quits or is fired, and the whole team is expected to meet the same velocity (because it was a pre-declared time card/contract to deliver) then the rest of the team picks up 40 hours of work per week until a replacement is hired. If that person was a specialist, then the other specialist gets to work 80 hours a week.
Except the math doesn't work. I think this came about from someone thinking, "If you are a good moral person, you will live up to your agreements and you agree to 100 velocity points, so you will do what it takes to deliver 100 points." And for maybe 10% variations, sure, people will work late out of a sense of professionalism. But if you ask a honest person to jump 10 feet when the maximum one person can jump is 5, then they can't. Doesn't matter how honest or professional they are.
So what is going to happen. Goodhart's law on perverse incentives is going to kick in. Those velocity points are self declared monopoly money. They're not objective. They are good planning tools as long as you don't give people an incentive to lie. To minimize the risk of the maximum loss, it is now rational for *developers* to plan for 50% slack or more. To squeeze out the last 10% of efficiency, you've cut output by 50% or more.
this #scrum stuff- it is a process improvement project. but with non-technical scrum masters, then we start to get a ticket management improvement process. Automated pipelines and practices (unit testing) start to disappear from the dialog.
I'm trying to imagine toyota's process improvement process if the car making part was to complicated to talk about and it became a way to progressively improve how the time cards got punched, since it is a lot easier for everyone to discuss that.
#scrum When you get your 2nd charge code (are on two projects) your productivity drops by half. So you'd be like adding 1/4 of a person to a team, not 1/2.
https://www.forbes.com/sites/tracybrower/2019/10/06/is-agile-really-worth-it-evidence-says-yes-if-you-do-these-4-things/#5f10f75b5488
#scrum now I want to model this in my tiny scrum simulator & see what params lead to an endless stream of tickets & batching is meaningless
#scrum if a team is regularly late, it will promise less & less until it delivers early & see last tweet, more items & creeping #kanban
#scrum so if a team regularly finishes a scrum early & is just given more items to work, isn't that just sliding into a #kanban system?
In Game of Aeron Chairs, remember the scene where Stakeholder John Snow executes the Product Owner for cowardice? That was the best. #scrum