Podcast appearances and mentions of Alistair Cockburn

This interview was recorded at GOTO Aarhus for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview hereAlistair Cockburn - Co-Author of the "Manifesto for Agile Software Development"Aino Vonge Corry - Retrospectives Facilitator, Teacher, Technical Conference Editor & Author of "Retrospectives Antipatterns"RESOURCESAlistairhttps://twitter.com/TotherAlistairhttps://www.linkedin.com/in/alistaircockburnhttps://github.com/totheralistairhttp://alistair.cockburn.usAinohttps://twitter.com/apaipihttp://metadeveloper.comhttps://github.com/apaipihttps://linkedin.com/in/aino-vonge-corry-9a23801DESCRIPTIONAlistair Cockburn shares his insights on the profound impact of AI on the Agile community and beyond. Together with Aino Vonge Corry they reflect on the history and evolution of Agile, contrasts AI's transformative power with past technologies, and expresses concerns about AI's potential to disrupt various professions.He emphasizes his role as a "Bard" rather than a futurist, focusing on current trends and practices around the world. The conversation also touches on Denmark's resilience in the global recession, highlighting the unique societal perspectives that contribute to happiness in Scandinavian countries.RECOMMENDED BOOKSAino Vonge Corry • Retrospective Antipatterns • https://amzn.to/3naFk84Derby, Larsen & Schwaber • Agile Retrospectives • https://amzn.to/3hB4eNkStone, Chaparro, Keebler, Chaparro & McConnell • Introduction to Human Factors • https://amzn.to/3mfXqY2BlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 16/11 a 22/11.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 16/11 a 22/11.

One of the most dramatic of the Gilbert and Sullivan comic operas is The Yeoman of The Guard, which is set in the Tower of London in the 16th Century. It was premiered in London in 1888 and ran for a record 423 performances causing it to be called a true English, Dramatic Opera. G&S Cape Town will be staging this opera at the Artscape Opera House from 10 August and I invited the music director and Production Co-ordinator, ALISTAIR COCKBURN into the People of Note studio to talk about the production.

Cancel your standup and record your decisions in writing, not conversations. This week on Troubleshooting Agile, Collaborations Expert and Author, Sumeet Moghe joins Squirrel and Jeffrey to explore "async-first" software development. Links: - Sumeet Moghe: https://www.linkedin.com/in/sumeetmoghe/ and https://www.asyncagile.org/ - The Async-First Playbook: https://www.thoughtworks.com/en-gb/insights/books/async-first-playbook asyncagile.org - Alistair Cockburn graph: https://agileconversations.com/AlistairCockburnCommunicationGraph.png - Martin Fowler "Periodic Face-to-Face": https://martinfowler.com/bliki/PeriodicFaceToFace.html - James Tannier, Effective Remote Work: https://pragprog.com/titles/jsrw/effective-remote-work/ -------------------------------------------------- Order your copy of our book, Agile Conversations at agileconversations.com Plus, get access to a free mini training video about the technique of Coherence Building when you join our mailing list. We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com -------------------------------------------------- About Your Hosts Douglas Squirrel and Jeffrey Fredrick first met while working together at TIM group in 2013. A decade later, they remain united in their passion for growing organisations through better conversations. Squirrel is an advisor, author, keynote speaker, coach, and consultant, helping companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: https://douglassquirrel.com/index.html Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, author and speaker. You can connect with him here: https://www.linkedin.com/in/jfredrick/

If two parents can run a family, why shouldn't two executives run a company? We dig into the research and hear firsthand stories of both triumph and disaster. Also: lessons from computer programmers, Simon and Garfunkel, and bears versus alligators.  RESOURCES:"How Allbirds Lost Its Way," by Suzanne Kapner (The Wall Street Journal, 2023)."Is It Time to Consider Co-C.E.O.s?" by Marc A. Feigen, Michael Jenkins, and Anton Warendh (Harvard Business Review, 2022)."The Costs and Benefits of Pair Programming," by Alistair Cockburn and Laurie Williams (2000)."Strengthening the Case for Pair Programming," by Laurie Williams, Robert R. Kessler, Ward Cunningham, and Ron Jeffries (IEEE Software, 2000).EXTRAS:"The Facts Are In: Two Parents Are Better Than One," by Freakonomics Radio (2023)."The Secret Life of a C.E.O.," series by Freakonomics Radio (2018-2023).

Idea zaproponowanej przez Alistaira Cockburna architektury heksagonalnej ma już prawie 20 lat. Ale jak krótko i rzeczowo opisać założenia Hexagonal Architecture, czy też Ports & Adapters? I jak to przekłada się na kod systemu?Każdy koncept można bardzo mocno i niepotrzebnie skomplikować. Nawet tak prosty w swojej istocie jak Porty i Adaptery. Dziś z moim gościem, Kubą Nabrdalikiem, wracamy do korzeni z 2005 roku i staramy się wyłuskać esencję tego wzorca architektonicznego. A jeśli przy drugim mikrofonie gości Kuba, to wiadomo, że będzie do bólu pragmatycznie i prosto w z mostu...W dzisiejszym odcinku:czym jest architektura heksagonalna,czym są porty i adaptery,skąd w ogóle wywodzi się ten koncept i jak ma się do dzisiejszych czasów,jakie typowe błędy można popełnić stosując ten wzorzec w kodzie,nie zabrakło oczywiście przykładów z życia i produkcji...Materiały dodatkowe:hexagonalarchitecture.org, homepage na temat Ports & AdaptersHexagonal architecture, nowsza wersja oryginalnego wpisu Alistaira Cockburna na temat architektury heksagonalnej z 2005 rokuHexagonal architecture @ wiki c2, wpis na blogu Warda CunninghamaSmallerWebHexagon, wspominane w odcinku repo pokazujące bazową ideęHentai, repozytorium Kuby Nabrdalika pokazujące użycie hexagona z modularyzacją i innymi technikami

