3 Keys to Merging Agile, DevOps & Staff Augmentation
Strategies to enable IT organizations to support a fast-growing company
How do you enable an IT organization to support a fast-growing technology company while building a delivery model that scales and endures? This is a question I’ve been asked frequently—and one I’ve spent decades navigating across high-growth organizations such as Salesforce and Splunk.
IT has long been at the center of enterprise transformation. What is often underappreciated, however, is that IT organizations must continuously transform themselves in parallel with the business. At times, it can feel like changing the tires on a moving car—entirely possible, but requiring clarity of vision, disciplined execution, and strong leadership alignment.
The following are core strategies I’ve consistently applied to deliver results at scale in high-growth environments:
Product vs. Project: Shift from project-based delivery to a product-oriented operating model.
Agile and DevOps: Combine modern delivery practices with engineering discipline and automation.
Resource Strategy: Evolve workforce models to support speed, quality, and long-term capability building.
Let’s explore each in more detail.
Product vs. Project
This is not about whether your company sells products or services—it is about how IT delivers value.
Traditional project-based models are designed around fixed scope, timelines, and budgets. Success is often measured by whether a project is delivered on time and within cost constraints. However, this model does not inherently ensure that the right outcomes are achieved or that long-term business value is created. It can also lead to fragmented execution, limited knowledge retention, and slower delivery over time.
A product-oriented model shifts the focus to sustained ownership of business capabilities. Persistent teams are aligned to products or services, funded over longer horizons, and accountable for outcomes rather than outputs. These teams develop deep domain expertise and are better positioned to continuously evolve their products in alignment with business needs.
From an organizational standpoint, this model also aligns with how high-performing teams operate. Drawing from Tuckman’s stages of development—forming, storming, norming, performing, and adjourning—long-lived product teams spend more time in the “performing” stage. In contrast, project-based teams often disband just as they reach peak effectiveness, resulting in lost momentum and institutional knowledge.
While transitioning to a product-centric model is not trivial, it sends a clear signal to stakeholders: IT is committed to long-term capability building, continuous improvement, and delivering meaningful business outcomes.
Agile and DevOps
Agile and DevOps are often discussed independently, but their true value is realized when implemented together.
Agile methodologies—such as Scrum, Kanban, and Extreme Programming—enable teams to deliver iteratively and respond quickly to changing requirements. DevOps, on the other hand, represents a cultural and operational shift that integrates development and operations through automation, continuous integration, and continuous delivery (CI/CD).
In practice, product-aligned teams should have the flexibility to adopt Agile methodologies that best suit their needs. For teams using Scrum, a two-week sprint cadence is often effective in establishing predictable delivery cycles and improving cross-functional alignment.
However, Agile practices alone are insufficient without the supporting engineering discipline of DevOps. Automation across the software delivery lifecycle—from code integration to production deployment—is essential to achieving both speed and quality. This allows engineers to focus on solving business problems rather than managing manual processes.
From an operating model perspective, embedding teams with DevOps personnel, as well as establishing DevOps as a shared service, can drive consistency in tooling, standards, and practices across the organization, while also creating a clear career path for engineering talent.
The primary challenge is not technical—it is cultural. DevOps requires breaking down traditional silos and redefining roles and responsibilities. Resistance is natural. Success depends on leadership alignment, clear communication, and a sustained commitment to change. When done effectively, Agile and DevOps together enable organizations to deliver faster, more reliably, and with greater business impact.
Resource Strategy
Transforming delivery models requires more than new processes—it requires investment in people.
As organizations evolve toward product-based, Agile, and DevOps-driven models, skill gaps often emerge. At the same time, the business cannot afford a decline in delivery quality during the transition. Maintaining trust with stakeholders is paramount.
This is where a well-defined resource strategy, including strategic partnerships, becomes critical.
Staff Augmentation
A shift to Agile and product-based delivery necessitates a move away from traditional managed services models toward staff augmentation. Managed services often externalize critical expertise, limiting an organization’s ability to build internal capability and reducing long-term agility.
In contrast, staff augmentation integrates external talent directly into internal teams, enhancing capacity while preserving ownership and accountability. This model is far better aligned to Agile principles and supports the development of high-performing, cross-functional teams.
Attempting to apply managed services constructs within an Agile model is a common failure pattern. Organizations must align their sourcing strategy with their delivery model to succeed.
Recruiting and Hiring
It’s important to ensure that both internal and augmented teams meet consistent standards of excellence. This requires alignment on technical competencies, engineering practices, and cultural expectations. I strongly advocate for applying the same hiring rigor to contingent talent as to full-time employees, including technical assessments and evaluation of soft skills.
Learning & Development
One of the most valuable attributes to assess is the ability to both teach and learn. High-performing teams create a two-way exchange of knowledge: external talent brings new skills and perspectives, while internal teams provide institutional knowledge and context. This dynamic fosters a culture of continuous learning and becomes a meaningful competitive advantage.
Timezone Proximity
Team structure must also account for collaboration dynamics. While fully co-located teams may not always be practical, effective Agile delivery requires sufficient overlap for real-time communication. In my experience, maintaining a 2–3 hour overlap with the core business timezone strikes the right balance. This enables collaboration without introducing the inefficiencies and burnout associated with highly distributed, asynchronous models.
On-Call and Incident Response
A mature DevOps model requires shared accountability for production systems. Teams that build services must also support them. Establishing clear on-call and incident response processes ensures system reliability while reinforcing ownership. This expectation must apply to both full-time and augmented team members and should be clearly defined from the outset of any partnership.
Building Cohesive Teams
Sustaining high performance across distributed teams requires intentional effort. Strong relationships do not emerge by default—they must be cultivated.
Creating opportunities for teams to connect—whether through regular social interactions, volunteering initiatives, periodic in-person collaboration, or recognition programs—strengthens trust and reinforces a shared sense of purpose. These investments are not peripheral; they are foundational to maintaining teams in a high-performing state.
Final Perspective
Enabling IT to support a fast-growing enterprise while building a scalable, durable delivery organization requires deliberate choices. It demands a shift to product-based thinking, the integration of Agile and DevOps practices, and a resource strategy that prioritizes capability over convenience.
This transformation is not without challenges. It requires sustained commitment, cultural change, and strong leadership. However, when executed effectively, it positions IT not as a support function, but as a strategic driver of business growth, innovation, and long-term competitive advantage.