Recently, I’ve done a management workshop on TDD. The audience was developmenet managers and team leads. Most of them did not know TDD. (Actually, most thought they knew what TDD was. But that’s a completely unrelated story.) During my session, I’ve walked them through an example (from Star Wars) and showed the thinking behind it,
When on the Scrum Master Podcast, I was asked a very important question: How do I get a systemic view of the organization. This is worth going deeply into. Let’s start with why this view is valuable. The more I work with teams, I find there’s a limit of change I can make. Or, rather, they can
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
As I was tinkering with my new CI toy, I became aware of a difference between light CI tools, and the feature heavy ALM tools: Permissions. I always I knew it was there, the ability to restrict all kinds of stuff. From adding work items, to deleting files from source control and to view comments.