×

Contact with Primitivo Cachero Viejo

Contact

Nombre

Correo electrónico *

Mensaje *

Menu
  • CONSULTING
    • Organisational Agility
      • ES
      • EN
    • Kanban Coaching, KMM, F4P, ESP, FLSA
    • Lean, Kaizen, Toyota-Kata, Hoshin
    • Leadership, Culture, Identity, Purpose
    • Antifragile and Resilient Organizations
  • COACHING
    • Business Coaching
    • Personal Coaching
    • Agile Coaching
    • TESTA Method Coaching
  • ABOUT ME
    • ES
    • EN

Organisational Flow

Buscar este blog

  • septiembre 2020 (1)
  • agosto 2020 (7)
  • julio 2020 (12)
  • junio 2020 (2)
  • mayo 2020 (2)
  • julio 2019 (3)
  • febrero 2019 (1)
  • septiembre 2018 (3)
  • julio 2018 (8)
  • junio 2018 (2)
  • mayo 2018 (2)
  • diciembre 2017 (1)
  • enero 2017 (3)
  • noviembre 2016 (1)
  • octubre 2016 (1)
  • septiembre 2016 (1)
  • agosto 2016 (2)
  • abril 2016 (2)
  • julio 2015 (4)
  • diciembre 2014 (2)
  • agosto 2014 (2)
  • mayo 2013 (1)
  • febrero 2012 (2)
  • octubre 2011 (1)

Follow by Email

Denunciar uso inadecuado

Páginas

  • Página principal

Las habilidades adaptativas a través de las lecciones de "El principito"

Las llamadas habilidades blandas o soft skills son habilidades sociales, habilidades de comunicación, personalidad, actitudes y atributos pr...

07 noviembre 2016

The size of the scrum teams

  lunes, noviembre 07, 2016 Primitivo Cachero Viejo   No comments


Much has been read and spoken about the size of the teams in Scrum, Agile, etc. We know perfectly well, by way of introduction and overview, a Scrum team should be multidisciplinary, by definition. That is, all the necessary roles included in the kit, to make a valid Product increase at the end of each Sprint. Until there all right. That is the best team Scrum to be productive and autonomous. That is the starting point for all Scrum team.


Scrum guide says, that the optimal team size is around 7 plus / minus 2 people. In short, the equipment should be between 5 and 9 people. cases teams of 3-4 people can be perfect. Later in the article we see that brings that size. But what is clear is that ever a team has to have more than 9 members. Why?


Already in 1983, Ikujiro Nonaka and Hirotaka Takeuchi such statements formulated after conducting research and new products in technology companies such as Juji-Xerox, Canon, Honda, Epson, Brother, 3M, Hewllet-Packard. In these studies, and later by Jeff Sutherland and Ken Schwaber to create Scrum come to affirm and demonstrate that those teams set up around 7 plus / minus 2 members generate a level of average productivity of a 300-400% more than a team normal 500% if you get to develop a great team or elite team.


A small team, 3-4 people does not make much interference, can be very autonomous with guidelines and a well-defined focus, being physically in the same space, work is consistent, responsible, aligned, without "trodden", well targeted and with fluid communication. Everything is easy with few individuals in the team. The problem appears to increase the number of team members.


Brooks's Law states that "adding personnel to a software project that is delayed delay it even further." It could even estimate what amount or percentage gets delay the project, but it is clear that delays, no more. You have to train that person on the product or technology, and will have to learn a non-technical knowledge, if no longer functional, and tactician on the product or software.


According to major studies by great personalities like Lawrence Putnam, a small team (under 9 persons), it requires 25% less effort than large to make the same product (between 9 and 15 people) one, which affects between 15-20% of productivity per team member, if we calculate a simple average we subtract 150-200% productivity on the computer.


In short, if an optimal equipment we can get to have a 300-400% productivity. And for whatever reason we add more people (surpassing the border of the 9 members) get remainder productivity 150-200%. 300-400% - 150-200% = same maximum productivity with a team of 9 or fewer members. And maximum productivity is said, indicating that a rule will be less productive, your product will be more expensive (more members of more cost equipment) and will be extended over time to be less productive.


Finally, not to elaborate any further and conclude in 1956 George Miller claimed and demonstrated that the maximum number of relationships and items that a person can hold in your short-term memory is 7. Later in 2001, Nelson Cowan, showed that Miller was wrong and had been very ambitious, he showed that it was only 4. with this statement it is clear that between 4 and 7 have good results, whatever is trying to go beyond, we are impacting team productivity, and therefore costs and deadlines.


Thus, it is now very topical a term called "Descale" or what is the same de-escalate. If we apply the same principles, studies, metrics that have been listed in the rest of the article, we obtain a scale of 4-5 teams teams of 7-9 people maximum we would be making a product perhaps 200-300% more Scrum productivity without realizing it. This can give us an average of a line of development for a product of 50 people, not 150 or 200 people. That certainly would have at most the same productivity as well scaled with Scrum teams and maximum 50 members.


