Tag: Dependencies
-
Better Planning with Two-Sided Dependencies
Every year, teams invest massive effort in annual plans that typically fail for one key reason: dependencies. Detailed timelines, careful estimates, and beautiful roadmaps all unravel once work begins and unforeseen issues with dependencies arise. Plans are always imperfect, and estimates are always off, but in large organizations, where delivery requires multiple teams and services,…
-
The Hidden Costs of Over-Collaboration
In the wake of Agile’s success and the benefits it offers organizations to help them achieve faster delivery, happier customers, and more engaged teams, “Collaboration” has become a buzzword. However, the way I see most teams practice collaboration is not in the sense of collaborating with customers; their focus is on the internal collaboration necessary…
-
The Team Dependency Matrix
In the large organizations I work with, dependencies are the number one blocker preventing fast flow. In these organizations that, for budgetary reasons, do annual planning, dependencies are the most significant determining factor to the success of their plans and the biggest afterthought. The tendency I see is for teams to plan their work as…
-
The Power of Predictable Delivery
With most of the Agile teams I’ve been exposed to, I’ve noticed that they spend easily over a hundred person-hours every month on practices like updating plans, reporting metrics, estimating, and sharing status updates. To them, these are some of the core practices that make them Agile. In general, as a way to be less…
-
Snapshot: Introducing Ready Options to a B2B Service Team
When I work with teams who have undergone Agile or Product training, these teams often have large backlogs of work and boast about the importance of prioritizing work based on value. I’m currently helping a team that went through such training years ago, but these practices of having a backlog and focusing on customer value…
Flow Focused 