Скачать или смотреть Remove Dependencies, Don't Organize Around Them in Agile Development

Watch the full podcast (AA121):    • AA121 - Self Organization Gone Bad  

...and find out what happens when self organization goes off the rails!

Remove Dependencies, Don't Organize Around Them in Agile Development #agile #short

= = = = = = = = = = = =
Subscribe to @arguingagile
   / @arguingagile  
= = = = = = = = = = = =

Or Listen On:

Apple Podcasts:
https://podcasts.apple.com/us/podcast...

Google Podcasts:
https://podcasts.google.com/feed/aHR0...

Spotify:
https://open.spotify.com/show/362QvYO...

Amazon Music:
https://music.amazon.com/podcasts/ee3...

Stitcher:
https://www.stitcher.com/show/agile-p...
------------------------------------------------------
We're going to talk about a lack of communication and coordination.

The collaboration aspect is inside of a team and communication coordination, I feel is the team out to the rest of the organization. And, I would say organizations catch this problem faster than they catch collaboration inside the team.

Yeah, I agree. These are usually prevalent and again symptoms wise teams will say we're waiting on So and so but that's an external dependency which they put on the board as a dependency and they will say yeah, but You know, it's there. We raised it. You raised it to to where? Don't put it on a board. Try and focus on getting it off the board.

Yes, it's one thing to make it visible. Fine. But then what? The goal should be to get rid of it off the board, which means either to accept it, mitigate it, resolve it, etcetera. And doing that involves interactions outside the team.

So when you have this kind of a challenge, what it looks like in real life is You know missed deadlines or or work that's carried forward and then people hide behind that we're waiting on them, right?

That's the classical oh, but the holes on your side when you're in a boat