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.

Hacking ThoughtWorks recruitment (Part 3 – Pairing interview)

This is the third article I’ve written on the ThoughtWorks recruitment process (for developers) and today I’m discussing what happens after a coding problem has been reviewed and both TW and candidate are keen to proceed: the pairing interview.

Ironically, there are normally three people in our pairing interviews; the candidate, a TW developer who will be a pair for the candidate, and a second TWer lurking ominously in the corner taking notes.  Why the 3rd person, I hear you ask – because it makes it easier to take notes and give feedback from a person external to…

Blog post by Andy Marks
22 July 2014

Original Link

Following up on action items

This retrospective activity is used for following up on previous retrospectives action items. Lack of accountability for action items is a common complaint about retrospectives. It is a simple and direct way to follow up on previously identified items.

Running the activity

1.   Open the list of action items (and their respective owners)

2.   Update the status for each item on the list.

3.  Add newly identified items


These are the possible status for the items on the list:

-          Closed. Completed action items

-          Added. Newly added action items to the list

-          Still pending. Things previously identified, but…

Blog post by Paulo Caroli - Funretrospectives
22 July 2014

Original Link

Part 2 of Collection Pipelines: a couple more examples

I’ve added two more examples of collection pipelines with this second installment. The first is the classic combination of map and reduce, also introducing specifying functions with names as well as lambdas. The second introduces the group-by operation and treating hashmaps as key-value pairs.

Blog post by Martin Fowler
22 July 2014

Original Link

Hacking ThoughtWorks recruitment (Part 2 – Coding Problems)

This is the second article I’ve written on the ThoughtWorks recruitment process (for developers) and today I’ll shed some light on how I approach reviewing a candidate’s submitted code problem and what that means for how candidates should approach these problems.  

It’s important to note that what follows is largely my opinion.  My opinion is considered and experienced, but it’s opinion nonetheless.  Try as we might, no two ThoughtWorkers will agree on an exact standard to which coding problems are reviewed.  We round off some of the edges of this risk by having two ThoughtWorkers review almost all our

Blog post by Andy Marks
21 July 2014

Original Link

Tópicos para uma Inception

Segue abaixo uma lista de tópicos para ajudar no planejamento de uma  inception.

Lista de tópicos para a Inception em si:

  • O que é uma inception
  • Hopes and concerns para a Inception
  • Apresentação dos resultados da Inception

Lista de tópicos para esclarecimento do escopo (Produto / MVP):

  • Apresentação do negócio
  • Visão do Produto
  • Objetivos Pincipais
  • Personas e usuários
  • Features
  • Jornada dos usuários
  • Detalhamento de Features
  • Estimativa
  • Priorização
  • Planejamento

Tópicos mais técnicos

  • Arquitetura atual
  • Requisitos náo funcionais
  • Trade offs técnicos
  • Path to Production

Tópicos mais usiness:

  • Influence vs interest – Stakeholder mapping
  • RACI matrix – Responsible, Accountable, Consulte…

Blog post by Paulo Caroli - Blog
21 July 2014

Original Link

Collection Pipelines

I’ve often come across a pattern in code where you organize some computation by passing collections through a pipeline of operations. I first came across it in Unix, did it in Smalltalk and Ruby, and find it common in functional programming. I’ve written an article to describe this pattern, and this is the first installment which contains an initial introduction and a definition of the pattern.

Blog post by Martin Fowler
21 July 2014

Original Link

Hacking ThoughtWorks recruitment (Part 1)

So apparently my employer, ThoughtWorks, has been anointed the toughest recruitment process of any technical company according to  Now this is clearly unverifiable bollocks in terms of any connection to an objective reality.  That said, it’s fair to say our recruitment process intends to be thorough and is time consuming.  The overall process might seem daunting to candidates on the starting line and staring ahead at each of the interviews as another hurdle to be cleared.

But there’s another way to look at this as well, and as an 11 year resident of this system and someone who

Blog post by Andy Marks
21 July 2014

Original Link

Livro: Métodos Ágeis para Desenvolvimento de Software

Uma honra estar com tantos amigos neste livro sobre métodos ágeis.


Segue a lista de capítulos com seus respectivos autores:

  1. O Manifesto Ágil por Alexandre Gomes, Renato Willi e Serge Rehem
  2. A História dos Métodos Ágeis no Brasil por  Alfredo Goldman, Claudia Melo, Fabio Kon, Hugo Corbucci e Viviane Santos
  3. O Framework do Scrum  por  Rafael Prikladnicki e Alexandre Magno
  4. Programação Extrema (XP) por Dairton Bassi
  5. OpenUP por José Papo
  6. FDD – Feature-Driven Development por Adail Muniz Retamal
  7. Lean por Samuel Crescêncio
  8. Kanban por Alisson Vale
  9. Modelagem Ágil  por Rodrigo Yoshima
  10. Domain-Driven Design por Felipe Rodrigues de Almeida
  11. Test-Driven Development …

Blog post by Paulo Caroli - Blog
18 July 2014

Original Link

High-Impact L&D

On my way to work today, I was scrolling through my blog roll and LinkedIn posts and came across this (as always) thoughtfully written post on It's Time to Redesign HR by Josh Bersin. He emphasizes the importance of re-thinking the role of HR and defines some of the aspects that make for a high-impact HR team. And one of the important points he raises is the need to consider HR as a talent function, moving beyond some of the typical administrative tasks that are typically seen as defining parameters of HR roles. To quote him here: “Our research

Blog post by Sahana Chattopadhyay
17 July 2014

Original Link

Sequence after a two day workshop: One Word -> FLAP

This sequence of activities worked well at the end of a two day workshop. Fourteen participants were able to share their learning and talk about what they take form it and their challenges ahead. The trainer could get lots of feedback regarding the workshop as well. It took 40 minutes.

Here is the retrospective agenda:

1. Set the context: the workshop is over. What to do with the learning?

2. Prime Directive: the Futurospective prime directive

3. Check in: one word

4. Main course: FLAP – Future direction, Lessons learned, Accomplishments and Problem areas

5. Filtering: Tell and Cluster


Blog post by Paulo Caroli - Funretrospectives
16 July 2014

Original Link