Transcript: Joe Krebs 0:00 2023 marks the beginning of the second decade of agile and for the past 10 years, I've been releasing podcast episodes with a variety of speakers and topics to you. And I hope you enjoy the ride so far. I don't know how many of you guys actually know the beginning of agile, and how it all started. While I started, the idea of a podcast actually started after a visit with Jean Tabaka in New York City, where we recorded again, a audio segment for the New York City community. After the recording, she pointed out that this was a really interesting conversation. And she really enjoyed it. And she thought, why am I only releasing this content to the New York City crowd and not on a world level as a podcast? So I began thinking about it, produced a podcast, and eventually it turned into agile FM, something you'll hopefully enjoy today. So as a tribute to Jean Tabaka, which left us way too soon, in 2016, I decided to re release that original content from 2013 with her. And what's amazing after I really listened to that audio segment with her is how much she already talked about organizational agility, somehow business agility, and some collaboration issues that are still valid today. So thank you, gene for, you know, helping me to get into the podcasting. And, you know, having me indirectly meet so many people on this podcast recordings. But I also wanted to make sure that everybody out there knows how influential Ginger Baker was in a variety of ways, and how valid her books and contents still are today, in 23. So I hope you enjoy this one. And in memoriam here is Jean Tabaka. Agile New York City 2013. Joe Krebs 1:56 I am your host Joe Krebs, and today I'm here with Jean Tabaka. Welcome to the podcast. Thank you so much, Joe. Jean, you're in town for a very special event to the edge on New York City community. We're celebrating our fifth birthday. Today, actually here at Pace University in beautiful, sunny New York City today. So thank you "A" for coming to the podcast. And "B" more important is actually speaking tonight to the edge on New York City community. That's a that's a wonderful thing for you.Jean Tabaka 2:26 Thank you. Thank you so much for inviting me. And I guess I could take a little bit of credit for the wonderful weather I brought from Colorado. What the heck. Yeah. And to be part of the fifth anniversary. Wow, what an honor. So seriously, thank you so much. This is great.Joe Krebs 2:45 Well, thank you, Jean, when I was when I was researching a little bit around your book, actually, in preparation for this podcast, I realized that, although we're turning five years, your book is older than five years. Yeah. Well, your book prior to the creation of agile in New York City. Wow. And it's still up to date. No, no. Should we say the book is timeless? It is it's still valid. I mean, people still read it. It's still a topic of conversation. It's not like a programming language has been outdated. The book is still very relevant. It's collaboration explained.Jean Tabaka 3:23 Right. Interestingly enough. About 2003. I think it was, I'll be talking about this in my talk this evening. But I'd like to really bring it up now. So thank you very much. And I was approached by the executive editor of the Agile Software Development series that was being run by Alistair Cockburn and Jim Highsmith. And he said, someone told me to talk to you. Wow, that was a bit frightening right there. And he said, I gathered that you have a great passion around collaboration, and specifically about how to facilitate collaboration. And I said, Yes, because I believe in the human aspect of agile, I read about it. And I don't see in the books, clear guidance about how to bring about self organization, how to make sure all the voices are heard, and how you can gather the greatest pools of insight. And he said, well, then write a book about it. I said, I could do that. But I think these sorts of things are much better transferred in person. And he said, well write the book. And it took me a long time to write the book, because very honestly, I didn't believe in it. I kept saying to him, but no one will read it. And he said, No, I believe in this book. And in fact, back to your point, Joe, he said, This is material, I believe will live on fact beyond many of the other books and he said if it doesn't, I promise su I'll work with you. I won't publish it if we really don't believe in it. And shoot. It's, it got published. It's gone beyond my wildest expectations. I am blown away, truly humbled by the people who still come to me worldwide and say, Thank you. Thank you for this book. I seriously never would have imagined and the gentleman who urged me to do this. Well, he was right. Yeah.Joe Krebs 5:40 Being persistent, right, and making you believe in, in what you're doing? Yes, even though you might not be seeing it at that point. But I did.Jean Tabaka 5:49 And I think you and I were talking earlier about our technical backgrounds. And I kept thinking, my book really isn't technical. Is it going to allow others to see that I have a technical background? Will it look like soft, fuzzy skills. And that was a part of the challenge for me as well to publish the book. And it's, again, just humbling that it's been welcomed into the community as it has.Joe Krebs 6:18 Well, the the other part of your title collaboration explained is actually facilitation skills for software project leaders. Yes. So what I actually like about this, two aspects of it, which are actually more important than ever, in our Agile community facilitation skills. And in 2006, when he was published your you talked about leadership?Jean Tabaka 6:40 Yes. In fact, that's the first chapter in the book. Wow. Thank you, Joe. Yeah, the first chapter of the book is on servant leadership, and what it takes. And there were people who had told me, Well, first of all, get rid of that chapter. And I just wouldn't, I refused. I believe that as we not just inform the Scrum Masters and the Agile coaches within our agile world, that is, we scale and have agile move outside development organizations, we move out what I'll call the value stream, that organizationally, we have to invite the notion of servant leaders, and people who believe in the insights of the teams as they bring forth their visions. That was very important to me. And that's why I lead the book off with that.Joe Krebs 7:39 So you have been doing this since 98. Yeah, the actual communityJean Tabaka 7:42 I am one of the Agile grandmothers.Joe Krebs 7:47 Since 98, there was also the word software in your book with would that be a word we could almost now like years later, almost eliminated, like because so many people do Agile outside of software development?Jean Tabaka 8:00 That yeah, I think that at the time, because my background was strictly software. I have a graduate degree in computer science learn. And that's all I've ever known about the world. And there's been this slow transformation of how I've gone from being analytical, to be more aware of the creative and humane side of how we create software. When the book first came out, I remember I had a gentleman contact me six months to a year afterward and say, he was from New Zealand. So right then and there again, I was blown away. Wow, my book was selling in New Zealand. And he wrote to me to say, why didn't you put the word software in this title? This book is not about software. It's about how to help organizations really be collaborative, how to facilitate collaboration. I knew about that, only in the software world at the time. And as I now look farther out, and around me, I see that and hear from people. This really isn't just about software. And thank you for helping software people understand the value of it.Joe Krebs 9:18 Why do you think it is that we have seen so many technologies come and go. And the topic of collaboration, facilitation is still very much a coot. I would actually say like it. It's important, more important than ever. What do you think is why technology can't solve specific problems in human behavior? We have all these tools will be now and but it seems like the projects are still not more successful from a from a collaborations perspective. Did you agree or do you do you think just been done some progress?Jean Tabaka 9:54 It's interesting. Originally, my target audience was For people who felt that more control would provide more success in the software world. And so I was trying to help command and control environments move to more collaborative environments. Some stuff I've been reading lately, interestingly enough, is pushing back on the agile movement saying, no people need to be able to work on their own to be truly creative. And I've been responding to that and a couple of posts here and there saying, I all the more believe in facilitation as a role because in this world where creativity needs to come both from the group, the the team, as well as the individual where creativity comes from both spaces. A really well informed and well seasoned facilitator is also sort of paid to be an observer, and to bring out the strengths of the team and the individual. So we raise the overall wisdom of the team, by individual contribution, and by overall team contribution. I don't know if that really answers your question orJoe Krebs 11:14 not? Well, yeah, I've seen like teams, distributed teams primarily, there was like, honestly, Cyril collaboration. They were assigning tickets to each other, talking. And that's not the collaboration I have in mind right?Jean Tabaka 11:29 Now it's not and and thank you for bringing that up. I've worked with a lot of distributed teams teams distributed within the same city within the same same state within the same country within the same continent, and then across three different continents. And again, the assumption is, well, we need to add more and more control. And I recognize that the scaffolding around these environments does require a bit more work than when the team is co located, we lose so much of the communication and the implicit versus explicit communication flow. The the tacit versus tribal knowledge. At the same time, when I've been traveling in India, and China, and Texas, sorry, I had to throw that in there. Talk about three different cultures. And what I have been doing is trying to help leaders in these types of environments understand good facilitation is all the more important. Because what I discovered that is that without good strong facilitation, in each of the remote areas, or distributed areas, as well as across the distributed teams, we can't really be reap the benefits of agile at all. In fact, people will start to become very alienated. And assume, frankly, sabotage by the other people. The only commitment the only communication device you have is a ticket. it for some reason, carries a little, little seed of blame and shame with it. Yes, that's not the intent. But boy, do I see shame and blame flying, you know, transcontinental.Joe Krebs 13:37 It's true. It's true. It's really true. Yeah. Well, you mentioned the Agile. I don't know exactly what you say as a movement or agile. You want to push back a little bit. You actually seeking a lot of advice outside of the Agile community. In your talk tonight, tell me why the Golden Circle of Agile? You you actually outline on our website, which is on www agile nyc.org. You actually say? Simon's you were very much influenced by Simon Sinek actually by a TED talk. Yes. So you're actually reaching out to totally other communities, tribes, so forth for for advice, and you map that to, to agility. Is that right?Jean Tabaka 14:24 Yes. Yeah, I want to clarify that I'm not pushing back on agile. What I'm doing is I'm inviting in and pulling in more resources into my technical world than I ever would have imagined. So initially, I was proud and eager to read as many agile books as I possibly could, and seek out the Agile speakers. Go to Agile conferences. What I'm discovering is that over time for Our agile adoptions to move into Agile transformations to move into organizational transformation. I'm being pulled to seek new guidance back to the talk for this evening. Tell me why and the golden the Golden Circle of Agile. When I saw the TED Talk by Simon Sinek, let's start with I was watching TED Talks. What I've been doing that five years ago. No, is Simon's talk about agile. No. But I listened to it multiple times, and took my own interpretations around it. They're not specifically what Simon says, oh, that sounds funny. Sorry. And then I bought his book, start with why. And it gives so much wonderful humanity underneath this thing called the Golden Circle of why, how what. And I said to myself, that really speaks to me. And it falls in line with some other authors and their books that I've been looking at, again, to broad the value of Agile to reap more benefits of Agile. They're not agile books.Joe Krebs 16:24 You do want to you want to share them with the Agile New York City community, what's on your bookshelf right now? What do you what are you interested in?Jean Tabaka 16:30 Actually, you know, oddly enough, what's more, well, yes, I have a bookshelf full of books. But, okay, this is a little bit of a nod to the Kindle. Because I love these books so much, I bought a Kindle, so I can carry them with me wherever. And, frankly, seriously, I use a Kindle as my library, as my reference library. So if you come through what I have on there, you'll discover every one of these books, I think that one of the biggest influences on me with regard to being a change agent, and therefore someone who believes in Agile transformation has been Seth Gordon. And admittedly, I haven't read all his books. But I would say this was a transformative book for me, and it's linchpin. I don't know if you've read that one, it blows me away. And it he talks about being prepared to bring your gifts and your artistry into your work. And I was thinking about how agile asks so much of us, and that our organizations deserve and should value our gifts and our artistry, I think agile invites that but it never really used those words. And he also says that we with our sense of artistry should be prepared to lean in to do hard things. And as we lean in a true artist chips, there are a couple of other things, he adds him with that. But I'd have to pull up my library to tell you this. Boy have those meant a lot to me with regard to talking about what Agile and how we as individuals work within an Agile transformation, and how an organization should be inviting our artistry and our gifts should help us lean in and ship. A book very similar to that. Daniel Pink's drive, and that has a lot to do with how intrinsic motivation is far more compelling for individuals and teams than extrinsic rewards, or extrinsic. Punishment is too strong a term but if you don't get this done, then you're in trouble. So you have to go into this depth tomorrow. Yeah. Wow, another book, I've been doing a lot. I've been going back to time and time again. And in fact, excuse me. Pardon me, I'm using sort of my metaphor for the year is Dan Heath and Chip his book switch. Again, nothing to do with agile, but has to do with when we're prepared to preparing to be transformative, and they have three metaphors there which are, drive the rider so set a vision, motivate the elephant, which is look into the emotions and the heart of what it takes to go to transformation and then shape the path so ensure that that can occur. And again, I think about Wow, all these things I care passionately with regard to agile, agile teams, agile organizations. I want to give these gifts to people about I get how hard it is. And we're worth we're worthy of what we can get out of that. And then a bit more technical.Joe Krebs 20:14 How do you fight broadening that scope? By looking into other industries? What do you what do you think is going to happen to our community? Or where would you like to see the Agile community? Getting stronger getting? Or emphasizing certain topics? Is there anything based on what you're seeing around? Yeah, John community?Jean Tabaka 20:39 I think I wouldn't be telling you anything new with this answer, but I'll give it to you.Joe Krebs 20:43 Please give it to me. You can decide.Jean Tabaka 20:46 And I believe the original agile movement, had a wonderful focus on how to help development teams deliver, and how to protect them from the tyranny that tended to surround them that held them hostage, in some ways. What I'm hopeful about with regard to reading these new things, and the way that I would invite them into agile communities, is that we are broadening, agile scope. And its focus, and inviting, and we're broadening both into the individual values, and our quality of life. And we're broadening out to the organizational view, and organizational quality of life. This is a hard sell, when I go talk to large organizations, they'll still look at the bottom line. And the reading I've been doing is that the bottom line will take care of itself sounds pretty Frou Frou, whatever the bottom line will take care of itself. When you really believe in the people. Every one of these books says believe in the people care and the people and these other things will take care of themselves. I've also been reading Don Reinertsen must be so I feel sorry. That's okay, I keep interrupting you. So.Joe Krebs 22:21 But that has to be true, right? Like a truthful. You believe in your people? I mean, it has to be, it has to be done right. From an organizational perspective. A lot of people say that it's just like I believe, just take care of your department and takes care of itself. Just focus on the customer. Or other say just focus on the employees, like whatever your viewpoint is. But some organizations try that. And it's still not successful, because they might not be really meeting it. But they're saying, right, yeah, so I guess there's a hidden agenda.Jean Tabaka 22:54 Yes, yes. And again, thinking about some of the things I've been reading in the agile and Google Groups, etc. And talking with organizations is I wonderfully I get paid to go talk with and listen to people. How did I get this lucky? And I hear that agile still puts them on Death Marches instead of one death march at the end. Now we have a death marked every two weeks. Yeah, let's sign up for Agile. And and they're under the Agile tyranny. Yeah, they're they're under some sort of tyranny of time box.Joe Krebs 23:33 So torture. Yeah, every two weeks. And that was not the intent. No, that's that's not the intent. Yeah.Jean Tabaka 23:39 And so as we're trying to do the right thing with agile, I think it's valuable for us to look outside of agile and say, Can we reinforce ourselves of what the intent was? And can we actually have it grow through our nurturing of the intent through these through these other guides?Joe Krebs 24:00 I do want to come back to something very, very tiny, narrow topics is meetings, you said, we already had focus we have created we have created where we are delivering software. So you're doing all these good things with agile but I still observe and I just wanted to ask you, obviously you're sharing this battle Holly, Holly, anyone meetings, meetings, Ali run any in any kind of shape, they run in an effective way? Do you have any advice for the listeners out there? I do like one tip or something, how to run meetings, a little bit more effectiveJean Tabaka 24:39 Habits of Highly Effective facilitator. Okay. And sometimes I think people are looking at me and saying, Well, Jean, when you see everything is a nail, yeah, your hammer is the right tool. I would like to use my company rally software as an example this coming August 1, I'm celebrating my eighth anniversary with the company. Thank you. And I was the first consultant hired into the company. Here I was writing a book I was hired in in 2004. I was writing a book on collaboration and facilitation specifically. We were very small group at the time. And I approached the CEO, Tim and the founder, Ryan, and said, I think we could really benefit from having facilitated meetings, Agile has so many meetings. And they said, Okay, ceremonies that Yeah, show us what you've got eight, seven and a half years later, we do not have any major meetings without a facilitator. We are an organization of facilitation. And this has not been through me pushing it on people. It has been through groups pulling it. This is not just the development teams, it's every department in the company. We have retrospectives, we have planning meetings. And we now actually have a facilitators group. And we check in with one another about what are you running into? What are some more things you've been reading besides genes, but we truly believe now we are a facilitation driven organization. And when I can bring that message into other organizations, because they say, agile is killing us there are too many meetings, then what I talked about with them is how effective are your meetings? What are you doing to ensure that they meet a purpose that they don't go on forever and ever, that they don't suffer from what I call LV di D? Yeah, loudest voice driven development, loudest voice decision making driven decisions. The facilitator is there to protect everyone and make sure everyone's heard and understood in a safe environment that I believe is truly critical to Agile. And that's why I think facilitation is a isn't great and necessary tool in the Agile set of tools.Joe Krebs 27:11 How do you see like social media networks, influencing the focus of today's meetings? Do you think that's like with Twitter, with Facebook with all these technical capabilities of instant messaging? Do you think that has any influence negatively on an agile project?Jean Tabaka 27:31 Well, what I can say is that being the one of the grandmothers out there, figure template inish, initially, I put push back very hard on no electronics in meetings, what I've come to believe more valuable is our intentions in meetings, and how electronic service services again, I'll just use my own company. But I've seen it in other companies, where we make agreements with one another at the start of a meeting, we declare our intentions, and the use of electronics. For instance, recently, we had a meeting where we wanted a colleague engaged. And so we just put her in Google Chat, turned in video chat and turned around and sat in a chair and major part of our meeting. In almost every one of our conference rooms, we now have very large high def, panel screens on the walls, so that we can have people in the meetings. And people will also say I need electrons, I need to have my electronics on because I need to stay in I Am. Part of it is so that we make decisions very quickly that we remove the waste of if someone's not in the meeting, we bring in their information to make decisions more informed and faster than waiting until outside the meeting. So theJoe Krebs 29:02 technology is related to the meeting itself to the Yeah, no, it's not like just chatting with somebody about something totally unrelated to the meeting. WeJean Tabaka 29:10 have meetings that still suffer from that. Yeah. And we as facilitators are learning how to check in with people about the agreements, the intentions and the norms. And I'll ask very specifically, who knows right now that they need to be in email. Okay. Yeah, email. Well, yeah, tell me that. Yes. I I have a burning issue that I need to be engaged in and therefore the rest of the group understands why that person is doing email and the others aren't. Yeah. And we still struggle with that.Joe Krebs 29:44 You said you started as a consultant with a rally Yes, but your title now is fellow keen on finding out what a fellow does for rally. Ah, tell me a little bit about Your day. What are how does a typical day of gene debate look like? What I would ColoradoJean Tabaka 30:06 in Boulder, beautiful Boulder, Colorado? Believe it or not, this is something of an emotional question and answer for me. I have loved my work as an agile consultant. I have loved and continue to love working with rally. It is the best job I've ever had in my 30 plus years in the technology community. Well, as the first consultant I help define what we would look like as consultants. One of the big things being we would be highly facilitated. When I moved into the role of agile fellow, the intention was, this is going to sound a little self serving that I would travel less travel less. But now you know something about that. What, what has been so deeply rewarding to be agile fellow is that I actually travel more. And it has to do with the fact that I read a lot more and I blog more. And I work with different levels, higher levels in organizations. And how we came up with the word fellow was we brainstormed and said we don't know what to call this. Let's just call it an agile fellow for now. But it's not an untypical definition. I didn't want to be called an agile thought leader. I thought that was pompous. And yeah, a bit assumptive. But I did want to be someone in the rally community and then in the community at large that where I made an intention of I'm here to share ideas and bring in as we talked about earlier, ideas that aren't even necessarily from agile books.Joe Krebs 31:55 What do you do to relax during boredom? I do try to get a feeling of what is are you scared? Are you ski?Jean Tabaka 32:02 Oh, well, I'm an extremely bad skier. But you ski Yeah. I just went skiing a couple of weeks ago and suffered about five major bruises all over my body and knocked my noggin my head pretty badly. I've broken a leg skiing. I skied into a tree two very badly sprained ankles. And then this two weeks ago, the worst bruises of my life. And I still get out there. It's so beautiful. Wow, I it is so beautiful.Joe Krebs 32:40 You're a skier in training. Claiming like, as we discussed earlier, we still feel like we're in graduate school. Yes, right. And you're stillJean Tabaka 32:50 I'll be in kindergarten as king. And I do love. The other thing about living in Boulder. I chose to live there 12 years ago. It's a beautiful place. There is a lot of entrepreneurship. There's a lot of sense of sustainability, and social impact and giving back to the community. And I've had the deep honor of being engaged with some of the social initiative clubs at the University of Colorado, and also helping with some of the entrepreneur programs. I'm helping set up an agile conference at the University in September. That may not sound like leisure. Okay, let's back off. When when you're passionate about your work, it bleeds back and forth. It really does.Joe Krebs 33:43 You know, it's like, what weekday is it and you will realize how I work on Sundays. But you don't feel it.Jean Tabaka 33:49 And I am trying to move away from so much of my reading, feeding into my passion about work. And actually this summer part of the rally program for having been at the company seven years, I'll be celebrating my anniversary. We get six weeks of sabbatical. So I'm intending to truly take six weeks completely away from my passion around agile.Joe Krebs 34:17 Will that be New York?Jean Tabaka 34:19 It's going to it's going to be in an undisclosed location in France, okay for four weeks of intense language immersion. And I have reasons for doing that which go back to Seth Gordon, and my need to lean in and ship.Joe Krebs 34:39 Awesome. With Thank you, Jean, thank you for your time here. It's been a delight prior to your talk. I just want to highlight that one more time. Tell me why they go in so called Agile we're gonna hear your talk later. At Pace University at our fifth anniversary. It's not a lot. Yay, but it's five years and it's good moment for us to reflect. And we're happy to have an amazing speaker like you onstage. And not only onstage, but also on the ground, actually where we have food, drinks and we can stay for some drinks. That's aJean Tabaka 35:13 hobby. That's food and drinks. Yeah. And music,Joe Krebs 35:17 drinks music, and so we have a good time. Thank you again.Jean Tabaka 35:22 Well, I'll tell you that again. Thank you so much. And thank you for inviting my topic about tell me why that is a passion of mine. I don't think I understood it back when I was an agile neophyte, and learning just how to work within teams. I now look at how passion drives us and should drive the organization. And as Simon Sinek would stay, I would say start with why and that's start with your passion and your vision. That's what I'll be talking about this evening.Joe Krebs 35:55 Thank you, Jean. Thank you so much. Bye bye.

