Luke: But I was thinking like, is there a way to do that foul fast, fail often, but expand so that you're failing less often over time? And I got to the conclusion like visually in my head, it's kind of like ⁓ it's kind of like the ⁓ Fibonacci sequence. So you think about the Fibonacci sequence, it starts really small. And expands, but over time the numbers get further apart. And that's where it sort of resonated with me. I haven't done much with it since, but that was like the epiphany, like the the what what do you call it? The the ⁓ back to the future he hits his head on the toilet and he fixes a time machine. Obviously I haven't thought of the time machine, but the Fibonacci sequence was that moment when I was like, That's it, it's the Fibonacci. It's it's fail fast, fail often, and then as you get better at it and as you learn from it, you're failing less often, but you're on this spiral, and then when you get to the end of the spiral, you release and then you do another and you cycle again.

Matt: I'm with you. If I remember rightly from I mean, from my very limited exposure to actually like really working officially within like a proper Scrum or Agile environment. You can change the length of the sprints, although I do think that they're supposed to be uniform so that you can build in some level of consistency. However, ⁓ I I'm sure I've seen somewhere a similar kind of idea to this, where what you have is you've got your two week or your one month sprints, whatever duration you set them to be. But at the same time you then have a larger sprint that's going across all of those smaller sprints. So that's yeah, I see where you're coming with that. I like the Feminazi reference as well. That's like a really fascinating way of

Luke: Yeah. Yeah, it's scaled agile framework safe, they call that. ⁓ yeah, which is and then you've got the biggest sprint that goes on top of the smaller sprints. Yeah. But it but it's yeah it's it's yeah, it's similar to that. Similar to that. And and if I was to speak to an agile connoisseur now he'd probably No, that's exactly what you want because But I'm so used to game development where you've got the milestones of like milestone one is this, two, three, four, and then you can have agile inside that. It's like it kind of

Matt: Is that that's the one where you've got the longer sprints on top of the smaller sprints? Yeah. Yeah, yeah, yeah, yeah.

Luke: hits the spot but doesn't quite hit the spot. ⁓

Matt: Yeah. So how would it work? So it right. So you're you're building your like I di I totally see where you're coming from. That's the great thing about this idea actually. The explaining it, it's like well, it sprints but in a Fibonacci sequence. I think it's a really good snapshot.

Luke: Yeah. Yeah. They Yeah. At first it was a snail shell in my head and then I was like, What does the snail shell represent? ⁓ that's the fib, and aren't she seafids? Yeah. So like the it's like the twos and the the it's like all the different low numbers and and then and then the bigger numbers. And when you get to the twenty one you should release.

Matt: That's Fibonacci, right. Hmm. So the the best ⁓ the best thing about coming up with a new idea is getting to name it. So like what ⁓

Luke: Yeah, I'll call it the Tim's method. There we go, boom. Stick my fucking stick my stick sorry, French. Stick my name on it. Yeah. Stick my fucking name on it. Yeah.

Matt: Set my fucking name on it. The ⁓ yeah, I like that as a working title. I think we can do better, but I I won't push the point.

Luke: We could do better. So comments and suggestions ⁓ below please. And don't forget to give this video a hype. Apparently that's a good thing now. Give it a hype. Yeah.

Matt: Yup. Yeah. Give it a hype, whatever that means. ⁓ lovely. Like, subscribe. Hype.

Luke: Hi. So yeah,