It’s coming out in installments:
and the whole thing in one piece:
Which is cheaper, waterfall or agile?
Briefly speaking, waterfall is a cost-optimizing strategy, agile is a time- and value-optimizing strategy. So, when it works, waterfall should be cheaper and agile faster. (ref: all the rework in agile).
But there is the cost of mistakes. In agile, incremental development causes constant rework. In waterfall, you don’t detect certain category of mistakes […]
These questions came from Stéfane Wojewoda at InfoQ in France. They are great questions, so I make the answers available here:
From the interviewer :
Alistair in the Hexagone
(note: “Hexagone” is a French word-play, the reference to the Hexagonal Architecture (discussion: Re: Hexagonal architecture) and also to the shape of France, roughly hexagonal, and hence sometimes […]
Jim Highsmith and I decided in autumn 2001 to create an agile conference for all roles, all methodologies (“big tent”). At the time, there was only the annual XP conference, which was programmer-centric, XP-only. We set June 2003, Salt Lake City, as the date and place.
Todd Little offered to help us shortly thereafter, and was instrumental in making the 2003 […]
In 2000 I tumbled onto the idea that information flows through organizations in the same way as convection currents of air (see the Harnessing Convection Currents of Information OOPSLA 2001 ppt pdf (discussion: Re: Harnessing Convection Currents of Information OOPSLA 2001 ppt pdf) talk).
I used to diagnose organizations and simply stand there and imagine all the […]
In 1998, I visited the Chrysler C3 project in Detroit and coined the phrase “A story card is a promise for a conversation.”
Why would I do that?
At that time, the word “requirements” was still very active. Requirements were of course written down.
A user story on the C3 project was just a few words written on a card: […]
Theory X versus Theory Y and Push- versus Pull cultures
I have become told that I have redefined “pull” a bit to make it fit the metaphor/rhyme, and it will cause misinterpretation. I need to think about the consequences of that.
“Pull” in my sense is not the same as “pull” in Toyota, lean or kanban or any of the other ones. […]
Howard’s Introduction to the podcast interview: “The “enigma wrapped in a puzzle” Alistair Cockburn has an interesting story: signatory of the Agile Manifesto, author of two pivotal books “Writing Effective Use Cases” and “Agile Software Development,” and founder of the Agile software development conference in 2003 along with the more recent “Heart of Agile” conference. This last, “Heart of Agile,” […]