This is the presentation I gave today at the “QA and Development in Agile” conference (It’s a bit more detailed than what the people in the room saw). This wasn’t a technical presentation, just an overview to the newly initiated to unit testing – third of the room wrote unit tests, the rest didn’t. And
It’s been a few weeks now, for my tenure as product manager at Typemock. Time for a review. What did I learn of becoming the product owner in an agile company? Get yourself a good coach. That may be true for every profession, but especially for the newly initiated, it’s a blessing if you can
In my last post, I warned against the dangers of the craftsmanship movement to itself. The main premise behind this warning is that business and developers don’t speak the same language. And since business has the upper hand, role power, money – business always wins. Martin Fowler’s post, Craftsmanship and the Crevasse, looks at the
I’ve gone from Michael Feathers’ post to Dan North’s post and then to Jason Gorman’s. If I need to choose a side, I’m definitely on Dan North’s side. As I was reading these posts,they seemed familiar. The holy wars and the calls to stop them, the call to better developers to separate themselves from the
In the last few weeks, we were hit by the flu. Many (including myself) have fallen before the mighty bug. Even after coming back from their sick bed, people have gone off for a second or even a third round. And lost. And the few that remained on their feet, need to carry on with
Something strange is going through TDD land these last couple of weeks. First it was Uncle Bob,with a new TDD theory – making tests pass in a certain order, actually helps incremental design, leading to a better solution. This is a very interesting post, and if he’s right, he might have discovered the cornerstone of
The first thought I had, reading about the Skype meltdown last week is: here’s another opportunity to score points for unit testing. Nothing like a a single bug causing so much havoc (or silence, in this case) to get developers attention to the catastrophes waiting to happen. But I decided to go deeper. There are
I was asked this question last Wednesday, when I led a TDD open session at the Israeli Software Craftsmanship User Group. My answer: It makes you think before you write code. In fact, next time somebody asks you what TDD stands for, you answer: Thinking-Driven Development. Sure, all the benefits are there: structured incremental progress,
I’ve witnessed a sort of agile/lean clash incident at our standup. Reviewing our kanban board, as tasks completed, others were left on the board. Instead of completing the tasks in progress, a developer decided to pick new tasks to work on, entering them into process. The Clash Agile promotes team empowerment. Developers are encouraged to
Heads-up: I’ve recently started looking more closely into lean and kanban. Expect more posts like this one. Typemock is a unique company. Developers’ work is similar to our customers’ work. And so, since day one, the developers have also been doing support work. Support calls have their own life cycle. That’s why usually they are