Dedicated development team

A dedicated development team that works inside your own tools

Engineers, a designer and a tester assigned to your product on a monthly engagement, with the roles written down and the code held in your repository.

Get your team scoped in writing
Trusted by the world's fastest-growing brands

What a dedicated team is

A team assigned to one product, paid monthly

A dedicated development team is a group of engineers and supporting roles assigned to your product on a monthly engagement. The roles are listed in a written agreement, and the team works from your backlog in your tools.

RDelivery app teamBuild stage · 4.0Designer0.5iOS engineer1.0Android engineer1.0Backend engineer1.0Tester0.5GGitHubJJiraSSlackAll in your name

Roles in writing

The agreement lists the roles on the team, such as iOS engineer, backend engineer and tester, and how much of each role your product receives.

Your tools, your queue

The team takes work from your Jira board, talks in your Slack and pushes code to your GitHub, so your people see the work as it happens.

Sized to the stage

A first version needs a different mix than a mature app. The team grows or shrinks as the written agreement sets out, and you approve the change.

Team or fixed scope

A monthly team or a fixed-scope project

The right model depends on how well the work can be written down in advance.

Fixed-scope projectA defined deliverable at one priceDedicated teamCapacity on a monthly term
What you buyA defined list of features, delivered for one priceA set of roles working on your product each month
Who sets prioritiesThe scope document, with changes written up and pricedYou, through your own backlog, as the product changes
How the cost behavesA single price for the scope, plus any approved changesA monthly figure that follows the size of the team
Best whenThe first version can be listed in full before work startsThe roadmap is long, or it will change as you learn
What you manageApproval of the scope and acceptance of each milestoneThe backlog, the priorities and the product decisions
How we decide

If the first version can be written down, we scope it as a project with a fixed price for the first milestone, from $25,000. A team makes sense once there is a product to keep building.

Facts that shape a team

Four facts about building with a team

Team size, repository control, the Apple account holder and protected branches, each with its source.

  1. Team sizeScrum Guide

    The Scrum Guide describes a team of typically 10 or fewer people.

    The Scrum Guide says a Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint. We size the team to the stage of the product and write the roles into the agreement.

  2. Repository accessGitHub

    On GitHub, organization owners have complete administrative access to the organization.

    GitHub’s documentation says organization owners have complete administrative access, and owners can assign other roles to individuals and teams. That is why the repository sits in an organization you own, with our engineers added at the access level the work needs.

  3. Store accountsApple Developer

    Apple gives an organization’s developer account to one person, the Account Holder.

    Apple says the Account Holder for an organization manages the account, renews the annual membership and accepts legal agreements on the organization’s behalf. For an app, that account should be yours, with our engineers added as team members.

  4. Code reviewGitHub

    GitHub can require approving reviews before a pull request is merged into a protected branch.

    GitHub’s documentation says repository administrators, or custom roles with the “edit repository rules” permission, can require a specific number of approving reviews before a merge. Because the repository is yours, you can set that rule on the branches that matter and decide who reviews.

What the team covers

Six parts of working with a dedicated team

From who is on the team to scaling it up or down, each part names what you hold.

Full-time roles by stageIn writing4.0Build2.5After launch4.5Feature pushBackendTesteriOSDesignerAndroid

Team composition by stage

The mix of roles changes as the product matures. Early on, a designer and a backend engineer matter most. Around launch, mobile engineers and a tester carry the load. Later, a smaller team can run releases and fixes. You receive: a role table for each stage in the written agreement.

DiscoveryFirst versionAfter launch
Access for the teamYour accountsGGitHubWriteJJiraMemberSSlackShared channelAAppleApp ManagerRevise any level laterGitHub roleReadTriageWriteMaintainAdmin

Onboarding to your tools

We ask for access to the tools your people already use and work in them, so there is no second backlog or side channel. You decide the permission level for each person. You receive: an access list showing who holds what, which you can revise whenever you choose.

GitHubJiraSlack
AccountsOwned by youAccountYour roleOur accessGitHub organizationOwnerCloud hostingOwnerApple DeveloperAccount HolderGoogle Play ConsoleOwnerAdmin credentialsSample Route Co.

Code and accounts in your name

The repository, the cloud account, the Apple Developer account and the Google Play Console account belong to your company from the first commit. Our engineers are members of them. You receive: the admin credentials and the ability to remove our access.

Team agreementSignedClause 9 · Assignment of IPDeveloper assigns to Client all right,title and interest in the code and designsthe team produces.A signed writing, per 17 U.S.C. § 204(a)Sample Route Co.WebzeniaSchedule B · licensesApache-2.0MIT

IP assignment in writing

The agreement assigns the code and designs the team produces to you, in a signed writing, which is what the Copyright Act requires for a transfer. You receive: the signed assignment clause, plus a list of the third-party libraries and their licenses.

Delivery app boardYour JiraIn reviewPull requestsReleaseYou approveRC-12Driver sign-inChecks passedRC-13Route listYour commentsTest buildSign-in and listTestFlightPlay internalApprove release

Planning and review

Work is planned from your backlog and arrives as pull requests in your repository, where your own engineers can read, comment and ask questions. Builds go to testers on TestFlight and Google Play internal testing. You approve each release before it goes to the stores. You receive: the pull request history and installable builds.

BacklogPull requestsBuilds
Role table: feature pushApproveRoleNowNewDesigner–0.5iOS engineer0.51.0Android engineer0.51.0Backend engineer1.01.5Tester0.50.5Team total2.54.5

Scaling up or down

When the roadmap grows or slows, the team changes size as the written agreement sets out, and you approve the new role table before it takes effect. The change starts once you approve the new role table. You receive: an updated role table in writing.

How it runs

Agree, onboard, plan and review, adjust

No stage starts until you approve the one before it. The documents below show what each one hands over.

team-agreement.csv

Team agreement: roles

Sample · Sample Route Co. delivery app, build stage
RoleShare of a full-time roleWorks in
Designer0.5Figma, then your Jira
iOS engineer1.0Your GitHub
Android engineer1.0Your GitHub
Backend engineer1.0Your GitHub
Tester0.5Your Jira and TestFlight
Team total4.0Monthly figure set in the written scope
The agreement names each role and its share. Changes to the table need your approval.

Our stack

The tools behind the team

The tools the team works in day to day. Choose any tool to see how it is used.

GitHub
Why GitHub

GitHub holds the code and the history of every change made to it.

How we use it

The code lives in a GitHub organization you own, and changes arrive as pull requests your engineers can read.

ReviewCI/CDActions
GitHubYes
GitLabYes
BitbucketPipes
NoneNo

Questions

Dedicated development team, answered

Start here

Get your team scoped in writing

Tell us what the team would be building and what you already run. We’ll send back the roles, how much of each your product needs, and the monthly figure in a written scope.