.png)
Scaling Agile: "Splitting Without Splitting" for Specialized Tech Teams
Explore how a market research giant innovates team structures and collaboration for large, specialized tech teams, blending agile principles with contextual flexibility.
Key Insights
-
Insight
Nielsen IQ, as a market research company with a large technology operation (2-3k tech employees within 30k total), intentionally maintains diverse and specialized roles, including academic data scientists. This structure challenges the industry's push for full-stack developers due to skill development and contractual complexities.
Impact
This highlights a strategic shift from generic full-stack roles towards specialized expertise in data-intensive environments, potentially influencing how companies structure and invest in diverse technical talent.
-
Insight
There is no single 'perfect solution' for scaling or splitting large development teams. Instead, a contextual approach like 'splitting without splitting'—maintaining one cohesive team culture while creating distinct deep-work spaces for sub-groups of 20-25 individuals—proves effective.
Impact
This insight offers an alternative to rigid team splitting, enabling large enterprises to maintain team identity and collaboration while benefiting from focused work, improving productivity and morale in complex projects.
-
Insight
Implementing 'fluid team' structures allows a single large team with multiple specialized backlogs (e.g., business operations, data science research, engineering standards) to dynamically re-team every sprint. This adaptability ensures optimal resource allocation based on shifting priorities and required skill sets.
Impact
Fluid teams can significantly enhance responsiveness to changing business needs and technical demands, preventing bottlenecks and maximizing the impact of specialized skills within dynamic project environments.
-
Insight
Effective team collaboration models must integrate three critical forces: system architecture, product vision and stakeholders, and, crucially, the 'people' dynamics (e.g., communication patterns, individual preferences). Decisions should not solely be technical or product-driven.
Impact
By prioritizing human factors alongside technical and product considerations, organizations can foster more sustainable, engaged, and productive teams, leading to better outcomes and reduced turnover.
-
Insight
Objective data from Developer Experience (DX) surveys (based on DORA metrics) and agile maturity matrices are crucial for validating organizational changes and gaining leadership buy-in. Metrics must be used constructively to build trust and facilitate improvement, not for punitive measures.
Impact
Leveraging transparent, trust-based metrics empowers teams to drive their own improvements and provides leadership with actionable insights into the effectiveness of agile transformations, improving decision-making and investment ROI.
-
Insight
Large enterprises can maintain an appearance of adopting standard frameworks (like SAFe) for management, while individual teams 'cherry-pick' and adapt elements from lightweight approaches (e.g., Less) to fit their specific context, thereby avoiding bureaucracy and fostering autonomy.
Impact
This highlights a practical strategy for balancing enterprise-level governance with team-level agility, enabling organizations to achieve perceived standardization while fostering real-world flexibility and innovation.
-
Insight
Comprehensive visualization tools, including communication maps (graphing individual collaboration), architecture diagrams overlaid with personnel, and stakeholder maps, are essential for revealing complex team interactions and dependencies. This transparency enables informed decision-making on team structure.
Impact
Enhanced visualization provides a clear, shared understanding of complex organizational dynamics, allowing teams and leaders to collaboratively design more effective structures and resolve collaboration bottlenecks proactively.
Key Quotes
"Maybe there is not one perfect solution. I think this is kind of the biggest realization that we've made that there is actually no perfect solutions."
"And for us as coaches, it's important for us not to make those decisions for the teams, but give them the space and the tools to visualize every aspect of these so they can reason about their own situation and make decisions that are more suitable for their context."
"But also you have to keep in mind that the metrics are one part, but who is using them, how they're using them, this would affect the measurement. And if you are in an environment, you can have the best metrics, but if you use those metrics to make um people's lives harder, then you're not gonna get a fair measurement."
Summary
Navigating Agile at Scale: The "Splitting Without Splitting" Imperative
In today's complex technological landscape, scaling agile methodologies in large enterprises presents a unique set of challenges, especially when dealing with highly specialized roles. This discussion with agile coaches from Nielsen IQ, a market research giant with a substantial technology operation, sheds light on innovative approaches to team structure and collaboration that defy conventional wisdom. Their experiences offer critical lessons for leaders and investors aiming to optimize efficiency and foster innovation without succumbing to rigid frameworks.
The Dynamics of Specialized Teams in an Enterprise Context
Nielsen IQ, with 30,000 global employees and 2,000-3,000 in tech, operates not as a pure technology company but as a data-intensive market research firm. This context necessitates a diverse workforce, including data scientists (many from mathematics/statistics backgrounds learning to code), machine learning engineers, SREs, and traditional front-end/back-end roles. While the industry often pushes for full-stack developers, Nielsen IQ intentionally maintains specialized roles, navigating the complexities of skill development, contractual obligations, and organizational design. The challenge lies in integrating highly academic data scientists who contribute significantly to research (problem space) while also embedding them in operational teams (solution space).
"Splitting Without Splitting": A Flexible Model for Large Teams
The conventional wisdom for large teams (exceeding 20 people) is often a hard split. However, Nielsen IQ realized there's "no perfect solution." Instead, they embrace a concept of "splitting without splitting" for teams ranging from 20-25 individuals. This approach maintains a single team culture, name, and shared principles, while simultaneously creating dedicated "deep work" spaces where sub-groups can focus. A provocative example is the "fluid team" model, where a single large team with three distinct backlogs (business operations support, data science research, engineering standards) dynamically re-teams every sprint based on shifting priorities and required skill sets. This fluidity allows for optimal resource allocation and ensures that critical tasks, be it contract fulfillment or security updates, are always addressed.
The Three Forces: Architecture, Product, and People
Crucially, effective team collaboration models, according to Nielsen IQ, must consider three intertwined forces: system architecture, product vision and stakeholders, and the often-overlooked people dynamics. Decisions on team structure and interaction should not solely be dictated by technical coupling or product roadmaps but must also account for individual preferences, existing communication patterns, and interpersonal relationships. Agile coaches play a vital role in facilitating these discussions, providing teams with tools to visualize these forces, rather than imposing solutions. This ensures that the chosen approach is suitable for the specific team context and fosters a sense of ownership.
Data-Driven Decisions and Contextual Agile Adaptation
To validate their experimental team models and gain leadership buy-in, Nielsen IQ relies on objective data. Developer Experience (DX) surveys, based on DORA metrics, and agile maturity matrices are instrumental in measuring team happiness, process efficiency, and overall satisfaction. These metrics provide a factual basis for conversations with management, demonstrating the impact of different approaches. Importantly, they emphasize that metrics must be used to facilitate improvement and trust, not to punish or create undue pressure. Furthermore, while the company might appear to adopt standardized frameworks like SAFe at a management level, teams are encouraged to "cherry-pick" elements from lightweight methodologies like Less (Lightweight Scrum) to craft solutions that genuinely fit their context, avoiding rigid dogma and bureaucracy.
The Power of Visualization and Continuous Evolution
A cornerstone of Nielsen IQ's approach is extensive visualization. This includes communication maps (graphing individual collaboration frequency), architecture diagrams overlaid with team members, and stakeholder maps. These visual tools help demystify complex interdependencies, identify crucial connections, and highlight potential pain points, allowing teams to collectively reason about their dynamics and design effective collaboration strategies. The journey is one of continuous improvement; there is no "final" model, as team compositions, product requirements, and technologies are constantly evolving. Ultimately, the goal is to create cohesive customer experiences by fostering adaptable, self-organizing teams that can deliver value effectively, even within the confines of a large, specialized enterprise.
Action Items
For large or growing teams (e.g., 20-25 people) with diverse specializations, implement a 'splitting without splitting' strategy. Maintain a single team identity and shared culture, but establish distinct, focused 'deep work' spaces for sub-groups during sprints.
Impact: This approach can enhance focus and productivity within sub-groups while preserving overall team cohesion and reducing the administrative overhead associated with formal team splits, leading to more efficient delivery.
Introduce 'fluid team' models for complex projects requiring varied expertise across multiple workstreams. Design a system where team members dynamically re-team each sprint, aligning with the highest priority items across specialized backlogs (e.g., business, data science, engineering).
Impact: This allows for highly adaptive resource allocation, ensuring that the most critical tasks are always addressed with the right skills, potentially accelerating time-to-market and improving strategic alignment.
When redesigning team collaboration, conduct workshops to explicitly visualize and consider the interplay of system architecture, product vision and stakeholders, and the 'people' dynamics (e.g., communication patterns, individual preferences, interpersonal relationships).
Impact: By taking a holistic view, organizations can design team structures that are more resilient, foster better morale, and align more effectively with both technical constraints and human needs, reducing friction and increasing collaboration.
Implement and consistently use developer experience (DX) surveys (based on DORA metrics) and agile maturity matrices. Utilize the data transparently to inform team-driven experiments and to effectively communicate progress and challenges to leadership, fostering trust.
Impact: Data-driven insights empower teams to continuously improve their processes and provide leadership with objective evidence for strategic investments in organizational change, leading to more targeted and effective improvements.
Develop and employ comprehensive visualization tools, such as communication maps (detailing collaboration frequency), architecture diagrams overlaid with team member responsibilities, and stakeholder maps. Use these visuals to facilitate team discussions on current dynamics and potential structural changes.
Impact: Increased transparency regarding team interactions and dependencies enables collective problem-solving and fosters a shared understanding, leading to more informed and accepted decisions about team organization and workflow.
Mentioned Companies
Nielsen IQ
4.0The company is central to the discussion, providing the real-world context and examples for the agile scaling strategies being presented.