Lessons learned forming a new development team in the public sector


Posted on January 6th, by admin in Blog. Comments Off on Lessons learned forming a new development team in the public sector

Don’t worry, if on day 1 your team has no kit, no desks to sit at, or software to use. In fact, don’t worry if on day 5 your team still has no kit, permanent location or software, because this will stop them falling into their default position of being glued to a screen, and avoiding eye contact with the strangers that now form their team.

When we started back in early December 2016, we had no kit for almost two weeks. Starting in a job without ID badges, access to the network, or dedicated work stations, left us with very little to distract is from having to talk to each other. And this precious commodity proved to be very welcome – it meant we had chance to get to know each other; our backgrounds, who was quiet, who was the joker, who understood what we were about to embark on, and who didn’t.

Having to be chaperoned everywhere – through the gate in the morning, to the canteen and back, or anytime we needed to leave the building became an almost surreal flashback to school days when I recall being taken on trips and accompanied everywhere by a teacher. However, it really reinforced the idea that we are a group, a collection of like minds – a team.

As the days moved on and we slowly started to gain some independence, with ID badges and Smart cards to access the computer network in the second week, and finally, some laptops towards the end of that week, we had a shared sense of having gone through some strange, enforced induction and it was a great ice breaker for us to get to know a little bit more about each other and for me, as Scrum Master, to see how everyone reacted to the removal of the technology we all took for granted in previous roles.

It was interesting to see how the team worked around these obstacles and did their level best to make good use of the time. Meetings were readily attended, questions eagerly answered, and sketched out solutions to problems that were not even in our remit were offered up in an attempt for individuals to start feeling useful. Prototype work was kicked off on individuals’ laptops and everyone was tasked with the mission to learn the technologies we had agreed to push forward with. Even over the Christmas period, tasks were delegated and those not taking advantage of the holiday worked enthusiastically on their tasks.

One month on from the day we started, we finally have a permanent home, a dedicated meeting room, and joy of joys, a dedicated wi-fi connection, all many things we would usually take for granted. We still await our final kit and software, but are doing our best to work around the limitations of the temporary kit, and this experience has given me some insight into how the team works at an individual level when the odds are stacked against them – which is remarkably well I must add.

It may be simple coincidence – another group of personalities may not have got off to such a good start – but I really think the disadvantages we faced in the first two weeks did us a favour, and set the tone for some good communications which we can take forward into everything we do.





Comments are closed.

Latest from the blog
Practice makes perfect

Looking back to the start of the year, when my current team were green and in an unquestionable forming stage, it’s clear that the...

Summertime Blues

No matter how much we try and plan our projects around holidays, and allow for the fact personnel will be off for long periods...

Navigating the politics of technology

The unfortunate consequence of being a new contractor working alongside respected and experienced incumbents is that there is a natural inclination to be deferential...