Dedicated teams and outsourcing
Developers, QA people and project managers who step into your code and start working.
The problem this solves
Recruitment takes time the project does not have. By the time an experienced developer is found, signed and settled in, the window for that release has closed. And when the project ends, the organization is left with a headcount it is not sure it needs.
The second problem is entering an existing system. A good developer who is not used to reading other people’s code spends months finding their way, and in the meantime nobody is delivering.
An experienced outside team solves both, as long as it works by the same rules as the internal team.
How Target runs such projects
There are two ways to work with us. We take full responsibility for a project and run it from the specification through production, or we complete an existing team with people who fit into your way of working.
Before we start we learn what the system does, where it hurts and what is measured. From there we assemble the team: developers, QA people and a project manager as needed. The first week goes to getting to know the code and the domain, alongside a contact at the client.
The work runs to our standard: code review, testing before a release, and regular reporting on progress. The team can grow under load and shrink after it.
Example project
We run development and outsourcing teams for leading companies in the market. The teams meet hard deadlines, grow and shrink according to the client’s needs, and hold a high code and security standard throughout.
How a project starts
- 01 Project ownership
We either own the project end to end, or join the client's existing team and work alongside it. We agree on which way to work at the start.
- 02 Specification and architecture
The specification is written with the people who actually use the system. The architecture follows: separation between components, a permission model, and the way external systems connect.
- 03 Build and production
Development moves in versions, with code review and a fixed code standard. After going live there is ongoing monitoring, incident handling and further development.
Questions we get asked
How long before a developer becomes productive?
Usually two weeks to a month, depending on the size of the system. We send people who are used to reading code they did not write, and we ask for a contact on the client side for the first week.
Can the team grow or shrink partway through?
Yes, that is what the model is for. The engagement is built so scope can change on agreed notice, without losing the knowledge the team has built about the system.
Who manages the team, us or you?
Both ways work. Some clients manage the people directly, and some prefer that we put a team lead of ours in place who reports on progress. We agree on it up front.