Enviar por correo electrónicoEscribe un blogCompartir con TwitterCompartir con FacebookCompartir en Pinterest
  • Share This:  
  •  Facebook
  •  Twitter
  •  Google+
  •  Stumble
  •  Digg
Entrada más reciente Entrada antigua Inicio
Related Posts Widget

No hay comentarios:

Publicar un comentario

Nota: solo los miembros de este blog pueden publicar comentarios.

Entrada más reciente Entrada antigua Inicio
  • Popular
  • Video
  • Category

Popular Posts

  • Somos habilitadores de la emergencia en las organizaciones
    Aunque el fenómeno de la emergencia en las organizaciones no puede ser ni precedido ni controlado, sí puede ser facilitado dentro de cier...
  • Delegation Poker
    I discovered this dynamic a long time ago, as Jurgen Appelo says: "delegation is not easy. Managers often fear a loss of control when...
  • What makes out a great team?
    This question has been going on for a while, specially since the digital transformation brought the awareness into the enterprises t...
  • rewards and merit money for the whole
    When I talk in my courses about rewards, I always like to recall a support request I received from a Spanish customer. This software ...
  • evolution and happiness of management
    This dynamic arose from the attempt to create sources of empathy based on the work experience of the members of the company. When i learne...
  • Happy motivators
    A long time ago, we conducted a retrospective of clients based on the Moving Motivators cards (More info at : https://management30.com/pract...
  • Are you prepared to implement the Obeya Room in your company?
    The maturation process of digital transformations, or agile transformations, is being significant. There comes a point where the approach to...
  • learning agility as a basis for a new more humane leadership and antifragile
    It is clear that in the world we live in, a fixed mentality does not bring many advantages. Every leader has to embrace change in the presen...
  • El coste de los proyectos Agile
    Con motivo de la última CAS (Conferencia Agile Spain) 2016 celebrada en diciembre en Vitoria, en los corrillos apareció un tema interesante ...
  • La holocracia sin filosofía no es holocracia
    En los últimos años estamos escuchando el término Holocracia en muchas empresas, que por una u otra razón implantan este modelo en su estruc...

Video Of Day

Popular Posts

  • Somos habilitadores de la emergencia en las organizaciones
    Aunque el fenómeno de la emergencia en las organizaciones no puede ser ni precedido ni controlado, sí puede ser facilitado dentro de cier...
  • Delegation Poker
    I discovered this dynamic a long time ago, as Jurgen Appelo says: "delegation is not easy. Managers often fear a loss of control when...
  • What makes out a great team?
    This question has been going on for a while, specially since the digital transformation brought the awareness into the enterprises t...
  • rewards and merit money for the whole
    When I talk in my courses about rewards, I always like to recall a support request I received from a Spanish customer. This software ...
  • evolution and happiness of management
    This dynamic arose from the attempt to create sources of empathy based on the work experience of the members of the company. When i learne...
  • Happy motivators
    A long time ago, we conducted a retrospective of clients based on the Moving Motivators cards (More info at : https://management30.com/pract...
  • Are you prepared to implement the Obeya Room in your company?
    The maturation process of digital transformations, or agile transformations, is being significant. There comes a point where the approach to...
  • learning agility as a basis for a new more humane leadership and antifragile
    It is clear that in the world we live in, a fixed mentality does not bring many advantages. Every leader has to embrace change in the presen...
  • El coste de los proyectos Agile
    Con motivo de la última CAS (Conferencia Agile Spain) 2016 celebrada en diciembre en Vitoria, en los corrillos apareció un tema interesante ...
  • La holocracia sin filosofía no es holocracia
    En los últimos años estamos escuchando el término Holocracia en muchas empresas, que por una u otra razón implantan este modelo en su estruc...

Blog Archive

  • ►  2020 (24)
    • ►  septiembre (1)
    • ►  agosto (7)
    • ►  julio (12)
    • ►  junio (2)
    • ►  mayo (2)
  • ►  2019 (4)
    • ►  julio (3)
    • ►  febrero (1)
  • ►  2018 (15)
    • ►  septiembre (3)
    • ►  julio (8)
    • ►  junio (2)
    • ►  mayo (2)
  • ►  2017 (4)
    • ►  diciembre (1)
    • ►  enero (3)
  • ▼  2016 (7)
    • ▼  noviembre (1)
      • The size of the scrum teams
    • ►  octubre (1)
    • ►  septiembre (1)
    • ►  agosto (2)
    • ►  abril (2)
  • ►  2015 (4)
    • ►  julio (4)
  • ►  2014 (4)
    • ►  diciembre (2)
    • ►  agosto (2)
  • ►  2013 (1)
    • ►  mayo (1)
  • ►  2012 (2)
    • ►  febrero (2)
  • ►  2011 (1)
    • ►  octubre (1)

Followers

Top Sites

  • ShiftUp
  • The flow system
  • Management 3.0

Contact Today!


primitivo@cacheroviejo.com
Copyright © Organisational Flow | Design by Primitivo Cachero Viejo
Con la tecnología de Blogger.