"You should connect with your Agile team for 20 minutes every day.
Unless you can't find the time.
In that case, you should connect with them for 1 hour."
If Agility is the ability to respond to changes in a meaningful way, a huge part of that consists of the time it takes until this response is in the hands of the customer so that a feedback loop can form.
If that's true, what's the value of Discovery Epics or Stories, Spikes, Dual Track whatever...
The problem with calculating a "velocity" for your team when using #Scrum in combination with Fibonacci-based storypoint sizes, is that completing 3 backlog items of size 8 is not the same as completing 8 backlog items of size 3, or 24 backlog items of size 1. The difference in effort and uncertainty makes such numbers a useless basis for comparison and prediction.
And following the example of XKCD in https://xkcd.com/2295/ : adding garbage numbers together leads to worse garbage numbers.
How do i explain to someone that daily standups are for devs to just keep up to date with whats going on and where they need help
And not a ridged meeting for documenting work done yesturday, todays work and blockers, so the scrum master can report back to upermanagement so they can audit and micromanage the team.
its not that i hate scrum, its i hate people that dont understand it and try to follow the letter of the law vs the spirit.
Hi folks! I have a new post up on Embracing Agility:
No Points for You!
A specific topic regarding Story Points from my AgileAI experiment was whether we should estimate work on defects & tech debt using story points. Read on to find out!