Selection of sources worth following from the book: The forgotten new philosophy of work, management & leadership
Many have already explored the trajectory of Agile adoption, the changes in sentiment toward Agile, and the recent challenges.
This is a new look at how the population of Agile practitioners changed over time.
Whether it is to a Subject Matter Expert, an external contractor, an Agency, a Global/shared Function, a Team Topologies’ Platform team or a Complicated subsystem team, when and how can some tasks and/or responsibilities be effectively moved outside the team?
Is there a valid alternative to Agile cross-team collaboration, one of the most consequential topics for successfully adopting Agile beyond one team? Should we tackle Agile cross-team collaboration challenges or transcend them?
This post is a four-part deep dive into the How-Tos of making Agile cross-team collaboration frictionless and enjoyable, in one word: effective. That is one of the most consequential topics for successfully adopting Agile beyond one team. Ironically, none of the current “scaled” solutions cut it.
Coaching literature extensively covers the “don’t collude” principle. But you also need to know the “don’t be taken hostage” principle.
A collection of short videos, interesting books, and inspiring thought leaders worth following, to test the whitewaters of modern leadership for modern organisations
There is a mismatch between the reality of modern software and digital products development and the binary separation between CapEx & OpEx. Let’s see how modern approaches overcome that.
OKRs (Objectives and Key Results) are, for many organisations, still a relatively new term that, as such, can hold the promise of an idealised future while moving again the goalpost to a later tomorrow.
And the term OKR creates enough ambiguity allowing different conflicting interpretations (e.g. a new fancy name for KPIs) to coexists. But once OKRs are well understood and properly put to practice, are they really good for innovation?
Automation practices in Agile Software Development have an important role. But what about Agile outside IT? What to automate? How to automate?
Here the link to the wiki of Complexity inspired practices for software and digital products development
An InfoQ article on practices inspired by Complexity theory that can be used everyday in Software and Digital Products development