TellenzeReading Radar
Explore Agile, ways of working and practical AI for teams. Find recent articles from six sources, then follow an idea back to its author.
Read our perspectiveWe're excited to announce a new strategic partnership with Kosli, the w orld's leading SDLC Governance platform. Together, we'll be helping regulated enterprises achieve faster, more efficient software delivery while maintaining the strict compliance and security requirements their industries demand.
As banks accelerate DevOps, manual governance lags behind. Drawing on DORA research and real-world banking experience, this ‘Expert View’ article shows why traditional approvals increase risk and slow delivery—and how automated, peer-review-driven governance aligns compliance with high-performing software delivery.
For organizations facing critical structural bottlenecks or striving for radical business agility, the solution requires fundamentally reshaping how teams are organized around value delivery, managing both the complexity and the cognitive load placed on people. The core question must shift from, "Are we doing Agile right?" to, "Are we organized in a way that supports flow?".
The second edition of Team Topologies is now available. Six years after the original publication sparked a fundamental shift in how organizations approach structure and purpose, this updated edition provides the evolved framework leaders need to navigate today's complex landscape.
Agile gave us better delivery practices, but many teams still struggle with invisible friction. The real bottleneck isn't your ceremonies-it's whether your org structure actually supports fast flow. Rich Allen's final piece in the 'Why Agile Isn't Enough' series explores how outdated team boundaries and coordination overhead quietly slow delivery, and why treating structure as a design lever (not a fixed artifact) can unlock the flow your teams are capable of.
In this 2nd part of the newsletter series ‘Why Agile isn’t enough (and what’s really slowing you down), Rich Allen explores two less visible frictions, overloaded platform teams and overly collaborative operating models, that quietly slow delivery. Instead of more process, we may need better questions about how our teams are structured, how they interact, and whether we’ve designed the organisation for clarity, autonomy, and flow.
The second edition of the book Team Topologies provides vital success stories, analysis, commentary, and clarifications to help leaders plan and execute transformations in every industry sector and geography.
Many teams adopt Agile in the hope of moving faster. They introduce sprints and stand-ups, visualise the work, and improve discipline at the team level. The process brings rhythm, visibility, and a sense of progress, and yet, delivery is still slow. Work gets done, but the value takes too long to reach users. Dependencies multiply, coordination becomes a constant effort, and every step forward seems to rely on waiting for someone else. "We're doing Agile", but are we really being agile? For many organisations, introducing Agile helps make the work more visible. Teams are more aligned in how th
Follow the ideas
These articles belong to their original authors. Summaries help you choose what to read; visit the original for the full context.
COME TAKE A LOOK
Curious? Join the waitlist and see how we welcome your team.
Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.
Join waitlist Start with your email. No payment needed to join.