This article is about the Scrum Retrospective Three Little Pigs and my personal experience with it. How to and the extra benefits of this retrospective. The goal I had with the retrospective, was to look back at the past sprint, but also to talk about what goes well (bricks); what goes well most of the time, but needs improvement to get impediments out of the way on structural basis (sticks); or what subject needs further improvement (straw).
On several projects I’ve seen that a test and development environment needs a email server. Most of the times it’s not wanted that the emails are really send out. So I started a search...
The Unit of Work design pattern solves the problem, that other components / layers in your software then the persistency layer needs to keep track on which data needs to be inserted, updated or deleted. Also this pattern makes sure that all the data is saved within one transaction.
Nowadays in the world of software engineering the problems are getting more complex. Luckily for us there are proven solutions for parts we need to solve. These proven solutions we call design patterns.
This article describes how to use design patterns, anti-patterns and contains other resources where you can find more information about this topic.