In this episode, the conversation continues with Jutta Eckstein, an independent coach, consultant and trainer, based in Germany. In the first part, she shares-Her origin story as a product engineerTransition from an engineer to a coachThe importance of listeningWe continue the conversation with: In her initial explorations with organizations, one pattern she found isThe understanding for leaders to introspect and understand their own responsibilitiesThat it is not always only technical aspects, but also the social aspectsHow having a common purpose helps in aligning team members togetherAlso creates a better buy-in and the work she had done with Diana Larsen on the book liftoffHow she finds and manages time to do so many things - liking her job and what she does!Doing what she feels is importantThe advice she got from Alistair Cockburn - what is the maximum money you want to make in a year?Making time to help others, not for money, at least immediatelyHow she reconciles different perspectives she gets from her network - by keeping some ME time, doing yoga, exercises etc and not forgetting self careHer thoughts on sustainability - that is her current passion as the planet is on fireSocial, environmental and economic pillars Diversity, inclusion, accessibility, equity Carbon footprint, wasteHolistic picture of the product: is or product improving lives everywhere or in a limited areaThe carbon impact of products during their lifecycle is more during the usageHow to find a balance between consuming more computing resources and the carbon footprintSome career tips in the area of IT and sustainabilityJutta Eckstein works as an independent coach, consultant, and trainer. She has helped many teams and organizations worldwide to make an Agile transition. She has a unique experience in applying Agile processes within medium-sized to large distributed mission-critical projects. Jutta has recently pair-written with John Buck a book entitled Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy (dubbed BOSSA nova). Besides that, she has published her experience in her books Agile Software Development in the Large, Agile Software Development with Distributed Teams, Retrospectives for Organizational Change, and together with Johanna Rothman Diving for Hidden Treasures: Uncovering the Cost of Delay in your Project Portfolio.Jutta is a member of the Agile Alliance (having served the board of directors from 2003-2007) and a member of the program committee of many different American, Asian, and European conferences, where she has also presented her work. She holds a M.A. in Business Coaching & Change Management, a Dipl.Eng. (MSc.) in Product-Engineering, a B.A. in Education, and is trained as pollution control commissioner on ecological environmentalism.links: https://www.linkedin.com/in/juttaeckstein/ https://www.jeckstein.com/https://www.agilebossanova.org https://jeckstein.com/sustainability

Squirrel and Jeffrey meditate on Brian Marick's announcement that he will no longer accept talk invitations on agile development, and the (different) reasons that both of them still use term "agile". Topics include joy at work, how it leads to profit, and the "near enemy" of that joy, which can lead to disillusionment. SHOW LINKS: - Listener Poll Results: https://twitter.com/TShootingAgile/status/1478640273991294983 - Brian's tweet: https://twitter.com/marick/status/1499905649970397189 - Brian's article on things left out of the Agile Manifesto: http://www.exampler.com/blog/2007/05/16/six-years-later-what-the-agile-manifesto-left-out/ - Joy at Work: http://dennisbakke.com - Joy Inc: https://menloinnovations.com : Joy, Inc. - Near Enemies: https://www.theguardian.com/lifeandstyle/2014/jun/07/change-your-life-near-enemies-buddhism - Alistair Cockburn on the "death" of agile development: https://heartofagile.com/agile-is-not-dead-quite-the-opposite/ --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com

Rocío Briceño joins Agile World to chat about how Agility can solve social issues around the world. Social Impact Agile is a movement founded by Rocío Briceño with active participation by Alistair Cockburn and Gerardo Blizter. Learn while having fun and chat about Rocío's passion, vision and why she's running for Vice President of Costa Rica. Social Impact Agile https://en.rociobriceno.com/siagile LinkedIn https://www.linkedin.com/in/rocio-briceno/ #Agile_World #AgileWorld #Agile #AgileTalkShow #ProductManagement #ProductCulture #ProductDelivery Online Agile World Better English Website Agile World Better English LinkedIn AgileWorld.Better English Facebook Agile World Better English YouTube Agile World Better English Vimeo Hosts Jessey Drewsen Steve Moubray Big Thank You to Sabrina C E Bruce Karl A L Smith Agile World © 2021 Broadcast Media, Hollywood, California | Better English Content by Hosts --- Send in a voice message: https://anchor.fm/agile-world/message

The trillion dollar question for any organization I train or coach at is do story points provide any value? And if so, how do we benefit from the value accordingly? Learn what Ron Jefferies, Ken Schwaber, Jim Highsmith, Martin Fowler, and Alistair Cockburn had to say regarding the use and abuse of story points!

There's nothing more useless to a Product team than a big backlog.  Bringing backlogs to life - making them usable, relevant, and getting value from them - is something that transforms ordinary teams into extraordinary ones.  To guide us on how to do that, we asked Jeff Patton - creator of User Story Mapping - to join us on the podcast.Featured Links: Follow Jeff on LinkedIn and Twitter | Jeff's upcoming Training Sessions | Buy Jeff's book 'User Story Mapping' | Alistair Cockburn's book 'Writing Effective Use Cases'Give UserLeap a try for free by visiting UserLeap.com to build better products.

In this episode of the InfoQ podcast Charles Humble talks to Lucas Cavalcanti, a Principal Engineer at Nubank, which is the leading FinTech in Latin America and has become the most valuable digital bank in the world. They discuss Nubank's early architectural choices including starting with Clojure and microservices, the challenges of using public cloud for financial services in Brazil, Nubank's desire for immutable architecture and use of Alistair Cockburn's Hexagonal Architecture, and lessons learnt as the startup scaled. Read a transcript of this interview: https://bit.ly/3m6wXMQ Subscribe to our newsletters: - The InfoQ weekly newsletter: bit.ly/24x3IVq - The Software Architects' Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/ Upcoming Virtual Events - https://events.infoq.com/ InfoQ Live: https://live.infoq.com/ - August 17, 2021 - September 21, 2021 - October 19, 2021 QCon Plus: https://plus.qconferences.com/ - November 1-5, 2021 Follow InfoQ: - Twitter: https://twitter.com/infoq - LinkedIn: https://www.linkedin.com/company/infoq/ - Facebook: https://www.facebook.com/InfoQdotcom/ - Instagram: @infoqdotcom - Youtube: https://www.youtube.com/infoq

