Latest Tweets

Latest Posts

  • Component Teams vs Feature Teams

    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. […]

Jon is a creative Agile, Business and Executive Coach with proven experience leading successful change programmes and producing award winning global products using web and mobile technology. Starting out as an Avionics Engineer in the British Army, Jon now focuses on fixing and building high performing teams (rather than helicopters), empowering organisations to deliver world-class solutions through organisational redesign, effective leadership coaching and training agile techniques to teams and individuals.





Jon holds the following certifications:

  • Scrum Alliance Certified Professional (CSP)
  • Scrum Alliance REP Trainer
  • SAFe Program Consultant® (SPC)
  • Scrum Alliance Certified ScrumMaster (CSM)
  • Scrum Alliance Certified Scrum Product Owner (CSPO)

To connect with Jon on social media, simply click on the LinkedIn button below.