Software development & practical team learning · Glasgow
We build software with your team, so your team gets better at building it.
ImprovTeam develops software for organisations and runs hands-on working sessions that help development teams collaborate, plan and deliver with less friction. Real code, real problems, real improvement. No slides-and-certificates training.

One practice, two halves
We build software
Web applications, internal tools and the services behind them, designed and developed for organisations that need something reliable and maintainable. We work in small increments, show working software early and leave code that your people can understand.
Development workWe help teams work better
Practical working sessions for software teams on the things that slow them down: unclear priorities, painful handovers, recurring defects, estimates nobody trusts. Sessions use your own backlog and code, so the improvement is immediate rather than theoretical.
Team sessionsThe best way to learn how to build software well is to build some, well, with someone beside you.
Working sessions, not courses.
We do not run accredited courses and we do not issue certificates. What we offer is closer to a skilled colleague joining your team for a while: facilitating, pairing, asking good questions and helping the team decide how it wants to work. The measure of success is how the team works the following month, not a pass mark.
- Your backlog, not a fictional case study
- Your codebase, not a sample repository
- Your decisions, written down by the team
- Follow-up to see what stuck
Sketch a session in thirty seconds
Choose your team, its biggest challenge and a format. We will outline how a session would typically run. Adjust it with us before anything is booked.
A half-day, roughly
An outline of a typical working session. Every session is planned with the team lead beforehand.
- Start
Framing
What is hurting, what has been tried, what a better month would look like. Ten minutes, everyone speaks.
- Next
Look at real work
Walk a recent piece of work from idea to release. Where did it wait? Where did it bounce back? Mapped together on the wall.
- Middle
Try something
Pair or mob on a live backlog item using a changed practice: smaller slices, clearer acceptance, a test written first, whatever the team chose.
- Late
Reflect
What felt better, what felt awkward, what the team will keep doing next week.
- End
Agreements
Two or three working agreements written by the team, plus a date for a short check-in.

Build alongside
For teams who want both outcomes at once, we join for a defined period to build a real piece of software with them. Our developers pair with yours, practices are introduced in the course of the work, and when we step away the team owns the code and the habits that produced it.
This suits organisations bringing development in-house, teams adopting a new technology, or groups that have grown quickly and lost their rhythm.
How build-alongside worksWhere teams usually start
"Everything is urgent"
The team is busy all the time yet little seems to finish. Usually there is too much work in progress and priorities change mid-stream. We start by making the work visible and agreeing what to stop starting.
"The same bugs come back"
Fixes are made quickly under pressure and the cause stays put. We trace a handful of recent defects back to where they could have been caught, then practise the habit that would have caught them.
"We inherited this code"
An agency or departed colleague left a system nobody fully understands. We pair on safe, small changes with tests around them, building confidence and knowledge at the same time.
"We are growing fast"
New people arrive faster than habits can spread. We help the team write down how it works and make the first fortnight for newcomers productive rather than bewildering.
The software side, in more detail
Not every client wants sessions. Many simply need a web application, internal tool or integration built carefully. We take those projects on in their own right: discovery, a staged plan with honest estimate ranges, development in short increments with working software shown regularly, then a calm launch.
Because we spend so much time inside other teams, we are particular about leaving software that is easy to pick up. Readable code, tests around the parts that matter, a short maintenance guide and a walkthrough with whoever takes over. If your own developers will own it, we invite them in from the first week so that handover is a formality rather than an event.
Read about developmentWhat teams take away
Working agreements the team wrote and believes in.
Changed habits practised on real work, not imagined.
Better software where we built or refactored alongside.
A short write-up of what was tried and decided.
A check-in a few weeks later to see what stuck.
Honest observations for the team lead, shared with the team's knowledge.
What we ask of you
- A team lead who wants this and will protect the time
- The whole team in the room (or the call), not representatives
- Access to real backlog items and, for build work, the codebase
- Permission for the team to change how it works
Boundaries
We are not an HR consultancy and do not assess individual performance. Observations are about how the team works, never reports on named people. We do not offer accredited qualifications. For software we build, support runs Monday to Friday, 09:00 to 18:00 UK time.
Quick answers
Do you work remotely or in person?
Both. Build work is usually remote. Working sessions are often better in person; we travel within the UK, and remote sessions work well with the right tools.
What size of team do you work with?
Typically between three and twelve people. Larger groups are split into several sessions so that everyone takes part.
Can you just build the software without the sessions?
Yes. Development is a service in its own right. We will simply make sure handover leaves your people able to maintain it.
Do attendees get a certificate?
No. Our sessions are practical working sessions, not accredited training, and we do not issue certificates.
How soon could a first session happen?
Usually within a few weeks of a first conversation. We need a planning call with the team lead beforehand, and enough notice for the whole team to clear the time. Rushing that part rarely helps.
What happens after a session?
You receive a short write-up of what the team tried and agreed, and we hold a brief check-in a few weeks later to see which changes stuck and which need another look.
Tell us about the team and the work.
We reply within two working days, Monday to Friday.