If you’re already doing agile wrong, retrospectives are one of the first things you let go of. A shame really, but if you’re doing something wrong, you better screw up the thing that will bring you the most value. Why does dropping retrospective seem the least harmful? If you think planning is important (because it shows
Because having source control is a solution. Sometimes we get fixated on something that’s missing, and we’re sure that’s the problem. When we can control it, it really isn’t a “real” problem, because it’s easily solved. But in many cases, the solution is out of our control, and we think that if only we had
As part of my ADC experience, I enjoyed being part of Gojko Adzic’s session: The Specification Game. The room was divided to groups of four – there were 6 teams. Each group included a product owner, developers and testers. Gojko and his team were the customers. They rolled out a product they needed: a Black
I firmly believe that in order for a team to succeed they should be committing themselves, and take accountability. I saw teams succeed when they do, and saw teams fail when they don’t. So in the upcoming changes we’re making, we want the team to be part of it. Thursday, we did a partial retrospection,