Squirrel explains how a telephone emoji helped a coaching client and we discover how codewords help build trust. SHOW LINKS: - Code words tweet: https://twitter.com/douglassquirrel/status/1421016370850971650 - Alistair Cockburn communication graph: p. 6 of https://alistair.cockburn.us/wp-content/uploads/2018/02/A-concise-theory-of-software-development-in-pictures.pdf - Schwarz, Eight Behaviours for Smarter Teams: https://cdn.csu.edu.au/__data/assets/pdf_file/0008/917018/Eight-Behaviors-for-Smarter-Teams-2.pdf --- Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@conversationaltransformation.com

Our friends at CITCON help us think about why we feel like we're covering the same agile lessons over and over, like breaking epics down into very small stories. An analogy to teaching long division turns out to be surprisingly helpful. - CITCON: https://citconf.com/ - Moore, Crossing the Chasm: https://en.wikipedia.org/wiki/Crossing_the_Chasm - Chris Matts, community of needs: https://snowbirdcollaboratory.org/community-of-needs/ - Alistair Cockburn: https://alistair.cockburn.us/ Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@conversationaltransformation.com

Tony and Craig are at Agile Australia in Melbourne and they (finally) catch up with Martin Kearns, the Chief Digital Officer at Innodev and co-organiser of Scrum Australia, and they chat about: Alistair Cockburn gets mentioned at around the 2:30 minute mark, and Martin was responsible for first bringing him to Australia Being coached is … Continue reading →

We look at two elements - Collaboration and Reflection - of the Heart of Agile approach developed by our friend Alistair Cockburn, and illustrate how conscious and attentive listening and reflection on emotions make a big difference for agile teams. SHOW LINKS: - Motherhood and Apple Pie: https://hotidioms.com/2012/02/21/motherhood-and-apple-pie/ - Collaboration Cards: https://www.collaborationcards.com , https://web.archive.org/web/20170621140230/http://alistair.cockburn.us/Collaboration+Cards - Collaboration Cards article: http://static1.1.sqspcdn.com/static/f/702523/26767147/1451886700677/201601-Cockburn.pdf?token=oTGZ9syVsnh4d%2BtW8ggVolCglEM%3D - Collaboration Cards course: https://www.heartofagile.academy/courses/using-collaboration-cards - Shu Ha Ri: https://martinfowler.com/bliki/ShuHaRi.html - Thanks for the Feedback: https://www.goodreads.com/book/show/18114120-thanks-for-the-feedback - Previous episode: https://soundcloud.com/troubleshootingagile/alistair-cockburn-heart-of-the-heart-of-agile --- Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@conversationaltransformation.com

We look at two elements - Collaboration and Reflection - of the Heart of Agile approach developed by our friend Alistair Cockburn, and illustrate how conscious and attentive listening and reflection on emotions make a big difference for agile teams. SHOW LINKS: - Heart of Agile tweet: https://twitter.com/TotherAlistair/status/1312407646364991489 - Alistair Cockburn: https://en.wikipedia.org/wiki/Alistair_Cockburn - Conversational Dojo kit: https://itrevolution.com/build-agile-conversations-with-conversational-dojo-webinar/ - Active Listening: https://en.wikipedia.org/wiki/Active_listening - London NVC Meetup: https://www.meetup.com/Nonviolent-Communication-NVC-London/ - London Organisational Learning Meetup: https://www.meetup.com/London-Action-Science-Meetup/ - Ladder of Inference: https://soundcloud.com/troubleshootingagile/a-sense-of-security-gained-lost - Above the Line: https://soundcloud.com/troubleshootingagile/walking-the-line-emotional-unawareness --- Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@conversationaltransformation.com

În episodul 7 vorbesc despre ”Artiști și Specificatori”, o activitate-joc dezvoltată și descrisă de Alistair Cockburn pentru conștientizarea comportamenetelor agile. Youtube: https://www.youtube.com/watch?v=WkmbEvcAwQs (Gestionarea Proiectelor Software | S1E07 | "Artiști și Specificatori")

Alistair Cockburn is one of the co-authors of the Agile manifesto! We talk about methodology and how often the culture is missing in them. Why is that the case? Why are we so focused on structure in general? We also talk about Heart of Agile, SAFe, writing the manifesto, Crystal Clear and much more! 

Tony, Renee and Craig speak to Alistair Cockburn and Soledad Pinter about the newly launched Heart of Agile Academy: The Heart of Agile Academy is the opportunity to reset Agile learning with a clean sheet of paper The core design decisions were to remove the classes being tied to a title and to be better … Continue reading →

In this Episode, Diana joined Shahin to talk about Agile Fluency and other related topics. We conversed about and around the following topics: Agile Fluency® Model (Resources, Community & Game); and it's reference Language Fluency  Group coaching compared to Individual coaching Retrospective Facilitator Gathering & Open Space Technology Continuous Learning & Continuous Improvement; Advice and Tools for newer people to Agile Coaching in the Zones & Improvement Kata We referred to and/or mentioned the following people: Rebecca Wirfs-Brock - Linda Rising - Esther Derby - Klaus Leopold (LeanOnAgile Show with Klaus) - Joshua Kerievsky - Ward Cunningham - Norman Kerth - Allison Pollard - Alistair Cockburn - Ron Jeffries - Arlo Belshee - Martin Fowler - James Shore We cited the following resources: By Diana & Co-Authors: Agile Retrospectives: Making Good Teams Great (Amazon US - Amazon CA) Liftoff: Start and Sustain Successful Agile Teams (Amazon US - Amazon CA) The Five Rules of Accelerated Learning (LeanPub) By Other Authors: Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy: Survive & Thrive on Disruption - Jutta Eckstein & John Buck (Amazon US - Amazon CA) Project Retrospective: A Handbook for Team Reviews - Norman Kerth (Amazon US - Amazon CA) Love is Letting Go of Fear - Gerald Jamposky (Amazon US - Amazon CA) Checklist Manifesto - Atul Gawande (Amazon US - Amazon CA) For more details please visit http://podcast.leanonagile.com. Twitter: twitter.com/LeanOnAgileShow  LinkedIn: linkedin.com/company/lean-on-agile

El referente mundial en el desarrollo de ingeniería del software y uno de los creadores del Manifiesto Ágile nos comparte su experiencia sobre El Corazón de la Agilidad, y sintetiza dos décadas de prácticas en cuatro críticos verbos imperativos que amplifican la efectividad: colabora, entrega, reflexiona y mejora.

Tony and guest host Phil Gadzinski talk to Alistair Cockburn for a brief overview and understanding about the Heart of Agile (and the link to how it all started in Australia): Scrum training had turned into training wheels and consistency – wanted to get back to the essence of Agile Progression from shu (follow techniques), … Continue reading →

What is your tribe? Have you identified the group of people that you work effectively with? Has your organization learned to bring the work to the people or are you still bringing the people to the work? Listen to this episode to hear Brad Hugick and Steven Fullmer discuss the nuances of Agile, Neurosociology and Project Management.What a way to start off 2020 and Season 3 with an engaging and thought-provoking discussion. Brad is an Enterprise Coach and shared several tools, techniques and tips from his career journey. If you’re planning or in the middle of an Agile Transformation this is a must listen to episode. Brad provided several real world, practical solutions he’s gathered during his career from Alistair Cockburn, Influential Books, and personal experience.Steve connected the Agile topics to Neurosociology. As a repeat guest, he continued to share his vast knowledge of how and why we think and behave as individuals and in teams. It is quite thought provoking to hear the connection Steve can make between Brad’s experiences and the science of how our brain works. This was a great show to kick-off Season 3 allowing leaders in our industry a platform to share their story!Tune in for upcoming shows with Project Management leaders and subscribe to the podcast on Apple Podcast, iHeartRadio, Spotify, Spreaker, Stitcher,or your favorite podcast platform!Thanks to our sponsor THE PMO SQUAD. Visit www.thepmosquad.com to learn about the Purpose Driven PMO and all their project management services.

Pour voir la version vidéo : https://youtu.be/iiPbhCxvSNc ----- Scrum Life a eu l'immense honneur d'interviewer Alistair Cockburn lors d'Agile Tour Lille 2019 pour parler de ce qu'est réellement le mindset agile. L'occasion pour lui d'introduire Heart of Agile (coeur de l'agilité en français). Découvrez-en plus dans la description ci-dessous

Alistair Cockburn gets us thinking about how agile methods are spreading, even to non-software teams like sales. Further, we bring in the idea of Wardley Mapping to see how, ironically, this very spread can lead to the conclusion that agile development is headed for the dustbin, but conclude (phew!) that agile methods have a healthy future. Apologies for a minor audio problem about 12 minutes in. SHOW LINKS: - Alistair Cockburn says Agile isn't dead: https://heartofagile.com/agile-is-not-dead-quite-the-opposite/ - Moore, Crossing the Chasm: https://en.wikipedia.org/wiki/Crossing_the_Chasm - Sheridan, Joy, Inc.: https://www.amazon.co.uk/Joy-Inc-Built-Workplace-People/dp/1591847125 - Wardley Maps: https://www.slideshare.net/swardley/an-introduction-to-wardley-maps - Previous episode on Agile beyond software: https://soundcloud.com/troubleshootingagile/agile-outside-software-teams - Heresy.io: https://heresy.io/ *** Our new book, Agile Conversations, will be out in May 2020! See https://itrevolution.com/book/agile-conversations/ and get ready to pre-order! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Mais um episódio no Agile Brazil! Dessa vez nosso convidado é o Alistair Cockburn, que vai contar um pouco pra gente sobre o coração do movimento ágil. Confira agora no Enzimas! Mande a sua pergunta/dúvida por áudio ou escrito para o Whatsapp 31 996977104 ou no email osagilistas@dtidigital.com.br que responderemos no programa!

The engineers know the project is in terrible trouble, but the executives think it's going great. This "greenshifting" anti-pattern occurs at NASA, software companies, and everywhere in between. We tell a few related stories, including a fable, and suggest methods that might work to counteract the greenshifting tendency in your organisation. SHOW LINKS: - "The Mushroom Song" by Steve Savitsky: http://steve.savitzky.net/Songs/mushroom/ - The SNAFU Principle (communication fable) from the Jargon File: http://skeptictank.org/files//cowtext/jargn10.htm - Appendix F on the Challenger disaster, by Richard Feynman: https://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt - Scott Ambler on Greenshifting: https://www.drdobbs.com/dr-dobbs-agile-newsletter/191600661 - Alistair Cockburn on information radiators: http://www.informit.com/articles/article.aspx?p=24486&ranMID=24808 - Brian Marick on lava lamps as build status indicators: https://gist.github.com/marick/3ec112bc38b2af267e15 *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

