Timing:

15 minutes

Ingredients:

  • Copies of the twelve principles of agile software (http://agilemanifesto.org/principles.html)
  • White-boards and/or flip-charts
  • Markers

Recipe:
This is an exercise that we came up with to better communicate the twelve principles behind the Agile Manifesto. In their existing form, it is challenging for people to read and understand each principle and, just as importantly, to easily refer to them later.

  • Divide participants in to groups, each with a white-board or flip-chart and markers.
  • Have the teams write down the numbers 1 through 12.
  • Challenge each team to, within a 15 minute time-box, come up with three words maximum that effectively capture each of the twelve principles.
  • To avoid ‘analysis paralysis’, make sure to give the teams time updates throughout (e.g. 10, 5, 2, 1 minute warnings). You will find that teams will speed up towards the end.
  • When time is up, go through each principle and discuss which are the most important words. Sometimes I like to ask people what their most and least favorite principles are.
  • Post the condensed principles somewhere visible, so as to make it a regular talking point.

Here is an example:

  1. Produce Value Early
  2. Welcome Change
  3. Iterative Delivery
  4. Daily Business Collaboration
  5. Trust Motivated Team
  6. Face to Face
  7. Working Software
  8. Sustainable Pace
  9. Technical Excellence
  10. K.I.S.S.
  11. Self-Organize
  12. Reflect and Adjust

Learning Points:

  • This is an effective way of capturing each principle in a much more concise and memorable way.
  • Probably the most valuable part of this exercise, is in the discussion that the teams have when trying to come up with the words. They need to first understand the principle before breaking it down.
  • Teams can establish a collective understanding and ownership of each principle.
  • This also makes for a good review exercise in a classroom environment.

Tempo:
15 minutos
Materiais:

  • Cópias dos doze princípios do software Agile (http://agilemanifesto.org/principles.html)
  • Quadros brancos e/ou flip-charts
  • Marcadores

Receita:
Esse é um exercício que criamos para melhor comunicar os doze princípios por trás do Manifesto Ágil. Da forma como estão escritos, é um desafio para as pessoas lerem e entenderem cada princípio e, tão importante, de serem capazes de se referirem a eles mais tarde.

  • Divida os participantes em grupo, cada um com um quadro branco ou flip-chart e marcadores.
  • Faça os times escreverem os números de 1 a 12.
  • Dentro de um período de 15 minutos, desafie cada time a criar no máximo três palavras que efetivamente capturem cada um dos doze princípios.
  • Para evitar a ‘paralisia da análise’, certifique-se de avisar frequentemente a cada time sobre o tempo (por exemplo, avisos a 10, 5, 2, 1 minuto do final). Você verá que os times aumentarão de velocidade à medida que se aproximam do final.
  • Quando o tempo acabar, passe por cada princípio e discuta quais são as palavras mais importantes. Às vezes gosto de perguntar às pessoas quais princípios são seus mais e menos favoritos.
  • Coloque os princípios condensados em algum lugar visível, de forma a transformá-lo em um ponto de conversa regular.

Segue um exemplo:

  1. Produzir valor mais cedo.
  2. Dar boas-vindas à mudança.
  3. Entrega iterativa.
  4. Colaboração diária de negócios.
  5. Acreditar em um time motivado.
  6. Face a face.
  7. Software funcional.
  8. Passo sustentável.
  9. Excelência técnica.
  10. K.I.S.S.
  11. Auto-organizar.
  12. Refletir e ajustar.

Pontos de aprendizado:

  • Essa é uma forma efetiva de capturar cada princípio de forma bem mais concisa e fácil de lembrar.
  • Provavelmente a parte mais valorosa desse exercício é a discussão que os times devem ter durante a criação das palavras. Eles precisam primeiro entender os princípios antes de desmembrá-los.
  • Os times podem estabelecer um sentimento de entendimento e propriedade coletivos de cada princípio.
  • Também pode ser um bom exercício de revisão em um ambiente de sala de aula.

    Duración: 15 minutos
    Ingredientes:

    • Copias de los doce principios de software ágil (http://agilemanifesto.org/principles.html)
    • Tableros y/o Pizarras
    • Marcadores

    Receta:
    Este es un ejercicio que nos acerca a una mejor comunicación de los doce principios detrás del Manifiesto Ágil. En su forma actual, es difícil entender cada uno de ellos con sólo leerlos; e igualmente importante, referirse fácilmente a estos posteriormente.

    • Divida a los participantes en grupos, cada uno con un tablero o pizarra y marcadores.
    • Pida a los equipos que anoten los números del 1 al 12.
    • Solicite a cada equipo que, dentro de un tiempo de 15 minutos (time-box), con tres palabras como máximo definan de forma efectiva cada uno de los doce principios.
    • Para evitar una “parálisis de análisis”, asegúrese de notificar el tiempo restante cada tanto (por ejemplo, advertencias de 10, 5, 2, 1 minutos). Usted notará que los equipos aceleran la marcha cuando se va acercando el final.
    • Cuando el tiempo esté cumplido, discuta para cada uno de los principios cuales son las palabras más importantes. A veces me gusta preguntar a la gente cuáles son sus principios favoritos y cuáles no.
    • Publicar los principios condensados en alguna parte visible, a fin de que sean un tema regular de conversación.

    Aquí está un ejemplo:

    1. Producir valor Temprano
    2. Bienvenido el cambio
    3. Entrega Iterativa
    4. Colaboración diaria [con el] negocio.
    5. Equipo Confiado [y] motivado.
    6. Cara a cara
    7. Software funcional
    8. Paz Sostenible
    9. Excelencia Técnica
    10. KISS (keep it Simple, Stu…) [Mantenerlo Simple]
    11. Auto-Organización
    12. Reflexionar y Ajustar

    Puntos de aprendizaje:

    • Esta es una forma efectiva de captar cada uno de los principios de una manera mucho más concisa y memorable.
    • Probablemente la parte más valiosa de este ejercicio, es la discusión que los equipos tienen cuando tratan de encontrar las palabras. Tienen que entender primero el principio, antes de descomponerlo.
    • Los equipos pueden establecer una comprensión colectiva y propiedad sobre cada uno de los principios.
    • Esto también lo convierte en un buen ejercicio de revisión en un ambiente de aula.

      10 thoughts on “Pocket-sized PrinciplesPrincípio de BolsoPrincipios de Bolsillo

      1. Also, I have that trying to consolidate the outputs from each group has not yielded much value as it might descend into who framed it better and who “got it wrong”. The awareness will come from the dialog.

      2. I just helped facilitate this session with other agile leaders as a tool to take back to their teams. We had some interesting discussions and I drew some insights that might be helpful to others.

        Introducing the exercise
        ========================
        Some people have a bad taste in their mouths from Agile did poorly and they may have negative reactions to anything “agile”. One way to deal with this would to acknowledge it up front. Then you can say that perhaps the negative experiences could
        be due to introducing practices which which were not aligned with the principles.

        So, it might be valuable to go back to the original principles and that is what we are going to do now.

        I think it would be valuable to make clear that this is a historical document. We may agree or disagree with the
        principles and that is fine. This is not an “agile checklist” to see how well you understand or enact these
        principles. Rather, it is to gain a deeper understanding of these principles and how they might help us.

        Some Debrief Ideas
        ===============

        Which principle do you most resonate with and why?

        Which principle to you not agree with and why?

        Which principle would the hardest to put in place and why?

        Perhaps a fist-to-five activity where you could gauge which ones the team most aligns with?
        You could then use those principles as a starting point for a team working agreement.

        1. I always ask to explain with an example of the principle in action in the participants’ environment or bring up examples that are relevant for the audience.

          As debrief questions, I usually add:
          – What would you do when an action follows most of the principles, but not all?
          – And related to specific principles, like the one about f2f communication. Does this mean one can’t apply agile when working in a distributed environment?

      3. Recently did this but extended by requesting the teams come up with a bulleted list for each principle which describe Scrum Artefacts, Scrum Events, our Day-to-Day practices etc. that demonstrate the practice of that principle. This way our teams can see how the Scrum Events for example are related to the Agile Manifesto Principles.

        Worked well, although never gave enough time for the exercise and make the mistake of breaking the teams into groups of four which resulted in two rounds of consolidation when one would have been enough.

      4. I too use this exercise when teaching the Scrum course: it’s a smooth way to help participants internalize the Agile principles.

      5. This is one of the must have in my teaching session for scrum courses.
        I plan 20 more minutes for the debrief and the “condensed” version of the different teams.

      6. I have used this game three times and I have found it to be very effective.

        One challenge I find with it is consolidating the output from the multiple groups into a single list. I like having a single list as it is a simple, clear, artifact that can be left on the team wall.

        What I have found works well it to create another list with the 12 numbers on it. Then I got a volunteer scribe, usually asking the person who had the neatest writing from the original groups. Then I gather the team around and have them come up with a ‘final’ pocket-sized principle. Usually, an informal dialog was sufficient for someone to suggest something and for the team to agree. Sometimes, I make suggestions and have used the decider protocol if things are moving too slowly.

        This additional discussion provides another opportunity for the team to talk about the principle which is the most useful part. However, this add another 15 minutes or so for the activity.

      7. Parabens!

        Achei muito interessante e prático não só este post, mas todo site|blog!!

        Fico contente em descobri um site assim que facilita e agiliza a nossa assimilassão do Agil. ;-))

      Comments are closed.