In May 2014 it will be two years since I joined ThoughtWorks Germany. The time here has been an amazing journey. I have learned many things.
I learned more about agile software development and I worked with interesting technologies. I am also dealing with clients and represent my company at a client site. I did learn of all that – and I don’t expect to stop learning anytime soon.
But there were a few things I learned, which I did not expect to learn at ThoughtWorks. I want to share three of them with you.
I am currently working on an application which has needs to work offline. This has the beneficial side effect, we use the different HTML5 storage capabilities. One of the is the File API, which we are using to store images locally – before queuing them for upload to a backend server.
In this article, I will share some code how we did this. The example works in Google Chrome – for DOM manipulation I will use JQuery.
Have you ever had a retrospective where you didn’t define actions to be executed and checked up on in the next retrospective? I did.
I facilitated a retrospective using the Lean Coffee exercise. This helped to generate some good discussion, but in the end there was no action item. Is that a bad thing?
When the safety check returns a low result (e.g. lots of 2s and 3s) there are ways to react in a retrospective. But how can you deal with low safety in a team outside the retrospective, e.g. in stand-ups or estimation meetings?
The write a letter to yourself exercise is an exercise to create continuity between two personal retrospectives. You write a letter – addressed to yourself – where you summarise what you learned and decided in this personal retrospective.
Then you put the letter in an envelope and close it. At the beginning of the next retrospective you open the envelope and read the letter. Thereby you can bridge two personal retrospectives together.