Discovery
Understand the customer and cherry-pick which processes can and should be adopted for their project.
05 Expertise
dNA —
dotNear Agility
dotNear has gathered 10+ years of experience developing software using Agile processes, adapting the Agile philosophy to work in a distributed development environment, typical of nearshore and outsourcing setups.
Foundation
Reveal business objectives and align architecture and functionality to current and projected outcomes.
Shippable sprints
Every sprint should deliver a potentially shippable product. Not a status report — a working increment.
Test-driven
A TDD environment that aims for no defects going forward. Testing is part of delivery, not a client task.
Total cost of ownership
We look forward, beyond today’s spend. We don’t do well as duct-tape programmers.
Distributed by design
Agile adapted to geographically distributed teams, with transparency as the governance mechanism.
In practice
Agile, adapted to
the distance.
We work in a naturally Agile way. We develop code for the sake of the outcome, not for the sake of the code. This helps us be more productive in terms of function points and keeps our code lean.
Agile is our preferred approach to development, and we use mainly Scrum. Pair programming for complex tasks, as well as TDD and CI/CD, are part of our usual take on projects. Unlike many nearshore firms who expect the customer to test their output, testing is an intrinsic element of our product delivery.
Our teams are all cross-functional. Team members have specialisms, but work together to optimise delivery time and quality, rather than focusing on their initial functional role and waiting for their turn to contribute.
We have subject matter experts on financial services, logistics, retail and travel — both in our nearshore location in Romania and trusted partners in the UK, Belgium and the Netherlands.
Sprint 01
Potentially shippable, every two to three weeks.
Distributed by design
“By breaking work up into a series of potentially shippable products delivered via sprints of two to three weeks, issues become visible to stakeholders almost immediately and can be resolved quickly.”
We are experienced in using Scrum across multiple distributed teams for software product development — one onsite and one nearshore, typically, but also one onsite and multiple nearshore teams which need to cooperate for the same goal.
Next step
Send us a project brief. Or just say hi.
A short note is enough. We reply within one business day, and a qualified shortlist can follow in 48 hours.