Thanks for explaining. I still think “planning” is a weird way to think about what’s supposed to happen during standup-- It seems to me that the whole purpose of working in sprints (and the rituals that that typically entails) is to plan ahead so that during the week you can execute on well-groomed, properly-scoped work. Of course when you notice something is wrong, or needs to be reconsidered, you might need to pull the brakes and realign mid-sprint, but my sense is that if you’re doing planning every day, that might mean that your work isn’t groomed well enough beforehand, or you’re not locking in important decisions during sprint planning.
But it might depend on the work, and it might depend on what you mean by “planning.” If your planning just looks like “Hey are you free to pair on issue 123 this afternoon? Okay sweet, I’ll throw a meeting in your calendar,” then yeah sure-- I wouldn’t use the word “planning” for that, but it’s not crazy to. Or maybe the work is different than my work, and actually does warrant some amount of day-level of planning that wouldn’t make sense for teams I’ve been on. I’m open to that, too.
(Btw I tried to look up this “planning planning feedback feedback cycle” thing and the only search results I got were THIS LEMMY THREAD, lol… Cool to see Lemmy show up in search results)
Okay but how does starting a secure shell help?