Extreme programming

So thinking about this, our agile manifesto that we talked about is the mindset.

Scrum Kanban, XP, blah, blah, blah, blah, blah, are frameworks.

So Scrum will tell you the daily scrum, this is what the daily scrum is, this is why we do the daily scrum.

It doesn't tell you how to do the daily scrum.

Okay.

So if we're talking about frameworks, then let's explore some of the frameworks that we might use if we're trying to be more agile as an organization.

So perhaps we're talking about, I think I know you mentioned Scrum, Kanban, XP.

So Which of those? How do organizations choose which one they want? What was that? I missed the hand signal.

I agree with that.

I think in Extreme Programming XP written by Beck and Fowler, they speak about, I mean, this is years ago, they speak about quality being the kind of the one lever you should never pull to reduce that in order to improve other things.

Like quality is going to be the most important thing to any co-base.

It will save you costs in the long run.

And that's Kent Beck.

Kent Beck wrote the book back in... 2000 Extreme Programming Explained, and we embody our version of extreme programming here at Minimal.

I don't know if it would be the way Kent would have done it, but here's what I can say, and it goes back to what you said, Jeff.

My sense of how Kent came up with the original practices of extreme programming is he didn't sit in a think tank room and say, well,

What other things could we try that could make? He looked back in his

own history and he said, when was I producing the best results? Under what conditions was I making the best progress on the project? When was I producing the highest quality? And he just started cataloging because I think in many ways he was as frustrated as I was.

And the dialogue, very rapid, because they can make the changes like that, the dialogue eventually drives the product where I want it to be.

That's the old extreme programming model, right? You go around in loops.

They were one-week loops or three-week loops, you know, back in the day.

But you go around with loops with the customer until you finally drive the system to where the customer wants it.

Whip up something that works, and now let's talk about what we don't like about it and refine.

So

this gets back to an idea that I used to talk about way back in the extreme programming days.

And I'd get an audience, and they were, you know, oh, we don't know about this extreme programming stuff.

Bing.

And we've been trying to figure out how to explain extreme programming in modern, recent kind of terms.

I think the juice has been squeezed out of extreme programming.

And finding another way, but the concepts are still there.

They're still valid, more valid in an AI world.

And this metaphor of the forest and the desert seemed to really resonate with folks.

So the deeper I dove into it, the more valid I find the analogy.

Since the first days of extreme programming, we've had this communication problem.