To improve we need transparency. We cannot solve problems we don’t see. We can’t improve an invisible process. We need people to speak out about how they feel, how their work is affected. In order to improve, my team needs me to admit I’m late, and not hide I’m working for two weeks, digging a hole, and find out
At Agile Israel conference, I was recruited to a “Hit The Experts” panel on engineering practices. Ok, I didn’t put too much of a fight. Most of the questions were not of the engineering nature, though. One of the questions went like this: We’ve adapted the Spotify model, and now there’s no specialization, expectations from
When I was a developer, I couldn’t understand why other developers were not as competent as me. When I was a team leader, I couldn’t understand why my team didn’t measure up to my glorified project saving success. When I joined Typemock, I couldn’t understand why most developers are prepared to live in bug-world, rather
Had great fun today at the Agile Practitioners 2013 conference today. Great keynotes by Boris Gloger and Dan North and great presentations by others, as well as meeting old and new faces. For the ones who missed my presentation, and those who want to feast their eyes again, here are the slides:
There are many agile conferences these days. Many of them are not about what we used to call “agile” anymore. In fact, a friend pointed out when I mentioned a TDD session from an agile conference, saying: Really? An agile presentation with code? Most of the topics today are moving towards lean, kanban, leadership and
Let’s say we’ve “conquered agile”, and the prophecy came true: we have a self-organizing team. How does leadership fit into this? What does a leader do in a self-organizing team? Influence. Leadership comes in many shapes and colors. There’ll be the technical leaders. The experts about technology and or process. There’ll be social-political leaders. We’ll