Talking to a team about carryover at a daily scrum meeting led me into a very uncomfortable confrontation with someone who already didn’t like me. Not sure why but I ascertained it had something to do with the unhealthy relationship between product and technology organizations and the fact that product was pushed by sales to make commitments on behalf of the teams that were essentially never met on time (more on that issue in a later post). So a contentious confrontation – read on…
We have a problem. Ok, I have a problem. I’m realizing velocity is often being used as a synonym for team capacity. In fact, I’ve done it, too. Don’t think that’s a problem? Well it impacts our forecasting, estimation, team health, and organizational expectations.
Busy. I’m busy. I’m too busy. I don’t have time to think – hell, I barely have time to sleep. Between work commitments, friend commitments, relationship commitments, and building my own brand, I am left with little time for myself. I’ve gotten into a pattern of trying to make every second add value (work-type value). What does it turn into? Burn out and ineffectiveness, and that is not what anyone wants or needs.
Just when you think something is such a simple and basic principle, you realize that the basics are often the first to go and the first to be questioned. Let’s revisit the definition of done and dissect this…Including a very high level take on the GROWS idea.