Dedicated development team

We need skills the team doesn’t have

When a team lacks skills, the quickest route seems to be a dedicated development team, brought in from outside to do the work. The work gets done, and the skills leave with the people who did it. At the next stage the team finds its practices unchanged since the start, nobody to learn from, and more code whose reasoning it doesn’t know.

Book a call

Does this sound familiar?

  • The product has real customers, integrations and loads that the code written at the start never anticipated.
  • Important decisions, such as changing the architecture or the way you release, keep being put off for fear of getting them wrong.
  • Hiring is slow, and newcomers learn from colleagues who have no time to teach.
  • A vendor gave us working code, and when they left the team no longer knew how to change it.
  • Automated tests, refactoring and frequent releases are practices the team knows, and can’t put into practice under deadline.

What stops the team growing with the product?

A team’s skills grow by working alongside people who already have them, on everyday code. The causes below take away that opportunity one after another. Those who knew have left, those who remain have nobody to learn from, and practices stand still.

  1. Practices haven’t moved on since the start

    Code born to test an idea now has to carry customers, integrations and a bigger team, while the team still develops it with the practices it had at the start. Without automated tests and continuous refactoring every change becomes riskier, and the team slows down just when the product asks more of it.

  2. The team is facing this stage for the first time

    Everyone knows the practices they need only by hearsay, and the most experienced people are absorbed by urgent matters. The practices are learned by pairing with people who have used them for years, on sprint tasks and on the code you have to deliver.

  3. Vendor code arrived without the practices to evolve it

    When a vendor writes important parts of the product, the team inherits the code without ever having worked with those who knew how to write it that way. The practices that code needs in order to evolve haven’t been passed on, and the team changes it with caution.

What changes when skills grow inside the team

People on the team pair with senior engineers who practise eXtreme Programming on sprint tasks, and the practices that were missing become the normal way of working on your code. Decisions that were put off get made, discussed with those who will have to carry them through.

Under deadline the team writes tests and refactors as on any other day, and newcomers learn those practices from their colleagues. The product’s next stage is prepared by your own people.

What stage has your product reached?

We look at the stage you are going through and the skills it demands, and at which practices the team should make its own first.

We use your data to respond to your request. Read our Privacy Policy.