April Wensel on Software Developer’s Journey, Arup Chakrabarti on On Call Nightmares, Alistair Cockburn on Being Human, Brian Balfour on Product To Product, and Kent Beck on Unlearn. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting May 13, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. APRIL WENSEL ON SOFTWARE DEVELOPER’S JOURNEY The Software Developer’s Journey podcast featured April Wensel with host Tim Bourguignon. April talked about hiring for attitude and mindset over the technical skills of the moment. She distinguished between the fixed and growth mindset and talked about how hearing a statement from an interviewee like, “I’m just not good with people,” is a sign that the person is currently thinking with a fixed mindset. Tim asked her to describe her company, Compassionate Coding. At Compassionate Coding, April teaches workshops on emotional intelligence to technical people. These skills are often called “soft skills,” but she prefers to call them “catalytic skills,” because they help technical people catalyze the application and acquisition of their other skills. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/45-april-wensel-encourages-us-to-get-in-touch-our-core/id1079113167?i=1000434465519 Website link: https://www.buzzsprout.com/190346/982475 ARUP CHAKRABARTI ON THE ON CALL NIGHTMARES PODCAST The On Call Nightmares podcast featured Arup Chakrabarti of PagerDuty with host Jay Gordon. Arup talked about starting out in medical research and being exposed to the notion of on call because much of the research involved having access to cadavers that were only available in short time windows that required him, from time to time, to drive to the hospital on a Saturday night. At Amazon, Arup learned what it looks like for not just individuals to go on call, but for whole departments and companies to go on call. At Netflix, he worked with the “father” of Chaos Monkey and managed site reliability as Netflix built out the simian army. He told a story about a NTP time drift that alerted almost every team at PagerDuty. The SRE on call quickly diagnosed the problem as NTP, but their run list was broken, so getting things back took a while. During this time, Arup had to keep the engineers from disabling these constantly-firing alerts because that could have caused them to miss something critical. He says this incident taught him that incident response is a team sport. This led to a discussion about the importance of keeping things light during an incident and taking the issue seriously without taking yourself seriously. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/episode-21-arup-chakrabarti-pagerduty/id1447430839?i=1000436439951 Website link: https://www.podomatic.com/podcasts/oncallnightmares/episodes/2019-04-25T04_08_18-07_00 ALISTAIR COCKBURN ON BEING HUMAN The Being Human podcast featured Alistair Cockburn with host Richard Atherton. Alistair talked about doing his Ph.D, being able to put the word “people” in the title of his dissertation (apparently a rare thing in academia), and how his heart sank when he realized that his own mentor’s dissertation on methodologies had already covered everything. Then he realized that if it really had covered everything, you could take it to any business in the world and it would solve their problems, but it doesn’t because businesses are made of people and no single methodology can solve all of the problems. Alistair says instead that methodologies and processes should be like tissues: you use them and throw them away. After two or three months, you have to change. He says there are some good things about process, one being that it provides a checklist, like that which a pilot and copilot run through before an airplane takes off. Often though, he says, processes are like drop boxes. You create them so that people don’t have to talk to each other. Companies that have communication problems often want Alistair to create a process for them to resolve those communication problems, unaware of the contradiction. Alistair often has the same advice regardless of the methodology a client has chosen. If a client says, “We do SAFe,” he says, “That’s fine, increase collaboration!” If a client says, “We refuse to do SAFe,” he says, “That’s fine, increase collaboration!” He also says he doesn’t have to teach collaboration because everyone already knows how. We just don’t want to.  Apple Podcasts link: https://podcasts.apple.com/ca/podcast/56-the-heart-of-agile-with-alistair-cockburn/id1369745673?i=1000435504887 Website link: http://media.cdn.shoutengine.com/podcasts/4081235a-554f-4a8f-90c2-77dc3b58051f/audio/afdb129e-9fcb-40e4-9243-b85f56f3e1b5.mp3 BRIAN BALFOUR ON PRODUCT TO PRODUCT The Product To Product podcast featured Brian Balfour with host Eleni Deacon. They talked about north star metrics, that is, having one metric that attempts to capture all of the most important dimensions of your business. Brian doesn’t believe you can capture this in one metric and instead prefers a constellation of metrics that includes: 1) a retention metric such as monthly/weekly active users, 2) an engagement metric that measures the amount of engagement and the trend over time for those active users, and 3) a monetization metric. He particularly doesn’t like revenue metrics because of their lagging nature and how they ignore actual usage. Being on a data engineering team myself in my current role, I liked what Brian had to say about how to approach data. He says companies need to take on the mentality that data is not a project with a start and end date, but a core part of building product that is meant to constantly evolve. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/north-stars-are-leading-you-astray-brian-balfour-reforge/id1293415837?i=1000436155421 Website link: https://omny.fm/shows/product-to-product-podcast/north-stars-are-leading-you-astray-brian-balfour-r KENT BECK ON UNLEARN The Unlearn podcast featured Kent Beck with host Barry O’Reilly. Barry asked about the system that Kent uses to help him explore uncertainty. Kent says he has habits that help. The first habit is that of reversing any sentence that begins with the word “obviously.” When somebody says, “Obviously, programmers can’t be trusted to test their own code,” he automatically thinks, “What if that’s not true?” A second habit is whenever somebody introduces Kent to a new model of thinking, he asks himself, “What would happen if I just acted like this model was true?” and he says that he applied that habit when reading Barry’s book Unlearn. Barry asked about what made Kent feel that the Test-Commit-Revert (or TCR) technique was worth exploring, since this required an unlearning of Kent’s own Test-Driven Development (or TDD) method. Kent says that he was disenchanted with asynchronous code reviews and used a third habit of looking further forward. During his tenure at Facebook, he experienced growth in the number of engineers from 700 to 5,000. At the time, people were anticipating the problem of having 10,000 engineers working together, but Kent followed the Bill Joy idea of looking six steps further, and looked into how 100,000 engineers would work together. His solution was Limbo, or asking “How low can you go?” to shrink the size of code that can be safely committed and put immediately in production and the TCR technique came out of that line of thinking. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/exploring-uncertainty-with-kent-beck/id1460270044?i=1000436242318 Website link: https://barryoreilly.com/unlearn-podcast/ FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/channel/UCysPayr8nXwJJ8-hqnzMFjw Website:

“We are now in the ‘post-Agile’ age…the explorers and innovators have moved on.” So says our very special guest, co-creator of the Agile Manifesto, Dr. Alistair Cockburn. In this inaugural episode of Agile on the Edge we explore post-Agile frameworks and techniques, including Heart of Agile and Solution-Focused Agile.

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this episode, I explore 'The Heart of Agile' approach with Agile Manifesto co-author and methodology theorist Alistair Cockburn. We talk:- How methodologies are like tissues- The paradox of needing methods to both increase and reduce communication- Why collaboration is at the heart of the Agile approach- The three emerging modes of leadership in complex work- The story of creating the Agile ManifestoEnjoy!https://heartofagile.com/

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this episode, I explore 'The Heart of Agile' approach with Agile Manifesto co-author and methodology theorist Alistair Cockburn. We talk:- How methodologies are like tissues- The paradox of needing methods to both increase and reduce communication- Why collaboration is at the heart of the Agile approach- The three emerging modes of leadership in complex work- The story of creating the Agile ManifestoEnjoy!https://heartofagile.com/

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this episode, I explore 'The Heart of Agile' approach with Agile Manifesto co-author and methodology theorist Alistair Cockburn. We talk:- How methodologies are like tissues- The paradox of needing methods to both increase and reduce communication- Why collaboration is at the heart of the Agile approach- The three emerging modes of leadership in complex work- The story of creating the Agile ManifestoEnjoy!https://heartofagile.com/

The agile principles talk about empowerment and autonomy, but do we have to make a complete switch from our current centralised-decision culture to a fully autonomous one? The Satir curve, six thinking hats, and a theory of Tic Tac change (really!) from Jeffrey and Alistair Cockburn, shows us a way to make a series of small changes rather than one big shift. SHOW LINKS: - Theory X and Theory Y: https://en.wikipedia.org/wiki/Theory_X_and_Theory_Y - The Uncanny Valley of A Functional Organization: https://stratechery.com/2013/the-uncanny-valley-of-a-functional-organization/ - Satir curve (J-curve): http://dhemery.com/articles/managing_yourself_through_change/ - Tic Tac presentation (Fredrick/Cockburn): http://blog.jeffreyfredrick.com/wp-content/uploads/2008/07/sdbp06tictactalk.pdf - Six Thinking Hats: https://en.wikipedia.org/wiki/Six_Thinking_Hats *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

In dieser Episode der Burndown Chart gehts es um Agilität. Ich erkläre, was ich unter dem Begriff Agilität verstehe. Hierzu benutze ich das Modell "The Heart of Agile" von Alistair Cockburn. Das Modell findet ihr hier : https://heartofagile.com/expanding-the-diagram/ . Ich wünsche euch viel Spaß! Marc

Today's episode features Kai Haley, Lead of Design Relations and the Sprint Master Academy at Google. We talk about design sprints and building a “sprint culture” as well as a much bigger question: The need for ethics in design. If you can build anything, faster, it's a kind of super power. And with great power comes great responsibility. While you might have heard Spider-Man say that, it also made me think of my favorite Plato's Dialog, Gorgias, which points out that power without knowledge of good (and evil) is pretty dangerous. Kai believes that training a sprint master means giving them the tools to keep people honest and mindful of their choices. What I really love about this episode is how open, honest and humble Kai is about how hard this work is. The Sprint can make it seem like solving big challenges is simple – all you need is five days and Google's list of activities – widely available on the internet! (and in the show notes!) But Kai makes it clear that any attempts to “copy & paste” the Sprint (just like any new way of working) into an organization will experience some turbulence. Adopting a new way of work can create a wave of change that will ripple out into the organization. To find sustainable success means changing rewards and recognition practices, building training and management support and lots and lots of flexibility and patience. We don't get into the basics of the design sprint in the interview so I'll say a few words of background. A design sprint is a structured process for getting a group of people to get together and make a big decision in a shorter—than—normal period of time. Sprints are a general term in use in Agile software development for some time and they have become really popular in the digital product design world as User Experiences Designers have had to contend with the spread of Agile in the world. In the last few years Google has developed an approach to design sprinting that blends parts of design thinking and parts of Agile into a powerful structure; building a clear, compelling narrative thread in the process. Inside Google, sprinting has developed into a key part of their culture, and the world is starting to take notice – starting with the NY Times bestselling book “Sprint” by former Google Ventures employees Jake Knapp and John Zeratsky who took their own unique flavor of the Sprint and wrote a clear, thorough, check-list approach to the method that made it seem simple enough for anyone to try. While it's often shorter inside Google and other organizations, the canonical structure is a five-day workshop that opens up a key challenge for a group or a company, explores several options to solving it and closes the loop with user research. Often workshops (that people like me run) *can* wind up feeling like Innovation Theater. Workshops can help teams get clear on a strategy and excited about big ideas. But those ideas can fade once the workshop ends. The ideas and the excitement get lost inside the organization. People who weren't there can question the validity of the ideas and power of their shared conviction. The Sprint format helps a workshop gain momentum and power though a key difference from the average workshop. For Kai, the key distinction between a workshop and a sprint is that a sprint develops a prototype and puts it in front of customers to get feedback on a key idea. A sprint helps end debate with evidence – and helps continue the conversation long after the workshop. The Sprint makes use of the Conversation OS in some interesting (and totally unintentional) ways – pulling on a few key levers of conversation design:  The cadence of work is sped up to force a decision and to create positive pressure, all while holding the work within a clear and powerful narrative thread. The visual map of the 5—day process helps get teams bought in on the power of working this way, establishing clear goals and agreements – regardless of how tough the middle of the week-long workshop gets, there are customers being recruited to test out the ideas, making it harder to give up and loose momentum! Pair this episode with a few others for a ricjer perspective on thes issues: - Dee Scarano, who's a Design Sprint Trainer and Facilitator at AJ and Smart, for more background on the sprint and being an awesome facilitator -Alistair Cockburn, one of the original Agile Signatories, if you're new to agile or want to go deeper into it -Daniel Mezick, who uses a unique, open-space approach to bring agile practices into organizations at scale You can find links for all of this and more in the show notes! Thanks for listening! Enjoy the show…and if you do, please take a moment and leave a review on iTunes. Google Sprint Kit https://designsprintkit.withgoogle.com/ GV Sprint on Medium https://medium.com/@gv.com Sprint Stories on Medium https://sprintstories.com/ The Sprint Book https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/1442397683 Plato's Gorgias https://www.sparknotes.com/philosophy/gorgias/summary/ Gransfors Bruk Axes: We have unlimited responsibility for Total Quality. https://www.gransforsbruk.com/en/about/corporate-responsibility/ Changing the Conversation with Sprints https://medium.com/google-design/changing-the-conversation-with-design-sprints-3ba776145468 The Conversation OS Canvas http://theconversationfactory.com/downloads/  Everyday Design Sprints with Dee Scarano http://theconversationfactory.com/podcast/2018/8/3/everyday-design-sprints-dee-scarano-aj-smart Agile and Jazz Dialog with Alistair Cockburn http://theconversationfactory.com/podcast/2017/7/19/alistair-cockburn-on-the-heart-of-agile-jazz-dialog-and-guest-leadership Agile as an invitation to a game with Daniel Mezick http://theconversationfactory.com/podcast/2017/6/23/dan-mezick-on-agile-as-an-invitation-to-a-game

