|
Hello project manager thread, technical IC here. Have noticed a pattern in $LARGE_ORGANIZATION and would like an outside perspective on how to come up with a realistic timeline for a project: What is the best way to deal with dependency teams (platform/infrastructure) that cause delays by ignoring requests, and only seem to move if escalated to the team's skip-skip level? When asked what happened, the most common answer is that they don't know what happened and, one time when we pushed further, that breaking SLA was inevitable because our team wasn't in their prioritization at the start of the year. We didn't even know they existed (frequent re-orgs). On the other hand, the executives are saying that the company should take a "bottom-up approach" to streamline processes, so they're clearly aware. Because it's a $LARGE_ORGANIZATION and re-orgs happen all the time, HLDs would take a lot longer to write if we must identify all of the exact people dependencies for a given project (and even if we did, another re-org could happen during the project if surprise delays go on for too long). Since different teams have different MOs when it comes to responsiveness and their SLAs, that makes it even harder to come up with realistic Sprint estimations. It seems the only effective strategy is to just escalate immediately after making every request and not to have any patience with anyone: to make even more noise than their other requests... but that doesn't seem healthy for anyone.
|
#
¿
Nov 18, 2022 16:37
|
|
|
|
| # ¿ May 10, 2024 04:09 |
|