更多

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.

Lessons and Tips for Using XMPP

A sports broadcasting project I worked on a year ago used XMPP as a performance optimisation and for in-game chat. We used ejabberd (on AWS EC2) for the server, Strophe.js for our web clients and Asmack for the Android client (which didn’t end up getting released.) It was an interesting experience, and I’d use that combination of tools again.

Some things we learnt:

  • You can use ejabberd in as a stateless router of messages. I’d highly recommend this: it was pretty useful to us to be able to tear down our cluster of servers and re-build without any loss of…

Blog post by Giles Alexander
7 June 2014

Original Link

What are the criteria for determining success for Test Automation?

Test Automation is often thought of as a silver bullet that will solve the Teams testing problems. As a result there is a heavy investment of time, money, people in building an Automated Suite of Tests of different types which will solve all problems.

Is that really the case? We know the theoretical aspect of what is required to make Test Automation successful for the team. I want to know from practical perspective, with the context what worked or not for you.

I am currently writing about "Building an Enterprise-class Test Automation Framework", and am gathering experience reports

Blog post by Anand Bagmar
21 April 2014

Original Link

Learning from Agile Project Management


This blogs post is in continuation to the series in which I shared my learning from Distributed Agile project. Link of the post here : goo.gl/xV9qfw

With this I am sharing my project management learning. While being on the project for around 8-9 months, I have captured different dimensions which as a project manager you would have to think of. This is just a guideline and not the exhaustive list, different project would provide different learning.

So at a high level I have portrayed the agile project manager as wearing 6 different hats.  These hats let him gain insight into

Blog post by Nishant Verma
20 April 2014

Original Link

Prospect

热战争不太可能发生。黄金这种动荡下作为通货在政府中传递的作用会越来越弱。

人类将受限与资本与智力。媒体、教育机构、企业、政府将成为两极分化的媒介。军队和政治依然存在,但博弈已经不是简单的流血,而是在看不见的意识形态中。

反资本垄断有了,但是不存在反智力垄断。智力的进入门槛越来越高,同时还有知识产权,将其变现为资本,未来是知识的天下。

如果说军事的差距、资本的差距还能用“肉眼”来衡量和感知,知识的差距甚至是无法测量的。

对此,投资也好,未雨绸缪也罢。


Blog post by Jiwei Zhu
20 April 2014

Original Link

Plan to move from Dropbox to Google Drive? Better think twice

After the huge price drop announced by Google I decided to give it a try. I have been a Dropbox user for a long time, but its prices versus my usage aren’t really compatible.

However, we only realize the pros/cons of a service after taking a closer look and comparing it to another one.

In the follow topics, I will cover some experiments/findings that I made.

Google Drive doesn’t support symlinks

At first glance, one thing that really annoyed me is the fact that Google Drive doesn’t support symlinks, i.e. it won’t upload to the cloud the content that a…

Blog post by Nicholas Pufal - CoffeeCup
19 April 2014

Original Link

do your stories tell a story?

I want to address a common anti-pattern that I see and suggest an alternative approach.  I’ve seen different styles of user stories, and though the sections differ by the needs of the team and the style of the BA/Product Owner, one common section that I see is the context (aka business context, narrative, etc).  This is usual a paragraph or two that is meant to show how the change  facilitated by the story will impact the user.  We’ll come back to that goal in a bit.

Anti-pattern:  A context that does nothing more than describe how the product will work…

Blog post by JK Werner
18 April 2014

Original Link

Retrospective activity (filtering) : Most Likes and Dislikes

cross posted on FunRetrospectives.com

This is a follow-up on the Plus Minus Voting activity. It creates a visual tool for the marked items according to its total score (from the lowest to the highest).

Running the activity
1. Create an axis as per the figure below ().->
2. Ask the participants to place the marked post-its (from the Plus Minus activity) on the axis as per their total score (e.g., 4 + and 1 – have a score of 3).
most-likes-and-dislikes
3. Discuss with the group about the items.
Note that the items with + and – on it…

Blog post by Paulo Caroli
16 April 2014

Original Link

Most Likes and Dislikes

This is a follow-up on the Plus Minus Voting activity. It creates a visual tool for the marked items according to its total score (from the lowest to the highest).

Running the activity

1. Create an axis as per the figure below ().

2. Ask the participants to place the marked post-its (from the Plus Minus activity) on the axis as per their total score (e.g., 4 + and 1 – have a score of 3).

most-likes-and-dislikes

3. Discuss with the group about the items.

Note that the items with + and – on it represent items in which…

Blog post by Paulo Caroli - Funretrospectives
16 April 2014

Original Link

APIs & Documentation – Who’s the Tail and Who’s the Dog?

API Docs: The Traditionalist View

I’ve written a lot of APIs in my time (think RESTful-type APIs, not library APIs). Often times, clients don’t have access to the code or don’t care to pore through it, so documentation is important. I’ve generally held the following to be somewhat of a maturity model for API documentation:

  1. No docs – call me and I’ll show you how to use it!
  2. Go to the wiki
  3. The docs are on a special page of the web application hosting the service. This is nice because the docs
    are versioned with the app; in fact, they…

Blog post by Brandon Hastings Byars
16 April 2014

Original Link

Leading vs. Lagging Indicators OR Futurospective vs. Retrospective Activities



Cross posted on www.caroli.org

Floyd Marinescu on his Culture and Happiness in Virtual team presentation at the QConSP 2014 conference brought a very interesting point to my attention.

Make sure to track and meet weekly to talk about your team leading and lagging indicators.

Leading indicators are metrics about the future and upcoming events. Lagging indicators are metrics collected based on the past events and happenings.

I watched his talk a little after I had given my latest talk about retrospectives. Naturally I related his points to my retrospective world.

Traditional retrospectives activities are looking at the past. Typically,

Blog post by Paulo Caroli
15 April 2014

Original Link