In this week's Podcast we're on to the penultimate Agile Principle, number 11: 'The best architectures, requirements, and designs emerge from self-organizing teams.' Amongst much more, we discuss: -How what should actually constitute a team is the sharing of a problem, not a manager. -The importance of employing a dynamic team approach, rather than a static one, to solving problems. -How the unique specificity of this principle is designed to get us away from the old 'phase' approach and avoid costly hand-offs. -Specific techniques to inspire a mutiny and become a self-organizing team, with some lessons from Stephen Bungay's 'The Art of Action', such as how to employ Direct Opportunism. -The Spotify model and the importance of shunning the easy route of adopting an off-the-shelf model. *** SHOWNOTES: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -Alistair Cockburn's mighty fine Koan for Agile development: "Management tells the workers to mutiny. The workers refuse" http://alistair.cockburn.us/Self-organization+means+mutiny -Stephen Bungay's brilliant book, 'The Art of Action': https://www.amazon.co.uk/Art-Action-Leaders-between-Actions/dp/1857885597/ -The unique case of the General Electric plant in Durham, North Carolina: http://www.fastcompany.com/magazine/28/ge.html -Spotify's self-organised teams, not an off-the-shelf model to copy: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ -Sign up to CITCON in Vienna, there aren't many spaces left: http://citconf.com/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

I describe an important lesson I learned from Alistair Cockburn, one of the "founding fathers" of the Agile Manifesto and movement, that still sticks with me today.

We're on to Agile Principle 10 this week: "Simplicity - the art of maximizing the amount of work not done - is essential." In comparison to the dark old days when the Agile Manifesto was written, the way projects are simplified and broken down seems a huge improvement. But simplicity plays an essential role in achieving the all-important first Agile Principle of "satisfying the customer through early and continuous delivery of valuable software," so Squirrel and Jeffrey discuss why this principle is still so important today. They discussed: -How simplicity asks you to exercise discipline and restraint. -How Elephant carpaccio helps to provide an environment in which that restraint is easier. -How simplicity is not just a call for businesses to restrain themselves in their demand for features, but for developers to restrain themselves in their demand for best practices- and how they can employ YAGNI instead. -What YAGNI is. -How to build a whole application's worth of software without actually writing any software. *** SHOWNOTES: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -Alistair Cockburn's brilliant Elephant Carpaccio lesson: http://alistair.cockburn.us/Elephant+carpaccio -What is YAGNI?: https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it -Zapier: https://zapier.com/ -IFTTT: https://ifttt.com/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

It's Episode 9 of the Troubleshooting Agile podcast! This week we're discussing Agile Principle 7: "Working software is the primary measure of progress." Some of the topics we cover are: -The importance of "moving past the 'phase model' or the 'percent-of-budget model'" in measuring progress. -How Burn-Up/Down Charts simplify and optimise the process of measuring progress by assigning value only to that which provides value to the customer. -And how they also build trust between the business and software development sides of a company by delivering regularly. -The dangerous pitfall of taking Agile Principal 7 too literally and finding yourself toiling away in a Feature Factory. -How to avoid this pitfall by motivating your team with Type Y Management - perhaps taking inspiration from Star Trek's Jean-Luc Picard - and focussing on Business Outcomes. -That an unexpected outcome of focussing on 'working software' is often less software. 'But the software you end with, you know works. And you know it matters.' ** LINKS: -The 12 Agile Principles - http://agilemanifesto.org/principles.html -An extract from Alistair Cockburn's brilliant Crystal Clear: A Human-Powered Methodology for Small Teams on Earned-Value and Burn-Charts - http://alistair.cockburn.us/Earned-value+and+burn+charts -Mary and Tom Poppendieck's brilliant book on Lean Software Development - https://www.amazon.co.uk/Lean-Software-Development-Agile-Toolkit/dp/0321150783 -John Cutler's blog on how to tell if you're working in a Feature Factory - https://hackernoon.com/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2 *** We'd love to hear any thoughts, ideas or feedback you have regarding the episode. You can email us, here: agile@troubleshootingagile.com Tweet us, here: twitter.com/TShootingAgile Or find our website, here: troubleshootingagile.com/ Also, here is a link to our iTunes: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2 If you have a moment, please like, subscribe and share with your friends. We really appreciate it.

In Episode 8 of Troubleshooting Agile it's Agile Principle 6: "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation." A few of the things we discuss: -The pros and cons of different communication channels. -Looking at Alistair Cockburn's book "Agile Software Development", why micro-gestures and physical interaction make face-to-face communication so much richer. -Why we need to remember that "a Story Card is a promise for a conversation". -The origins of CRC Cards back in the 90, and their real value as a conversational tool and in building a shared understanding. -How effective communication also increases the effectiveness of isolated reflective thought. -How to apply this principle effectively to distributed and remote teams. -"Don't measure your software productivity by linear feet of documentation on the shelf." *** LINKS: -Chapter 3 of Alistair Cockburn's Agile Software Development: http://alistair.cockburn.us/ASD+book+extract%3A+%22Communicating,+cooperating+teams%22/v/slim -Alistair's Richness of Communication graph: http://alistair.cockburn.us/get/2287 -Alistair on coining "A story card is a promise for a conversation": http://alistair.cockburn.us/Origin+of+user+story+is+a+promise+for+a+conversation -CRC Cards: http://www.extremeprogramming.org/rules/crccards.html -Jeff Bezos's Management Tool for Self-Discipline: http://blog.idonethis.com/jeff-bezos-self-discipline-writing/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the episode. You can email us, here: agile@troubleshootingagile.com Tweet us, here: twitter.com/TShootingAgile Or find our website, here: troubleshootingagile.com/ Also, here is a link to our iTunes: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2 If you have a moment, please like, subscribe and share with your friends. We really appreciate it.

In episode 5 of Troubleshooting Agile we discuss the Third Agile Principle: 'Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.' Evolution in our thinking, since the Agile Manifesto was written back in 2001, makes what was once considered 'shorter timescales' seem laughable now, but, when retrospecting, 'working software frequently' remains one of the core agile disciplines. But, as Squirrel and Jeffrey highlight through various client stories, it is far from easy to implement continuously. We hear where, why and how so many companies fail to fully employ this principle, and Squirrel and Jeffrey discuss some interesting techniques to overcome common problems - from slicing up elephant carpaccio to employing continuous integration with nothing more than a rubber chicken. *We apologise for a few sound difficulties at the start of the episode with Jeffrey's mic. Stick with it and they soon pass.* *** Squirrel and Jeffrey have told us which common obstacles they regularly witness that prevent organisations from delivering working software frequently. Now we want to hear from you guys on the matter. You can leave your answers in the comments below, you can email us at agile@troubleshootingagile.com, or you can find a poll on our Twitter feed @TShootingAgile. What are the obstacle for your organisation to delivering working software frequently? 1. The tech team aren't offering to do this, or don't know how. 2. Customers (external or internal or both) don't know it's possible or how to use it if offered. 3. Both 1. and 2. 4. Neither - we already deliver frequently! *** SHOWNOTES: -Agile Manifesto Principles - http://agilemanifesto.org/principles.html -Continuous Delivery, by Jez Humble and David Farley - https://martinfowler.com/books/continuousDelivery.html -Continuous Delivery - https://continuousdelivery.com -CITCON - https://citconf.com -James Shore's blog: "Continuous Integration on a Dollar a Day - http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html -Alistair Cockburn's blog: "Elephant Carpaccio" - http://alistair.cockburn.us/Elephant+carpaccio *** We'd love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else for that matter). You can email us, here: agile@troubleshootingagile.com Or send us a tweet, here: twitter.com/TShootingAgile Or you can find our website, here: troubleshootingagile.com/ Also, here is a link to our iTunes: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2 If you feel like liking, Sharing and/or Subscribing, we'd really appreciate it.

In the first of a few podcasts recorded in India, Devesh and I test Alistair Cockburn’s trampoline effect theory, we talk about how agile demand is causing the community to scale too quickly, why you should hire people who are agreeable and open minded rather than ‘agile experts’, and why agile transformation should all be … Continue reading "Episode 33 With Devesh Chanchlani" The post Episode 33 With Devesh Chanchlani appeared first on Why Agile Transformations Fail.

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,” has meme-ified Alistair, in ways oversimplifying who and what he is. But becoming a meme, he says, is crucial in order to have a greater impact. Alistair also shares his thoughts on Agile 2.0, what that means, and provides us with possibly our favorite quote for all of the Agile2017 conference: “Some people say that Agile is dead -- no, it’s just been incorporated into the bloodstream so you can’t see it”. Howard Sublett hosts at Agile2017 in Orlando, Florida. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com.Subscribe: bit.ly/SIQYouTube, bit.ly/SIQiTunes, www.solutionsiq.com/agile-amped/Follow: bit.ly/SIQTwitterLike: bit.ly/SIQFacebook

