More on this book
Community
Kindle Notes & Highlights
Read between
October 25 - October 31, 2022
If the desired state is agility, the way there should already be agile.
Organizational change should start with the organizational processes because fulfilling customer wishes, as well as the Time-to-Market, is a question of the processes used, collaboration and dependencies.
There should be as many dependencies eliminated as possible. Most important, though, is good management of every dependency which remains.
Stringing together locally optimized units does not create a globally optimized system—as
If a team optimizes itself to the highest degree, the entire value chain can get messed up.
it isn't important how fast individual teams within an organization work. If we want to increase the system output, we must ensure that the right team is working on the right thing at the right time.
An organization's agility is not created by stringing together a bunch of agile teams. Agility is created when the interactions between teams are agile.
At Flight Level 3, the focus is on prioritizing upcoming projects and initiatives according to the strategic direction of the company. At Flight Level 2, the focus is on breaking down the chosen projects and initiatives into actionable pieces and coordinating the work with the participating operational units. At Flight Level 1, the teams involved in the operational work separate the tasks of the project/initiative into smaller packets and are focused on delivering them.
Value for the customer is only created when they receive the right product. The customer doesn't care how the people working on and delivering the product were organized and structured.
It will never be possible to have absolutely no dependencies between teams, services and products within an organization. However, you can and should make it a habit to eliminate dependencies whenever possible.
To avoid having meetings, you can certainly write thousands of Emails, or only a few teams coordinate with each other, or each team continues to make their own isolated decisions—but these are clumsy solutions that require additional coordination rather than bringing improvement.
An estimation only needs to be as exact as necessary, not as exact as possible.
Cross-functionality is a company mentality and not an organizational setup for teams.
Important meetings should be held frequently
