Agile.FM Por arte de portada

Agile.FM

De: Joe Krebs
Escúchala gratis

  • Resumen

  • Radio for the Agile Community
    2013-2024
    Más Menos
Episodios
  • 152: Lisa Crispin

    152: Lisa Crispin
    May 1 2024
    Transcript: Agile FM radio for the agile community. [00:00:04] Joe Krebs: In today's episode of Agile FM, I have Lisa Crispin with me. She can be reached at very easy to remember lisacrispin. com. Lisa is an author of a total of five books. There's three I want to highlight here or four actually is Obviously, a lot of people have talked in 2009, when the book Agile Testing came out, a practical guide for testers and Agile teams.Then following that more Agile Testing, right? Then I thought it would be most Agile Testing, but it turned into Agile Testing Condensed in 2019 and just very recently a downloadable book, Holistic Testing, a mini book. Welcome to the podcast, Lisa. [00:00:47] Lisa Crispin: Thank you for inviting me. I'm honored to be part of the podcast.You've had so many amazing people on so many episodes. So it's great. [00:00:54] Joe Krebs: Thank you. And now it's one more with you. So thank you for joining. And we will be talking a little bit about a totally different topic than maybe the last 20 episodes I had maybe way back. I did some testing topics, but I cannot recall maybe the last 20 episodes.So we're not about testing a super important topic. I would not consider myself an expert in that. And I don't know of the audience who has been listening to maybe the last 20 episodes are very familiar with agile testing. Maybe everybody has a feeling about, when they hear the word testing, but there is a huge difference between agile testing.And let's say traditional testing methods. If you just want to summarize like very brief, I know a lot of people are familiar with some of those things, but what it is, if somebody says what is agile testing, why was this different to traditional testing methods? [00:01:47] Lisa Crispin: Yeah. I think that there are a couple of big differences.One is that testing this is just a truth and not necessarily something to do with agile, but testing is really just part of software development. So many people think of it as a phase that happens after you write code, but in modern software development we're testing all the time, all the way around that whole DevOps loop, really.And and so the whole team's getting engaged in it through the whole lifecycle and the focus. Is on bug prevention rather than bug detection. Of course, we want to detect the bugs that make it out to production so we can fix them quickly. But really what we want to do is prevent those bugs from happening in the first place.So there are all these great practices that were popularized by that extreme programming and agile, things like test driven development, continuous integration, test automation all the things that go into, the planning. Workshops and things where we talk about our new features and break them into stories and what's going to be valuable to customers, having those early conversations, getting that shared understanding, things like behavior driven development, where we think about what we're going to code before we code it.That's all really different from, I guess I would say a more traditional software development approach where, Oh, we focus on these requirements. The requirements and a lot of people think about testing is just make sure it met the requirements. But there's so much more to that. We've got all these quality attributes, like security and performance and all the things that we also need to test.So it's a huge area, but it's woven into software development, just like coding, just like design, just like architecture, just like monitoring and observability. It's all part of the process. [00:03:31] Joe Krebs: Yeah. It's like a QA baked in, if you want to see it this way. And then also the automation of all that, right?So automating everything you just said is probably also a concern. Not that's necessarily new to agile, but that's a focus as well now I don't know if I don't have necessarily data points around that but I have worked with a lot of Scrum teams and Agile teams in my career.And it seems, if somebody would say what are the challenges within these teams? And one of them is, you can almost always highlight that, and I say almost purposely because there are good exceptions, is to build an increment of work once per sprint. A lot of teams do not accomplish that, and it's often related to testing activities.Why is that, in your opinion, like when we're seeing these teams struggle to put an increment of work out or a piece of the product or whatever you want to call it if you don't use Scrum necessarily, but to build something that could potentially go out. It's the quality standards of going out. What are the struggles out there for teams, especially on the testing side?I see that as you just said, like it's always happening or often happens at the end, rather than in the front. [00:04:46] Lisa Crispin: Yes. Unfortunately, I see, still see a whole lot of scrum teams and other agile teams doing a mini waterfall where they have testers on the cross functional ...
    Más Menos
    31 m
  • 151: Maureen McCarthy and Zelle Nelson

    151: Maureen McCarthy and Zelle Nelson
    Apr 22 2024
    Transcript: Agile F M radio for the agile community. [00:00:04] Joe Krebs: Thank you for tuning into another episode here of Agile FM. Today I have two guests with me. We are a trio today that is Maureen McCarthy and Zelle Nelson are with me. They both are we're going to go really deep on this the creators of the method that's called the Blueprint of We and they can be reached at collaborativeawareness. com. Welcome to the podcast, Maureen and Zelle. [00:00:28] Maureen McCarthy: I am so thrilled for this conversation, Joe, because. The weaving between Agile and the work we do in the world is brilliant. And I love having the conversation about how that goes on. So [00:00:39] Zelle Nelson: really happy to be here. [00:00:40] Maureen McCarthy: Yeah. Thanks. [00:00:41] Joe Krebs: Awesome. Yeah, we will be talking a little bit about that blueprint of we, but before we do that just to set the stage a little bit with everyone, why the blueprint of we exist, why your work exists.There is a very sad history to this, and that is that Maureen, you found out that you have a rare genetic lung disease, and you are. Operating on 10% lung capacity. Is that correct? [00:01:11] Maureen McCarthy: That is true. I've been on oxygen for 20 years, but nobody lives as long as I have. So it's a, it's very rare. Most people are dead.Within 10 years I've had it 35 . [00:01:21] Maureen McCarthy: So I've had since I was very young. But it's not a sad story. It's actually a very creative story. It's not, I don't, there's lots of crazy stuff that goes on with it, but I don't feel sad about it. We've done so many, we've made the stress of what.A health challenge can be into a creative process of How do you thrive even when stuff is going on that's nuts. [00:01:43] Joe Krebs: Yeah the reason why we connect a little bit the blueprint of we the work you guys are doing and facilitation collaboration is directly tied to this to the lung disease. Can you guys elaborate a little bit on.How this all started for you guys and how you are, obviously your behavior changed as a result of that diagnosis [00:02:08] Maureen McCarthy: we actually met the year my doctors told me that I would die. So it was my 10 year mark of when most people are dead and meeting somebody. We both had our own individual businesses at that point, but meeting somebody the year you're supposed to die, you don't measure anything up against forever.You have to look at what's here right now and decide what you want to do with it. And we realized like the normal path when you meet someone is, do you want to date and get engaged and get married and have a white picket fence? Like you actually have those things that just project in your mind, because that's expected, to at least ask those questions. [00:02:44] Zelle Nelson: There was nothing for us to pull off the shelf to say, this is how you do it. [00:02:48] Maureen McCarthy: Yeah. [00:02:49] Zelle Nelson: So we had to design it for ourselves [00:02:51] Maureen McCarthy: and we created this. Document this relationship design document. We realize we've got to design something that's so specific to us and there's things that we want to No one understand about ourselves, about each other, but most specifically about who we are together.If this isn't what doing what you normally do when you become a couple, what the heck is it? So that design process we wrote down, we're like, let's do a design process, a design document, let's make it iterative and changeable and. Upgraded over time to, to show us who we are when we learn more about ourselves, about another, when we go through the chaos of in and out of the hospital and losing more lung capacity and massive levels of pain and just crazy things.You've got to be agile. You literally have to be agile. And without the design document, I think we could have gotten lost. In a path that can be very chaotic, especially because lots of people around us got worried. It made me understand the difference between worry and care. Like when people worry for me, all my pain gets worse.It's harder to breathe when people care about me. It's two different ways we're using our neurocircuitry, right? And care is a way to support other people. Worry is a way to add more stress and fear and the weightiness of all that. And when you've got 10 percent lung capacity. You feel weightiness unlike other people.Yeah, this is, I'm like a little like a little experiment of my own body of what it means to be like collaborative and connected, because everything that's going on in my body, we use as a way to be part of the design. Like this, there's chaos going on in here. How does that mirror the chaos of the world and how do we design healthy relationships and healthy interactions based on, what could be considered chaos?[00:04:40] Joe Krebs: Yeah, so this blueprint you guys, we're going to go a little bit deeper here. It's really something you build, it's a process. It's a relationship design process used to ...
    Más Menos
    30 m
  • 150: Maggie Jackson

    150: Maggie Jackson
    Apr 1 2024
    Book “Uncertain - The Wisdom and Wonder of Being Unsure”: Transcript: Agile FM radio for the agile community. [00:00:05] Joe Krebs: Thank you for tuning into another episode of Agile FM. Today I have Maggie Jackson with me. She wrote a book called Uncertain the Wisdom and Wonder of Being Unsure. She also has published a book Distracted you might be very familiar with because it has been published a few years ago. Maggie is an award winning author, journalist.She writes about social events. In particular about technology. She's a contributor to the Boston Globe. She wrote for the New York Times, the Wall Street Journal, and she has been featured on media around the world, including MSNBC, Wire. com, and the Sunday Times. And now she is on Agile FM. So thank you so much for being here and sharing some thoughts on the latest release, Uncertain, with the Agile FM listeners.[00:00:54] Maggie Jackson: My pleasure. Great to be with you. [00:00:56] Joe Krebs: Yeah, that's awesome. You have some really good endorsements and praise here from people like Daniel Pink, Gretchen Rubin and Sherry Turkle on your book. This is it's really amazing. You you have written this book. This was recently released in 2024. So this is a new publication.What drove you to writing this book? Uncertain. What was your motivation of approaching this project, this book? [00:01:24] Maggie Jackson: Yes, sure. Especially because uncertainty seems so foggy and monolithic and negative. And I, after I wrote the book Distracted, which is about, the gains and costs that we have in a split focus world wanting to write a book about thinking, so if you have a moment somewhere, focus, or you have the skill to focus, what do you do with it?And of course, thinking well is our challenge as we move forward in this world, in this day and age. And so the first chapter of the new book was about uncertainty, and it became in a classic way, the whole book, because first of all, because I discovered, veins of or explosions of new research in so many different fields from medicine to business to psychology, a lot of new research about uncertainty.And it hadn't been a very well studied topic, believe it or not before. And by that, Epistemic or psychological uncertainty, which is the human response to the unknown. So I'm really writing about our human response to the unknown and the basically the idea that when you meet something new and unexpected, Your response is to understand that you've reached the limits of your knowledge that you don't know that it could be this way.It could be that way. So that's how I fell into writing the book and I discovered as well that uncertainty is highly misunderstood. It's maligned and yet it's far. It's not weakness. It's not inertia. It's not the negative that we all assume it to be today in this efficiency oriented society.[00:03:03] Joe Krebs: Yeah that's true. We probably have some listeners here at Agile FM that are maybe in the corporate world and they are building products and or executing projects of some sort. And and we see the desire of being certain. We see the desire of running and having a plan, even if the plan is very short and maybe only a few weeks long.Uncertainty is always present, isn't it? [00:03:29] Maggie Jackson: Exactly. And again there are these two kinds of uncertainty. There will always be unpredictability there. Life will always take twists and turns. And we might have the data and the models and the plan. And yet, there's so much we can't know.Despite this incredible probabilistic weather models that we have, you don't know if the snowstorm will dump one or two inches on your backyard next week. So there's so much we can't know. We don't know, but what we can do is control our response to the unknown. We can get skillful at understanding how to manage not knowing or what we don't know and what we want, what we're not sure about.And that's where the, that's where the news is fantastic. There's so much now that relates to how uncertainty basically is very highly connected to. Cognitive skills like curiosity and agility and resilience, which are exactly the kind of cognitive skills we need now on. So I think you're right.And another point I'd make is that we always will need resolution. We always know we'll need an answer. And of course, we want a plan and a kind of security. And yet. By, over predicting or clinging to a plan when it's out of date. That's where we lose the agility. So what I'm talking about is opening up the space between question and answer.Uncertainty is really that middle ground. It's basically. The brain's way of telling itself that there's something to be learned here when you're meeting something new, you have a kind of stress response, which is really, that's where the unease and the discomfort of uncertainty comes from. It's a stress response.But now we're beginning to find out scientifically that unease is actually highly beneficial because, as I mentioned, the brain ...
    Más Menos
    29 m
Gestión Economía Éxito Personal
Más Menos

Lo que los oyentes dicen sobre Agile.FM

Calificaciones medias de los clientes

Reseñas - Selecciona las pestañas a continuación para cambiar el origen de las reseñas.

Reseñas de Audible.com

Opiniones de Amazon
No hay comentarios disponibles