Most Agile teams think in sprints. Plan, build, ship. Repeat. It’s efficient. But in practice it leaves two critical variables out of the loop: discovery and validation.
In practice, this creates a predictable failure pattern: teams ship features quickly, only to discover the feature solved the wrong problem, or that the implementation didn’t account for real user behavior. The sprint cadence rewards velocity. However, velocity without direction is just moving fast in the wrong direction.
To solve this, at Cafeto, after 12 years of managing nearshore software teams, we’ve found that the most successful projects combine three frameworks: PHVA (Planear, Hacer, Verificar, Actuar Plan-Do-Check-Act), Agile methodology, and Dual-Track Sprint design. Together, they close the loop that standard Agile leaves open.
The problem with sprint only thinking
Agile was designed as a philosophy of empirical development build small, learn fast, adapt continuously. In reality, many teams, it has been reduced to a delivery machine: write tickets, run sprints, ship features.
What gets dropped from this machine?
- UX research that validates whether the feature is the right feature
- Design exploration that considers user flows before implementation begins
- Quality validation that goes beyond ‘the tests pass’
- Retrospective learning that actually changes how the next sprint is run
Ultimately, the result is predictable: fast teams building the wrong things. High velocity, low impact.
This is particularly acute in nearshore and remote team contexts, where the distance between business stakeholders and delivery engineers can obscure misalignment until it’s expensive to fix.
What is PHVA (Plan-Do-Check-Act)
To address this gap, PHVA is the Spanish adaptation of Deming’s PDCA cycle a continuous improvement framework developed in manufacturing and adapted widely in quality management and software engineering.
- PLAN (Planear): Define the problem, hypothesis, and success criteria before doing anything
- DO (Hacer): Execute the planned action in a controlled, observable way
- CHECK (Verificar): Measure the results against the success criteria
- ACT (Actuar): Standardize what worked; adjust or restart what didn’t
In practice, applied to software development, PHVA provides the meta-framework that Agile lacks at the strategic level. Where agile defines how the work happens (in sprints, with ceremonies, with backlogs), PHVA defines whether the work is the right work.
Bibliography references for PHVA in software:
- Deming, W.E. (1986). Out of the Crisis. MIT Press.
- Moen, R., & Norman, C. (2009). The History of the PDCA Cycle. Proceedings of the 7th ANQ Congress.
- ISO 9001:2015 Quality Management Systems — incorporates PDCA as a foundational principle.
Dual-Track agile: design and delivery in parallel
While PHVA provides the improvement loop, Dual-Track Agile, developed by Marty Cagan and Jeff Patton, separates development into two concurrent tracks:
Discovery track
Running continuously, 1-2 sprints ahead of delivery
Goal: Validate what to build before building it
Activities: User research, prototyping, UX design, technical spike, stakeholder validation
Delivery track
Standard sprint cadence (1-2 weeks)
Goal: Build what has been validated in discovery
Activities: Implementation, code review, QA, release
The insight of Dual-Track is simple: discovery and delivery should not compete for the same sprint. When they do, discovery loses. Teams skip research and ship assumptions.
As a result, by separating them structurally, you ensure that what enters the delivery track has already been validated
Reference:
- Cagan, M. (2008). Inspired: How to Create Tech Products Customers Love. SVPG Press.
How PHVA + Agile + Dual-Track work together
When these frameworks are combined, a clear operating model emerges. Here’s how Cafeto integrates all three:
First, PLAN (PHVA) → DISCOVERY TRACK (Dual-Track Agile)
Before a sprint begins, the discovery team (product + UX + tech lead) validates the hypothesis. What user need are we trying to address? How will we know if the solution is successful? What technical limitations do we need to consider?
This is PHVA’s PLAN phase but executed with Agile’s lightweight documentation and collaborative approach.
Next, DO (PHVA) → DELIVERY TRACK (Sprint Execution)
The delivery team builds what has been validated. Because discovery happened first, the sprint backlog contains tickets with clear acceptance criteria, validated UX, and architectural clarity.
This is standard Agile delivery but with a foundation of validated intent.
Then, CHECK (PHVA) → SPRINT REVIEW + RETROSPECTIVE
Beyond velocity metrics, the team measures outcomes: did the feature solve the problem it was designed to solve? Are the success criteria from PLAN being met? The retrospective isn’t just about process — it’s about product learning.
Finally, ACT (PHVA) → BACKLOG REFINEMENT + DISCOVERY PIVOT
What worked gets standardized. What didn’t triggers a new discovery cycle. The backlog is updated to reflect real learning, not just the next set of assumed tickets.
Why this matters for remote teams specifically
This becomes even more important in remote and nearshore teams, where communication is less organic and real-time than co-located teams. This makes implicit alignment (the kind that happens in hallway conversations) impossible. Everything must be explicit, documented, and agreed upon before work begins.
PHVA + Dual-Track enforces this. When discovery happens before delivery, the team enters every sprint with shared context reducing misalignment and rework that would otherwise require expensive synchronous meetings to resolve.
Conclusion
Ultimately, Agile isn’t wrong. Sprint-only thinking is wrong.isn’t wrong. Sprint-only thinking is wrong. The most effective development teams co-located or nearshore combine the rigor of PHVA, the adaptability of Agile, and the clarity of Dual-Track design.
At Cafeto, this framework isn’t theoretical. It’s how we run projects. It’s why our clients ship things that work, not just things that are done.
Want to see how this would apply to your team’s context? Let’s talk.
Book a Consultation to learn about engineering operations to Colombia:
https://outlook.office.com/book/[email protected]/?ismsaljsauthenabled
Learn about: The Changing Economics of the H-1B Visa here
