How we work
How we deliver projects across teams and time zones
We blend proven practices, from classic waterfall planning to modern agile delivery, into one way of working. It holds up whether your project has a single team in Los Angeles or several teams across locations and vendors.
Distributed delivery
Multi-site, multi-vendor projects with mixed teams
We have worked with software vendors and with businesses outside the software industry, on projects with teams in different parts of the world.
Done well, distributed development produces high-quality software faster, makes a business more agile and better able to handle competition. Done badly, it produces delays and misunderstandings. These are the two challenges we plan for on every project:
The challenge
Communicating clearly across distance, time zones, languages and cultures
How we handle it
One project manager as your point of contact, decisions written down where everyone can see them, and progress shared in your client portal rather than scattered across email.
The challenge
Managing requirements, changes, assets, code and testing when people are in different places
How we handle it
Every part of the lifecycle is planned for a distributed team from the start, so there are no overlaps between teams and no conflicting delivery dates.
Practices
Agile for distributed development
Customer focus
Every team, wherever it sits, delivers the highest-priority features first, so the most valuable work reaches you soonest.
Sprint reviews
At the end of each sprint the delivered features are reviewed with you and your feedback goes into the next one.
Test-driven development
Tests are written before the code. That keeps the design as simple as possible, gives good test coverage and stops features creeping in that nobody asked for.
Refactoring
Code is improved continuously as the product evolves, which keeps the architecture healthy instead of piling up problems for later.
Team set-ups
Three distributed Scrum models
Distributed Scrum
How the teams are organized
Cross-functional Scrum teams in each location, coordinated by a Scrum of Scrums that meets regularly across locations.
A good fit for
Larger products split between several teams that still need to ship together.
- One Scrum team per location
- Scrum of Scrums hub
From first call to launch
See how a project would run
Stage 1 of 4
Discover
A free call to learn your goals, customers, and current setup. Business analysts join when the project needs them.
Your side
What this looks like from your side
You don't need to know Scrum to work with us. You get a clear plan, regular demos and one person to ask.
- A written plan with priorities agreed before work starts
- The highest-priority features delivered first
- A review of finished work at the end of every sprint
- Milestones, tasks and approvals in your client portal
- Independent QA on every project, described in our quality policy
Read about our quality policy or the ways you can engage us.
Want to start a project?
Tell us what you want to achieve. A strategist reads every request and replies within one business day with next steps, or a straight answer if we aren't the right fit.