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
I’ve gone back to watch Uncle Bob Martin’s presentation “Agile overview” from NDC 2010 (while you’re at it check his “The land that scrum forgot”, the man is such a storyteller!). In the presentation, Bob tells about Winston Royce’s study “Managing the development of large software systems”, from 1970. This article is the origin of
Last week, I had the great pleasure of attending the Agile Practitioner in Israel meeting. Roy Osherove gave a splendid presentation on the “10 mistakes team leaders make” (and if that’s the sample, you better go check the entire course). As the presentation went on, it was evident there’s some division between the crowd and
If you’ve read any basic agile stuff, you know that agile teams deliver value in a consistent frequency. The team works on what’s important first, giving the best value for money. When working in a consistent velocity, you can estimate very accurately when features are going to be delivered. Prepare yourself for a shock. It
My NDC 2011 talk in moving pictures form. Danger! Craftsmen Ahead! from Gil Zilberfeld on Vimeo.
A funny thing happened to me last week. As I was driving to work, I was listening to another brilliant podcast from Manager-Tools on Assumptive Goal Settings. The curious name (for me, at least) is actually something we’ve done before. AGS is about reaching a goal, when you don’t have a clue how to get
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
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
If you’re like most people you’re under-resourced. You have many more tasks than you can handle. Your team is fully booked. And the work keeps pouring in. They ask: “What should we do first?” What should we work on first to go into the product? Bugs coming in from support calls? Maybe this cool new
I’m a big fan of Manager Tools. I’ve been listening to the podcast and recommending it to anyone, manager or not, for the last five years. A recurring topic in the podcast is Manager Tools co-founder Mark Horstman’s laws: It’s all about people More communication is better. And there are more, and I invite you