Unfortunately, I have a much easier time admitting when I'm wrong about something involving work. Let me share with you a story about a time I was wrong something about involving Scrum. Back in its early days, Scum didn't have sprint retrospectives. That's probably not very surprising. No one thought about it at first. But you're probably thinking that as soon as someone did think about, we all quickly added sprint-retrospectives to our sprints. No, not really. Many people did, of course, quickly add retrospectives. But some of us, me included, did not. That sounds crazy now, and it's something I was wrong about. See, I can admit that. Let me tell you why I My objection was basically, why should a team member wait until the end of the sprint before sharing with the rest of team a suggestion for how they can improve? If I come up with an idea that will help us build better software, I should share it with my teammates immediately, not at the of sprint. But here's what happened. Suppose I do come up with some great idea in the middle of some day in a sprint. I am not going to stop programming right then to tell everyone about it. Besides, you're all in your own things. So I tell myself, I'll tell you about at tomorrow's standup. But at tomorrows stand up I can't remember what it was I wanted to you. What teams learned, what I learned. was that it was better to set aside a designated time to talk about ways to improve. Of course, it's theoretically better, to jump up and tell a team about a great new improvement right when you think of it. But you probably won't do that. So set a side a designated time every sprint. There's nothing that prevents you from jumping up, and sharing some amazing improvement immediately, if you do happen upon one. I was wrong. I'd thought that just talking about improvements whenever someone thought of one would be better. It wasn't.