2 ms·
A couple of questions then: what's the long term result of a perpetual "I haven't done {thing X} because of {justification Y or Z}"? And related to that, do yo
by ethbro 11y ago
A couple of questions then: what's the long term result of a perpetual "I haven't done {thing X} because of {justification Y or Z}"?
And related to that, do you encounter the "no one on the agile team is empowered to remove this blocker" (because it's too many departments away and that team has no stakeholder/ownership close enough to the agile team)? If so, how does that play?
- alistairSH 11y ago1. Most of those can be avoided with enough coordination and planning. If you know thing X has a dependency, you need to plan for it (and make sure any other team knows about it). Weekly scrum-of-scrums, leadership meetings, etc. 2. No, we don't usually encounter that. That said, when we do run into long-running problems, we do need to escalate. One of our systems had some serious performance problems and it did take VP involvement (daily 15 minute standup with the players involved) to keep things moving towards a resolution. It's annoying when it happens, but I'm not sure it's completely avoidable in a large org. Perhaps I've been lucky, but management has always had my back - we def have a culture of servant-leadership, at least in my division.