Component Teams vs Feature Teams
27 Feb 2018
There’s nearly always too much work. Certainly there is often too much work for one team. Considering the optimum team size (in Scrum) is between 5 and 9 people, it doesn’t take much of a backlog to require us to have multiple teams. When this is the case, it introduces the problem of how to divide the work up between the teams. The two most common ways I’ve seen teams organised are as Component Teams and Feature Teams – but which is the best way of organising your company? This is an area that is often debated. They are contrasting approaches to software delivery and I’ve heard many arguments in favour of each. Let’s have look at them. Component Teams Component Teams are considered to be made up of experts that specialise in a specific domain and they are focused only on the knowledge and technology related to their domain. It ’stands to reason’ that if there is an area of complexity needing work performed on it on a regular basis, we should have a team dedicated to it. Common examples are the user interface (UI) or the database (DB), we may well have a team for each of those. […]
The term Agile originates from the Agile Manifesto of 2001, but the first Agile approaches emerged in the 1990s with Scrum and eXtreme Programming (XP). The agil8 approach brings expertise built over 20 years with these early Agile methods right through to the latest developments such as Lean Kanban.
The agil8 approach is to help you select, tailor, define and implement the best Lean and Agile approach for your own particular circumstances. What is right for one organisation or project is not necessarily right for another. Whilst many of the challenges that different organisations face in implementing Agile are often the same, the solutions to those challenges are, like the organisations themselves, always unique. Moreover, organisations and circumstances change so what is the best solution today is unlikely to be the best solution tomorrow. Above all else, the agil8 approach emphasises the important of continuous evolutionary improvement.
This kind of expertise only comes with years of experience. Lean and Agile is fine in theory, but without a deep practical understanding of the different approaches and how to make them work in the real world their potential is very difficult to realise.
The agil8 enablement approach can be applied at any scale from the individual team, departmental or enterprise level. It covers everything that you need to make your transition to Lean and Agile effective and successful including Initiation, Training and Education, Coaching, Reviews and Retrospectives, and Transformation Management.
Scrum is the most popular agile method by far, and is usually at the heart of the approach adopted by agil8 clients. However, Scrum’s apparent simplicity raises challenges when attempting to map it onto a complex organisation, so the agil8 approach involves applying Scrum in the best possible way for each unique circumstance.