My conversation with Alistair Cockburn was Agile to the core! We revised our timeline and deliverable with a quick standup and got right into it: After all, Agile principle #2 is to welcome changing requirements, even late in development. To wit, I thought we had an hour, early on the call he asked for 20, tops! (Somehow I kept him on the line for 45, since I'm deft at conversational manipulation. And he was keen to keep it going, too.) Alistair quite the nomad, teaching Advanced Agile workshops all over the world. When he's not teaching, he might be dancing Tango in Argentina or brushing up on his French in Nice. But sometimes the location is too distracting, so he was holed up in Florida where he found a town that was *just* boring enough to allow him some time to get some work done. He was moving house unexpectedly the day we were slated to chat. I saw on Facebook that his AirBnB had a shag carpet and the humidity and mustiness mixed with a thick carpet was making him sick! I tried to give him an out, but he was adamant we do our conversation, even for only 20 minutes. His motto: Now is better than the future. One of the pleasures and inspirations of talking with Alistair is that he's a man who really lives his principles: Agile principle #10 is that "Simplicity--the art of maximizing the amount of work not done--is essential". You'll hear how Alistair tries to design his life to make this principle a reality! As I mentioned two episodes back with Daniel Mezick, around Open Space Agile Transformations, Agile is kicked around a lot in the consulting world, but my sense is that all of those people haven't actually read the Agile Manifesto! Alistair was one of the originators and signatories back in 2001, and it was a response to a broken way of working. But just like any ideology, it's come to be interpreted in alot of ways by a lot of people. It was fun to go back to the source! I really enjoyed Alistair disagreeing with my characterization of Agile as a Design for Conversations. But I see it that way: Agile designs for some conversations and  not for others. And in fact, Alistair has a lot in common with Dave Gray, who I interviewed a few months back: Dave wondered about who has the right to design a conversation and if it can be overdesigned! Alistair is a proponent of Guest Leadership...that making space for momentary, voluntary leadership can powerfully transform work and teams. Alistair and I had what he would call a Jazz Dialogue: a conversation with a meta-conversation layered on top! I have listened to this episode a few times and it's a tough one to summarize or encapsulate. One thing that I'm left with is the idea that even the desire for agility or the hunger for no ideology is an ideology. Which leaves me reflecting on the ways that my own internal tendencies leads to my own ways of seeing things as "right". After all, designing a conversation is power and power should be exercised carefully...because I could be wrong! Show Bullets and Links Alistair Cockburn on the Web Agile Manifesto Crystal Clear Improvisation in Dance: What's Fixed and What's Flexible? "I expect people to decline my advice" The Oath of Non-Allegiance Precision vs. Looseness Crystal Clear: The Sloppiest methodology that could possibly work (Martin Fowler) "Arranging my life for the maximum amount of freedom" Anchoring Sloppiness in Essential details. (the opposite of an Overdetermined System) Cultural Invasion: Design as Cultural Imperialism Assuming that people bring their whole adult self to work: Agile Practitioners mentioned: Daniel Mezick Ken Schwaber Nic Sementa Kay Johansen Guest Leadership RE: When do people step forward and help: The Good Samaritan Experiment (hint: when they're not in a hurry) Be the Change you want to See can backfire Host Leadership The Art of Hosting Open Space Technology Going Meta: Talking about how we talk Jazz Dialogue The Heart of Agile Self Storytelling Kokoro: The heart Alistair's Poets: ee cummings and Emily Dickinson and a poem Alistair wrote in honor of ee: Mary Oliver's Wild Geese: You only have to let the soft animal of your body love what it loves

Note: This is the audio only version of the video podcast which can be found here -> https://vimeo.com/217951635 This is a short version of the HOA + Personal Agility Canvas session led by Dave Prior at the 2017 Heart of Agile Conference in Pittsburgh. During this video Dave provides a walk through of the Personal Agility Canvas with a focus on the expanded Heart of Agile. If you are new to this tool, it is a great way to conduct a self-assessment on your own Personal Agile Transformation. It will also help you establish personal goals for your desired state of personal agility and help you define actions you can take immediately to amp up your adoption of Agile. THE PERSONAL AGILITY CANVAS If you'd like to download a PDF of the canvas to complete on your own while you are viewing the video, you can find it here: http://bit.ly/2pVW7Ol CONTACTING DAVE You can reach Dave on the LeadingAgile site at https://www.leadingagile.com/guides/dave-prior/ On Twitter: https://twitter.com/mrsungo Or on his personal site at: https://drunkenpm.blogspot.com/ FEEDBACK/QUESTIONS If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LEADINGAGILE CSM AND CSPO CLASSES For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: http://www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class. HEART OF AGILE And to learn more about The Heart of Agile, please visit Alistair Cockburn's site here: http://heartofagile.com

Last week at the 2017 Scrum Gathering in San Diego, Dave Prior had a chance to sit down with Maria Matarelli and Alistair Cockburn to discuss the 2017 Heart of Agile Conference in Pittsburgh on April 27-28, Guest Leadership, the importance of dancing at conferences, Maria’s budding career as a DJ, her upcoming humanitarian work in New Zealand as well as her Agile Lifestyles event that will be live streamed from a stadium in New Zealand on May 3 (US time)… and of course… the Tango. If you’d like to learn more about the 2017 Heart of Agile Conference being held in Pittsburgh on April 27-28, follow this link: http://heartofagile.com/heart-of-agile-conferences/heart-of-agile-pittsburgh-2017/ Here are some additional links from the podcast: The Scrum Alliance has posted the presentations from the 2017 Scrum Gathering in San Diego on their site. You can find them here: https://scrumalliance.org/why-scrum/scrum-resources/gathering-presentations For more information Guest Leadership please check here: http://alistair.cockburn.us/Guest+Leadership Maria’s presentation in New Zealand on May 4th at 9 AM New Zealand time / May 3rd at 4 PM EST https://www.linkedin.com/pulse/join-powerful-agile-lifestyle-live-streamed-from-new-may-matarelli Dave’s previous interview with Alistair Cockburn on Designing Quality of Life https://soundcloud.com/drunkenpmradio/alistair-cockburn-designing-quality-of-life Contacting Alistair Cockburn Web: http://alistair.cockburn.us Twitter: https://twitter.com/TotherAlistair Contacting Maria Matarelli Web: http://mariamatarelli.com Twitter: https://twitter.com/MariaMatarelli Contacting Dave You can reach Dave on the LeadingAgile site at http://www.leadingagile.com/guides/dave-prior/ On Twitter at http://twitter.com/mrsungo Or on his personal site at: http://drunkenpm.net Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: http://www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

The original video version of this file can be found here: https://vimeo.com/213030252 The Heart of Agile 2017 is being held on April 27-28 in Pittsburgh. It is the 2nd annual HOA conference and it will also be the first Agile Conference held in Pittsburgh. Derek Huether and Dave Prior will both be speaking at the event. In this short video Derek and Dave each provide an overview of the sessions they will be leading at the event celebrating Alistair Cockburn’s approach to getting back to the basics of what makes Agile work. If you’d like to check out Derek’s session: How to Find Early Indications That Your Delivery System Will Fail April 27, 2017 1:30pm  -  2:15pm Empress Deck 1 http://heartofagile.com/Session/how-to-find-early-indications-that-your-delivery-system-will-fail/ And if you’d like to see Dave’s session: Heart of Agile + Personal Agility Canvas April 28, 2017 3:30pm  -  4:15pm Empress Deck 1 http://heartofagile.com/Session/heart-of-agile-personal-agility-canvas/ And if you need information on the conference in general or want to attend http://heartofagile.com/heart-of-agile-conferences/heart-of-agile-pittsburgh-2017/ We hope to see you there!

Craig and Tony sit down for a conversation at YOW! Conference with Betty Enyonam Kumahor (stands for good for me, on the way there) who is a technology leader in Africa: Tony and Enyo are mutual members of the Alistair Cockburn fan club YOW! Conference talk “Frugal Innovation and Scaffolding Software“ Software engineering uptake in Africa … Continue reading →

Writing the introduction to a podcast interview with Dr. Alistair Cockburn is not a simple thing. He is the co-author of the Agile Manifesto and the author of numerous books on Agile, Use Cases and Object Oriented Programming. There is also his work with Crystal and now with the Heart of Agile. He’s contributed a significant body of material around the topic of how we work. While this interview touches on most of the above, the primary focus of the interview is around a simple question with a complex answer: How can you design a lifestyle that is based on continually examining and enhancing the quality of your life. The interview is a long one, but is filled with volumes of advice and wisdom on how to build a professional life that supports the level of quality you want to achieve in your personal life. The information will be especially valuable for anyone working on consulting. For those who are pressed for time, I’ve created detailed show notes below so you can jump to a specific portion if you need to and you can find them here: http://bit.ly/2cjamVJ If you would like to learn more about Alistair Cockburn, check out http://alistair.cockburn.us. If you’d like to follow Alistair on Twitter, you can find him at https://twitter.com/TotherAlistair If you’d like to learn more about Heart of Agile, check out http://heartofagile.com If you’d like to check out the Facebook Live conversation between Alistair and Nic Sementa, try http://bit.ly/2cESM57

Nic Sementa from the Agile Marketing Academy joins me in this podcast to share his thoughts on how to craft User Stories that will work for marketing. Nic's thoughts and opinions on this topic are heavily influenced by his marketing background, which, as he points out in the interview, is a little unique since most of the conversations on the topic are led by agile practitioners.  During the interview Alistair Cockburn joined in the conversation to offer his expert advice and guidance on the subject. Alistair is one of the authors of the Agile Manifesto, the creator of the Crystal methods, leading voice on Use Cases and the man behind the Heart of Agile. (There is lots more - you can find it all at http://alistair.cockburn.us/ ) Show Notes: 00:38 Nic’s background and the challenges faced by Marketing that Agile could help with 4:27 Putting Agile together with Marketing 5:52 User Stories from a Marketers perspective 6:52 The historical challenges involved with “marketing” to the customer as opposed to engaging directly with the customer to find out what they need 8:00 How coercing your customer to buy leads to the marketing equivalent of technical debt 8:50 Googling Agile Marketing 9:20 The corporate world is high school with ashtrays 10:00 Why marketing needs a new language framework for Agile 10:57 Apology to the Band Geeks (which Dave is) 11:30 Revenue impact of implementing Agile Marketing Techniques 11:52 How User Stories change in Agile Marketing 12:33 Personas and more 13:33 Developing a deeper understanding of the User and his/her pain points 14:03 MadMen in Reverse is not going to help you understand the “ideal customer” 15:14 Marketing Research 16:10 There is no such thing as offline marketing 17:52 Recap of the Marketing User Story Guidance 18:57 Let’s get al Skynet with this thing! 20:00 Special Guest Alistair Cockburn on Agile Marketing User Stories 25:55 Abstract thinkers vs. concrete thinkers 28:05 Alistair’s visual grammar version of User Stories 35:33 Where to learn more about the Agile Marketing Academy and how to reach Nic Some Links: For more on the Agile Marketing Academy you can go to their Certification site http://www.agilemarketingcertification.com or send them an email at info@agilemarketingacademy.com. You can reach Nic on Twitter -> https://twitter.com/nicsementa

