Last time we looked at how things came to be. How things converged around a group of software developers in a ski resort: There were actual experiments in the field with reported successes. There was a funnel for communication to spread those ideas. And now there was a joint vision and a name. The agile
My two-step forward, one-step back dance with Trello began way before I boarded the kanban train. In the beginning we used it as our main tool for planning, documenting and controlling development. The team was willing to try it, after using a whiteboard and (not-so) sticky notes with the planned-doing-done trio, which we copied to
In the beginning we had plans. These plans were crucial to the business organizations. They relied on products being ready, so marketing could have marketing prepared, sales can sell them, and support support them. Then reality happened. Either the products were not ready on time, or their quality was bad, or were not what the
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
I’m addicted to predictability. I admit it. I want my life to flow along, according to plan. Sure there will be some minimal changes, but I can adapt. I’ve given up on this long ago, as I came face-to-face with real life. I know life is not predictable. And I have embraced change, as agile
I want to thank everyone who come to my presentation yesterday. I got my inspiration (and a few jokes) from the following presentations: Agile Overview – Robert Martin The Land that Scrum Forgot – Robert Martin The Mistake at the Heart of Agile – Michael Feathers And for the people who want to read the
If you’re in Israel, and understand Hebrew – you’re eligible! Join me on Sunday, 4-Dec-11, for a lesson you’ll never forget (or at least for the length of the presentation) – An agile history lesson. I’m going to talk about how we got here, what did we do on the way, discuss the question on
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
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
Apparently, I’ve become addicted to my task list. My latest “things that work” to juggle tasks works great. Except when it doesn’t. When’s that? Weekends. I took precautions to have the ability to write down tasks when I’m away from my computer. But, I still manage to think about things to do when I’m not