Monthly Archives: June 2010
I’ve been learning Scala and during the process I have tried two different IDE setups, Eclipse and IntelliJ. They both can integrate Scala and provide syntax checking, test executions, code assistants and so forth. I’ve been working with the Scala 2.8.0 release candidates so the environment has fluctuated a bit due to the changes between
Many have gone through the agony of a Scrum transformation and noticed that revolution is hard. It requires a lot from the people involved but at the same time it is mostly adapting to new surroundings, to the new way of collaborating and making work visible. Agile methods come with the implicit expectation that you
What is needed for functional retrospectives? Retro’s do not always work and sometimes it is difficult to see why. After taking part in both unsuccessful and successful retro’s I now try to list couple of things I think are required for functional retrospectives. Team You actually need a team. Not a group of individuals where
Usually our team achieves 20 +/- 2 points in one two week sprint. The sprint we finished yesterday showed some amazing figures. We completed 37 story points. When we arrived at our retrospective we did not have a clear agenda so the retro was used to think why we had so successful sprint. Our scrum
As Cory Foy puts it, craftsmanship equals responsibility! The change starts from you. If you won’t do it, no one is going to do it for you. A good starting point is the Apprenticeship Patterns. Go and read it on-line. And do not forget the Manifesto for Software Craftsmanship! And watch Cory’s presentation from XP2010!