02:48 - Jim Gay Introduction Twitter GitHub Blog Ruby DSL Handbook 03:43 - Object Design Clean Ruby SOLID Principles 04:39 - DCI (Data, Context, Interaction) Main Resource for DCI (FullOO) 07:20 - What Painpoint DCI Aims to Solve The Gang of Four Book object-composition Mailing List (Google Group) 09:31 - Designing From DCI From the Start (Process) Levels of Use Cases Writing Effective Use Cases by Alistair Cockburn 11:42 - Object Composition Single Responsibility Principle 13:56 - Definitions: Forwarding, Delegation, Consultation, and Inheritance Class-Based Inheritance vs Prototype-Based Inheritance JavaScript Influence 18:37 - DCI and Service Objects Context 24:36 - Roles and Object Factoring Authentication 28:49 - One Context in a Single File surrounded 30:17 - Coupling and Cohesion 31:37 - Typeclasses 33:09 - DCI Criticism casting 36:51 - The Current State of DCI (Skepticism & Criticism?) Domain-Driven Design 38:56 - Preventing Reuse 41:18 - When should you not use DCI? 43:45 - Transition: Using/Undoing DCI (Experimentation) 45:04 - Resources fulloo.info Marvin object-composition Mailing List (Google Group) Clean Ruby More DCI Blog Posts by Jim Delegation Is Everything And Inheritance Does Not Exist Chubby Models Are Still Fat With Concerns. DCI Focuses On How Things Work Together The Gang Of Four Is Wrong And You Don't Understand Delegation Triggering The DCI Context OOP, DCI And Ruby - What Your System Is Vs. What Your System Does 4 Simple Steps - Extending Ruby Objects - The Tip Of The Iceberg With DCI Picks Richard Hamming: You and Your Research (Jessica) Martin Fowler: Yagni (Coraline) Ruby Monday (Saron) JunkFill (Saron) Wappalyzer (Saron) WhatFont (Saron) Julian Feliciano: What Is Source Control? (Saron) Bodum Santos Stovetop Glass Vacuum 34-Ounce Coffee Maker (Avdi) The Master and His Emissary: The Divided Brain and the Making of the Western World by Iain McGilchrist (Jim) request_store_rails (Jim) littleBits (Jim)

02:48 - Jim Gay Introduction Twitter GitHub Blog Ruby DSL Handbook 03:43 - Object Design Clean Ruby SOLID Principles 04:39 - DCI (Data, Context, Interaction) Main Resource for DCI (FullOO) 07:20 - What Painpoint DCI Aims to Solve The Gang of Four Book object-composition Mailing List (Google Group) 09:31 - Designing From DCI From the Start (Process) Levels of Use Cases Writing Effective Use Cases by Alistair Cockburn 11:42 - Object Composition Single Responsibility Principle 13:56 - Definitions: Forwarding, Delegation, Consultation, and Inheritance Class-Based Inheritance vs Prototype-Based Inheritance JavaScript Influence 18:37 - DCI and Service Objects Context 24:36 - Roles and Object Factoring Authentication 28:49 - One Context in a Single File surrounded 30:17 - Coupling and Cohesion 31:37 - Typeclasses 33:09 - DCI Criticism casting 36:51 - The Current State of DCI (Skepticism & Criticism?) Domain-Driven Design 38:56 - Preventing Reuse 41:18 - When should you not use DCI? 43:45 - Transition: Using/Undoing DCI (Experimentation) 45:04 - Resources fulloo.info Marvin object-composition Mailing List (Google Group) Clean Ruby More DCI Blog Posts by Jim Delegation Is Everything And Inheritance Does Not Exist Chubby Models Are Still Fat With Concerns. DCI Focuses On How Things Work Together The Gang Of Four Is Wrong And You Don't Understand Delegation Triggering The DCI Context OOP, DCI And Ruby - What Your System Is Vs. What Your System Does 4 Simple Steps - Extending Ruby Objects - The Tip Of The Iceberg With DCI Picks Richard Hamming: You and Your Research (Jessica) Martin Fowler: Yagni (Coraline) Ruby Monday (Saron) JunkFill (Saron) Wappalyzer (Saron) WhatFont (Saron) Julian Feliciano: What Is Source Control? (Saron) Bodum Santos Stovetop Glass Vacuum 34-Ounce Coffee Maker (Avdi) The Master and His Emissary: The Divided Brain and the Making of the Western World by Iain McGilchrist (Jim) request_store_rails (Jim) littleBits (Jim)

02:48 - Jim Gay Introduction Twitter GitHub Blog Ruby DSL Handbook 03:43 - Object Design Clean Ruby SOLID Principles 04:39 - DCI (Data, Context, Interaction) Main Resource for DCI (FullOO) 07:20 - What Painpoint DCI Aims to Solve The Gang of Four Book object-composition Mailing List (Google Group) 09:31 - Designing From DCI From the Start (Process) Levels of Use Cases Writing Effective Use Cases by Alistair Cockburn 11:42 - Object Composition Single Responsibility Principle 13:56 - Definitions: Forwarding, Delegation, Consultation, and Inheritance Class-Based Inheritance vs Prototype-Based Inheritance JavaScript Influence 18:37 - DCI and Service Objects Context 24:36 - Roles and Object Factoring Authentication 28:49 - One Context in a Single File surrounded 30:17 - Coupling and Cohesion 31:37 - Typeclasses 33:09 - DCI Criticism casting 36:51 - The Current State of DCI (Skepticism & Criticism?) Domain-Driven Design 38:56 - Preventing Reuse 41:18 - When should you not use DCI? 43:45 - Transition: Using/Undoing DCI (Experimentation) 45:04 - Resources fulloo.info Marvin object-composition Mailing List (Google Group) Clean Ruby More DCI Blog Posts by Jim Delegation Is Everything And Inheritance Does Not Exist Chubby Models Are Still Fat With Concerns. DCI Focuses On How Things Work Together The Gang Of Four Is Wrong And You Don't Understand Delegation Triggering The DCI Context OOP, DCI And Ruby - What Your System Is Vs. What Your System Does 4 Simple Steps - Extending Ruby Objects - The Tip Of The Iceberg With DCI Picks Richard Hamming: You and Your Research (Jessica) Martin Fowler: Yagni (Coraline) Ruby Monday (Saron) JunkFill (Saron) Wappalyzer (Saron) WhatFont (Saron) Julian Feliciano: What Is Source Control? (Saron) Bodum Santos Stovetop Glass Vacuum 34-Ounce Coffee Maker (Avdi) The Master and His Emissary: The Divided Brain and the Making of the Western World by Iain McGilchrist (Jim) request_store_rails (Jim) littleBits (Jim)

Victor is joined by Dale Ellis (@theDigitalDale), Jason Kerney (@JasonKerney), Zach Bonaker (@ZachBonaker) and Garrett Borunda (LinkedIn) at the Cape Rey in Carlsbad for a lively morning of Agile and Coffee. In this episode, our Agile heroes discuss: Agile tools to give Voice to a Teams "Agile is a cancer" Erik Meijer's presentation The Hacker Way - a Rational Alternative for Agile (explicit content) in which he claims that "Agile is a cancer that we have to eliminate from the industry" Agile Is Dead (Long Live Agility) by Dave Thomas (manifesto signatory) The Failure of Agile by Andy Hunt (manifesto signatory) Shu Ha Ri by Alistair Cockburn(manifesto signatory) Should Scrum die in a fire? by Ron Jeffries (manifesto signatory) Good To Great by Jim Collins Coordinating work between teams Power of Success (Mob Programming at Hunter) ACCUSWest 2015 archive at AgileLib.net, courtesy of Tobias Mayer Coming soon is Dr. Dave's 5 Saturdays program's Train the Facilitators workshops: May 30th and June 6th. More info at 5Saturdays.org Reach out to Vic (@AgileCoffee) on Twitter and use the hashtag #tellAgileCoffee to interact with us on an upcoming episode.

While at NDC London, Carl and Richard talk to Ian Cooper about hexagonal architectures. Turns out the important part is not the six sides - it's the idea of ports and adapters. Originally talked about by Alistair Cockburn, this is an architectural approach that focuses on being tolerant to testing as well as separating commands from querying. It's not quite Command Query Responsibility Segregation (CQRS), but you can see it from there! Ian discusses testing in a hexagonal architecture and how Test Driven Development (TDD) works so well with the separation of concerns that ports and adapters offers. If you're working on a long lived application that needs to be maintainable, you should be looking at hexagonal architecture!Support this podcast at — https://redcircle.com/net-rocks/donations

While at NDC London, Carl and Richard talk to Ian Cooper about hexagonal architectures. Turns out the important part is not the six sides - it's the idea of ports and adapters. Originally talked about by Alistair Cockburn, this is an architectural approach that focuses on being tolerant to testing as well as separating commands from querying. It's not quite Command Query Responsibility Segregation (CQRS), but you can see it from there! Ian discusses testing in a hexagonal architecture and how Test Driven Development (TDD) works so well with the separation of concerns that ports and adapters offers. If you're working on a long lived application that needs to be maintainable, you should be looking at hexagonal architecture!Support this podcast at — https://redcircle.com/net-rocks/donations

In September 2014, Alistair Cockburn met with researchers at the SEI headquarters in Pittsburgh, Pa. The SEI Podcast Series team was there as Cockburn sat down with Suzanne Miller to discuss his unique perspective as one of the creators of the Agile manifesto and his viewpoint on the current state of Agile adoption. Listen on Apple Podcasts.

This post explores several approaches to prepare for absorbing changing requirements in product development projects. This post was inspired by Alistair Cockburn’s recent remarks. Project Requirements Many development projects have formal requirements. Most often these are found in projects that … Continue reading →

In this episode of The Agile Revolution we have a special guest, Alistair Cockburn. Alistair spends time: denying a K Stew affair answering what brings him to Australia plugging his fantastic Advanced Agile Course presenting his thoughts on where ... Continue reading →

Nat Pryce is an early adaptor of eXtreme Programming and a contributor to several open source libraries and tools supporting Test-Driven Development, like jMock. In this episode we discuss several topics from the book 'Growing Object-Oriented Software, Guided by Tests' that he wrote together with Steve Freeman. We talk about the 'Londen-style' of Test-Driven Development, using mock objects to drive your design, listening to your tests and dependency injection. Nat's personal blog 'Mistaeks I Hav Made' is on http://www.natpryce.com/ and you can follow him on twitter via @natpryce. This interview is recorded on June 14th at the Software Practice Advancement conference (spa2011) in London. Interview by @freekl and @arnetim. Audio post-production by @Mendelt. Links for this podcast: The roots of the 'Londen-style' of Test-Driven Development can be traced back to the eXtreme Tuesday Club (XTC). A weekly London (pub) meeting that started more than 10 years ago. On his blog Nat visualizes different kinds of tests that drive the design of a software system. In the podcast we discuss the blogpost 'Whose domain is it anyway?' of Dan North. Nat completed his PhD thesis in 2000: 'Component Interaction in Distributed Systems'. A lot of his thoughts on object-orientation and messaging between objects and peers that is described in the book, can be traced back to his early research. In order to improve the testability of your software, Steve and Nat propose to apply the Ports and adapter architecture from Alistair Cockburn. You can read more on this subject on the wiki of Alistair. Use Hamcrest Matchers to improve the readability of your tests: learn more from this tutorial. While the use of Dependency Injection is widely spread in the software engineering community, Nat considers applying this style harmful. On his blog you can read more of his thoughts on this subject. In 2004 Steven and Nat published the article 'Mock Roles, not Objects' in which they introduces jMock. MultithreadedTC: a framework that can be used to test concurrent Java applications.

I got a chance to speak with Alistair Cockburn at Agile 2006.  He talks about his evolution as a Methodologist from a hardware guy, the Crystal family of methodologies, his writing and much more.I hope you enjoy.-bob payne