Show mobile menu

Blogs

Lots of our people have lots of opinions. Here are just a few of them

ThoughtWorks embraces the individuality of the people in the organization and hence the opinions expressed in the blogs may contradict each other and also may not represent the opinions of ThoughtWorks.

KALM - Keep, Add, More, Less


KALM (Keep, Add, More, less) is a retrospective activity that fosters the conversation to the current activities and the perceived value. It helps team members to understand each other perceived value on such practices.
 
The KALM (Keep, Add, More, less) divides the board into 4 areas:
  • Keep – something the team is doing well and you recognize the value on it.
  • Less – something already being done; but you rather do less of it.
  • More– something already being done; and you believe will bring more value if done even more.
  • Add – a new idea, or something you…

Blog post by Paulo Caroli- Agileretroactivities
17 May 2013

Original Link

General Behavior activity



The General behavior activity fosters a team conversation about behavior. It is specially useful when forming new teams. The results of this activity serve as an ongoing guide for acceptable and unacceptable team behavior.

Running the activity:

1.      Separate the canvas in two separate areas with the following titles

  • Wonderful behavior
  • Unacceptable behavior

2.   Ask the participants to write on post-its (and place at the canvas) examples of wonderful behavior and unacceptable behavior.
3.      Group conversation about the notes.

Please find below a sample result after runnign this activity.



 

Blog post by Paulo Caroli- Agileretroactivities
14 May 2013

Original Link

Ground rules

This activity helps with team formation. It is specially useful for –collectively—deciding and writing down the team ground rules.

Discussing ground rules after problems arise is much more difficult. Ground rules should focus on these elements:
  • Process  – How the activities will be carried out.
  •  Norms  – Ways in which team members will interact with each other.

Running the activity:

1.                  Create the empty canvas with the ground rules elements (in my case: Ground rules / Process and Ground rules / Norms).
2.                  Ask participants to write down the rules they are really strong about…

Blog post by Paulo Caroli- Agileretroactivities
13 May 2013

Original Link

Opinion on Music

Simply put, this is my list of favorite albums all times.

  • Sargent Peppers Lonely Hearts Club Band (The Beatles)
  • White Album (The Beatles)
  • Abbey Road (The Beatles)
  • Revolver (The Beatles)
  • Magical Mistery Tour (The Beatles)
  • Let It Bleed (Rolling Stones)
  • Sticky Fingers (Rolling Stones)
  • Are You Experienced (Jimi Hendrix)
  • The Velvet Underground & Nico (Velvet Underground)
  • Led Zeppelin IV (Led Zeppelin)
  • The Dark Side Of The Moon (Pink Floyd)
  • The Wall (Pink Floyd)
  • Machine Head (Deep Purple)
  • A Night At The Opera (Queen)
  • The Who…

Blog post by Vincius Gomes
13 May 2013

Original Link

That Guy & This Guy



That Guy & This Guy is a team building activity that foster the conversation on being a  team player. The results of this activity serve as an ongoing guide for acceptable and unacceptable team behavior.

Running the activity

1.       Separate the canvas in two separate areas with the following sentences (drawing is very welcome)

  • Don’t be “that guy”
  • “This guy” rocks!

2.       Ask the participants to write notes on this and  that guy


 “That Guy” is a non-team player..This Guy” is the ultimate team player. Everyone wants “this guy” on their team! Please…

Blog post by Paulo Caroli- Agileretroactivities
10 May 2013

Original Link

fire prevention and firefighting




Moving around large Agile projects, I came across a common situation that hinders the team performance.  Individuals cannot allocate time for improving their work (and avoid future problems) because they are constantly firefighting current issues.

It typically happens like this: Someday on the past, the problem has started. Unfortunately, the issue (small at the time) was not clearly identified. It only got enough attention when it was on fire. Therefore the vicious cycle:


Everyone is busy putting out fires -> no time to improve (and avoid future fires) -> more fires


It takes discipline! Finding the balance between fire…

Blog post by Paulo Caroli
1 April 2013

Original Link

What am I managing?



When I first started PMing I used to manage people working.
A few years went by. I changed.
I realized I should manage the work and enable people.
More years went by. I changed again.
Today I came to the realization I should manage people expectation and enable the work.
I wonder what will be my realization in another few years.

Blog post by Paulo Caroli
15 March 2013

Original Link

Treinamentos deste mês! #Agile, #Tempo e #LeanStartup

Estou me organizando para fazer pelo menos 3 workshops por mês. Serão sempre workshops de 3-4 horas de duração. Eventualmente um workshop com duração maior, 8 horas. Fora quando estiver apoiando na formação de metodologias ágeis da TargetTrust.

É a minha forma de seguir praticando, ensinando e trocando ideias com o pessoal que quer melhorar. Todos queremos! Estes workshops me ajudam e me dão ritmo para escrever, para pensar em coisas diferentes, e evoluir como profissional. Vivendo o meu propósito. E se der para bancar os custos de sala e coffee break e um valor…

Blog post by Daniel Wildt
14 March 2013

Original Link

Dia 19 e 20 tem evento do GUMA-RS + TecnoTalks!

Uma série de dinâmicas para você aprender mais sobre metodologias ágeis e boas práticas de programação.

No dia 20 (dia 2) estarei colaborando com o evento, com uma eXtreme Hour.

O evento vai começar com um pequeno tutorial sobre eXtreme Programming e depois faremos a dinâmica.

É uma hora bem intensa trabalhando nela.
E depois fazemos um fechamento, uma retrospectiva.
Aproveite a faça a sua inscrição!

Tagged: agile, event, extreme hour, extreme programming

Blog post by Daniel Wildt
13 March 2013

Original Link

Lessons learned quadrants (planning vs success)

This activity is great for seeking lessons learned after a big event.

Setting up the activity:

  • Describe the context
  • Decide upon post it colors (each color should cover a given category/area)
  • Draw the following on the canvas
Running the activity:

Please share your notes for the given context.

Following the color code, create your notes and place them accordingly:

The bigger the success, the higher you should place your note (failures goes to the lower part of the canvas).

If you consider your note is about something highly planned, then place it on the very left; otherwise you should place…

Blog post by Paulo Caroli- Agileretroactivities
6 March 2013

Original Link