Home / Project Management Advice / Agile Team Structure – 4 Options For Your Project Team

Agile Team Structure – 4 Options For Your Project Team

Agile project management has taken the IT world by storm, and is reported to be saving some companies around 25 per cent on their production costs as a result. Slowly, the agile mentality is making its way into other areas too, as companies outside of the IT industry start to recognise the benefits of working in a more flexible, changeable way.

If you are in the process of putting together an agile project team, you have the ability to choose a number of models in terms of the structure and focus of your team. Here are four of the most popular team structures in use today that you could adopt depending on the needs of your project.

1.      A generalist team

The generalist team offers great flexibility because any team member can pick up any task at any time. If your team is made up of people who have a broad range of skills and can work in diverse roles, this could be a great choice for you. Generalist project teams will need to understand the project clearly from the start and be able to see things from different viewpoints throughout. The approach is hard to implement with large teams, however, and works best in small businesses where everyone is passionate and multi-talented.

2.      A specialist team

The specialist team is made up of people who are experts in their own discipline. It is completely to opposite of the generalist team where everyone can do a bit of everything, and instead focusses on getting the very best people for each part of the job to work together on the project delivery. The upside is that you have the potential to develop a very good project, what with so many specialists working on their own elements of the job. The downside is that you might end up with some people overloaded and missing their sprint targets, whilst others twiddle their thumbs with nothing to do.

3.      A relay team

For companies that are trying to move away from the waterfall methodology and are in the process of transitioning to scrum, this type of team is a common marker. Working as a tag team, the team members work for a sprint on particular discipline and then everything grinds to a halt whilst they fold back and wait for the next discipline to start. This is good for a team that are not ready to embrace the agile philosophy entirely, but in the long run will only make deadlines harder to achieve.

4.      Team handoff

Once the scrum is in use across the whole organisation, a handoff team can work really well. In this model, the work is handed off from one team to another over the course of the project, letting the best people take care of different aspects of the final deliverables as time goes on. For example, a product may be designed by one team, built by another and then installed by a third. This only works when the entire organisation is working in an agile way and is comfortable with this type of mentality.

About M Symonds

The author is a freelance consultant specialising in digital marketing. She has many years experience in IT and IT Project Management in the oil industry and investment banking on complex global projects and managing outsourced project teams.

Check Also

PM Tagging

3 Prime Reasons You Need Tagging in a Project Management Tool

Every project manager’s job is to initiate, plan, monitor, execute and complete every single project …