I’ve been thinking lately about how agile turned out to be the way we know it today. And the more I think about it, I get more depressed. You see, agile was supposed to save us all. It was supposed to be the bridge between business and developers. And 10 years after its inception, we
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
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
Jim Highsmith recently wrote about “Velocity is Killing Agility”. Velocity was originally used as a planning tool. You measured velocity in the past, in order to see how much throughput you’ll get in the future. If we put it very simply: Throughput = Capacity x Velocity Now, as Jim describes in his post, velocity has
As I was going through Twitterland, I heard this strange sound: “Coders are special. We are expected to know how to do things we’ve never done before and estimate how long they will take." Well, yes and no. The part about estimating how long it will take is definitely true. See, there’s someone paying for
Here’s a short, incomplete list of my upcoming public speaking engagements. When I know, you’ll know. I’ll be speaking at the Agile Development Practices East Conference on Wednesday November 9th, at the Rosen Centre Hotel, Orlando, Florida. My talk is about “8 Principles for Better Unit Testing”. I’ll be at the conference area throughout Wednesday
InfoQ had a round-up of ideas about “How Long Would it Take to Build the Product?”. It was funny (ha-ha funny) to read some of the responses. One person suggested that upfront estimations end up in a fixed scope, which is anti-agile. If I was new to agile, I would read it this way: if
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
Last week I had great time hosting a Typemock Webinar called “10 secret unit testing tips”. The fun thing was that I’ve discovered both in preparation and answering questions live that I have at least 20 tips in me for at least two more webinars. So prepare for “10 secret unit testing tips strike back”