Podcasts about jutta eckstein

Jutta Eckstein is expanding the concepts of Agile to be a company-wide model, instead of a niche process for software developers. We chat with her about the book "Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy" which she co-authored on this subject. For more details on the book and many free resources, see: www.agilebossanova.com Discuss this episode: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠discord.gg/XVKD2uPKyF⁠⁠

In dieser Episode von Data Science Deep Dive sprechen Mira und Wolf-Gideon über das Agile Fluency Model und dessen Bedeutung im Data-Science-Kontext. Im Fokus stehen die verschiedenen Stufen der Agilität sowie die damit verbundenen Vorteile und notwendigen Investitionen. Wolf-Gideon erklärt, wie man den optimalen Agilitätsgrad für ein Team ermittelt und welche Praktiken dabei relevant sind.    ***Links*** Buch von Henning Wolf und Wolf-Gideon Bleek (2010): Agile Softwareentwicklung: Werte, Konzepte und Methoden (ISBN: 978-3-89864-701-4) it-agile Webseite https://www.it-agile.de/ Mehr Infos zu Wolf-Gideon Bleek auf der Seite von it-agile: https://www.it-agile.de/ueber-it-agile/das-team/dr-wolf-gideon-bleek/ Manifest für Agile Softwareentwicklung https://agilemanifesto.org/iso/de/manifesto.html Agile Fluency Project (EN) https://www.agilefluency.org/ Artikel: The Agile Fluency Model - A Brief Guide to Success with Agile von James Shore & Diana Larsen (EN) https://martinfowler.com/articles/agileFluency.html Buch: Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy von Jutta Eckstein & John Buck https://www.agilebossanova.com/ Feedback, Fragen oder Themenwünsche? Schreib uns gern an podcast@inwt-statistics.de

In this podcast the Culture and Methods editorial team along with special guest Jutta Eckstein talk about the current state and trends we see in the technology industry in 2024. Read a transcript of this interview: https://www.infoq.com/podcasts/infoq-culture-trends-2024/ Subscribe to the Software Architects' Newsletter for your monthly guide to the essential news and experience from industry peers on emerging patterns and technologies: www.infoq.com/software-architects-newsletter Upcoming Events: QCon London (April 8-10, 2024) Discover new ideas and insights from senior practitioners driving change and innovation in software development. https://qconlondon.com/ InfoQ Dev Summit Boston (June 24-25, 2024) Actionable insights on today's critical dev priorities. devsummit.infoq.com/conference/boston2024 InfoQ Dev Summit Munich (Sept 26-27, 2024) Practical learnings from senior software practitioners navigating Generative AI, security, modern web applications, and more. devsummit.infoq.com/conference/munich2024 QCon San Francisco (November 18-22, 2024) Get practical inspiration and best practices on emerging software trends directly from senior software developers at early adopter companies. https://qconsf.com/ The InfoQ Podcasts: Weekly inspiration to drive innovation and build great teams from senior software leaders. Listen to all our podcasts and read interview transcripts: - The InfoQ Podcast www.infoq.com/podcasts/ - Engineering Culture Podcast by InfoQ www.infoq.com/podcasts/#engineering_culture - Generally AI https:/www.infoq.com/generally-ai-podcast/ Follow InfoQ: - Mastodon: techhub.social/@infoq - Twitter: twitter.com/InfoQ - LinkedIn: www.linkedin.com/company/infoq - Facebook: bit.ly/2jmlyG8 - Instagram: @infoqdotcom - Youtube: www.youtube.com/infoq Write for InfoQ: Learn and share the changes and innovations in professional software development. - Join a community of experts. - Increase your visibility. - Grow your career. www.infoq.com/write-for-infoq

Konferenzen spielen eine zentrale Rolle für den Austausch von Wissen und Erfahrungen nicht nur zu Software-Architekturen. In dieser Episode sprechen Michael Stal und Eberhard Wolff mit Jutta Eckstein, die Program Chair der OOP-Konferenz ist. Dabei geht es darum, warum es sich lohnt, Vorträge auf Konferenzen zu halten. Außerdem geben sie Tipps, wie man erfolgreich Vorträge zu Konferenzen einreicht und dann hält. Sie teilen dabei ihre Erfahrung als Sprecher:innen und Mitglieder verschiedener Programm-Komitees, bei denen sie eine Vielzahl von Vortrags-Abstracts gelesen und bewertet haben. So ergibt die Episode einen guten Blick in den Maschinen-Raum des Konferenz-Business.

In this episode we speak with Claudia Melo, Jutta Eckstein and Steve Holyer about the Agile Sustainability capability and how it can help your teams create a better world. Jutta Eckstein (https://www.jeckstein.com/) works as an independent coach, consultant, and trainer. She is trained as a pollution control commissioner on ecological environmentalism. Jutta has helped many teams and organizations worldwide to make an a 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'. Steve Holyer is an experienced trainer. coach, facilitator and consultant helping organizations unleash value and deliver results. He is also a frequent international speaker and a thought-leader on Scrum and Agile software development. He serves as advocate and mentor for companies, leaders and change agents looking for a better way of working using Agile practices in a productive, fulfilling, and fun way. Steve learned his craft serving as a Scrum Master with multiple teams and organizations, so he knows how to change an organization from the inside. From international Swiss business to emerging markets in South Africa, Steve understands and shows how to apply Scrum and Agile principles in specific cultural contexts. Since 2000, he has been based in Zurich. Switzerland. Claudia Melo is a technology leader building high-performing agile teams, taking big ideas and bringing them to life, and helping teams successfully navigate through change and innovation. She brings over twenty years of global experience in developing new digital solutions. digital transformation, consulting, technology/business strategy, evidence-based research & working with senior leadership executives. She was previously Director at Loft, Enterprise Agile Coach with the United Nations in Vienna. and Thought Works' CTO for Latin America, where she also played a Global Head of Tech Learning Development role. Since 2016, she has been working on ICT for Sustainability, aligned to the 2030 Agenda for Sustainable Development. Claudia received her Ph.D. in Computer Science (Agile Team Productivity) from the University of São Paulo (USP), in collaboration with the Norwegian University of Science and Technology (NTNU). She is passionate about community building and impact, contributing through volunteering, public speaking, teaching, mentorship, research, books, and industry reports in Latin America, Europe, US, and Scandinavia. In 2015, she received the USP Outstanding Thesis Award and, in 2016, cited as "Mulheres Inspiradoras" by ThingOlga in Brazil. She is also an advisory board member in Computer Science for Insper. --- Send in a voice message: https://podcasters.spotify.com/pod/show/comparativeagility/message

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

In this episode, Jutta Eckstein, an independent coach, consultant and trainer, based in Germany, shares Her origin story of starting as a product engineer, with an interest in software developmentStarted as a trained teacher and when the need for teachers dropped, went on to study product engineering and studying Pascal - and completely falling in love with software developmentAlso getting trained as pollution control commissioner, when she could move from street protests to actually working to keep pollution under controlHer early experience with Pascal and Assembler, and Smalltalk being her all time favoriteBeing part of the professional communities such as OOPSLA, and getting an orientation on the techniques and practices that got crystallized as Agile practicesHer transition from an engineer to a coach : discovering her strength based on a trigger by her project managerMoving into areas of architecture and design and becoming a team coachThe difference between a consultant and coach rolesStudying business coaching and change management, to get a formal understanding and foundationHow that enabled developing connections with people across various industriesMy task is not to create the right mindset, my task is coming with the right mindset myselfThe importance of listening, coming with experience, and working with expertsStarting with a retrospectiveStarting with a few questions: clients having prior experience with changeWhy do you think it will be successful this timeWhat hinders you from starting nowIf she discovered anything surprising in these initial explorations… her response of a pattern she sees.. In the next episodeJutta 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: @JuttaEckstein | https://www.linkedin.com/in/juttaeckstein/ | https://www.jeckstein.com/| https://www.agilebossanova.org | https://jeckstein.com/sustainability

“There's no leading without following. We are only a leader because somebody is following us." Jutta Eckstein is a coach, consultant, and trainer who has helped many teams and organizations worldwide making an Agile transition. In this episode, we discussed ideas from her book “Company-wide Agility With Beyond Budgeting, Open Space, and Sociocracy”, also widely known as the BOSSA nova. Jutta started by sharing today's company challenge in terms of collision of values between shareholder, customer, and the employee, and she provided a suggestion how to align the values better. She then broke down BOSSA nova and explained each concept and principles of Beyond Budgeting, Open Space, Sociocracy, and Agile. Jutta also shared the four values of BOSSA nova and how they also relate extrinsically to sustainability. Listen out for: Career Journey - [00:06:24] Writing BOSSA Nova - [00:08:34] People-Customer-Shareholder Value - [00:12:04] BOSSA Nova - [00:14:54] Beyond Budgeting - [00:24:16] Open Space - [00:32:56] Sociocracy - [00:37:58] Agile Values - [00:44:04] Transparency - [00:49:50] 3 Tech Lead Wisdom - [00:52:22] _____ Jutta Eckstein's Bio Jutta Eckstein works as an independent coach, consultant, and trainer. She has helped many teams and organizations worldwide to make an Agile transition, especially with 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. Follow Jutta: Website – https://jeckstein.com/ Twitter – @JuttaEckstein LinkedIn – https://linkedin.com/in/juttaeckstein Our Sponsors Mental well-being is a silent pandemic. According to the WHO, depression and anxiety cost the global economy over USD 1 trillion every year. It's time to make a difference! Learn how to enhance your lives through a master class on mental wellness. Visit founderswellbeing.com/masterclass and enter TLJ20 for a 20% discount. The iSAQB® Software Architecture Gathering is the international conference highlight for all those working on solution structures in IT projects: primarily software architects, developers, professionals in quality assurance, and also system analysts. A selection of well-known international experts will share their practical knowledge on the most important topics in state-of-the-art software architecture. The conference takes place online from November 14 to 17, 2022, and we have a 15% discount code for you: TLJ_MP_15. DevTernity 2022 (devternity.com) is the top international software development conference with an emphasis on coding, architecture, and tech leadership skills. The lineup is truly stellar and features many legends of software development like Robert "Uncle Bob" Martin, Kent Beck, Scott Hanselman, Venkat Subramaniam, Kevlin Henney, and many others! The conference takes place online, and we have the 10% discount code for you: AWSM_TLJ. Like this episode? Subscribe on your podcast app. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Pledge your support by becoming a patron. For episode show notes, visit techleadjournal.dev/episodes/106.

We know that Agile impacts organizations and the lives of the people we develop solutions for. But, did you know that Agile is having an impact on the planet? Agile Consultant, speaker and author, Jutta Eckstein, sits down with host Bobby Woods at XP2022 in Copenhagen, Denmark to talk about exactly how that is happening and the impact Agile is creating for worldwide sustainability.

Jutta Eckstein from Germany, she is CIT Coach, Consultant, Speaker, Author, Trainer.She said about importance of learning from experience. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

Jutta Eckstein spricht über ihre Karriere im Bereich Software-Architektur.

Full video interview available here: https://youtu.be/oJbZF1yiWvg  Guest Bio: Aino Vonge Corry (born 1971 in Aarhus, Denmark) is an independent consultant, who sometimes works as an agile coach. After gaining her Ph.D. in Computer Science in 2001 she spent the next 10 years failing to choose between being a researcher/teacher in academia, and being a teacher/facilitator in industry. She eventually squared the circle by starting her own company, Metadeveloper, which develops developers by teaching CS, teaching how to teach CS, inviting speakers to IT conferences, and facilitating software development in various ways. She has facilitated retrospectives and other meetings for the past 15 years during which time she has made all the mistakes possible in that field. Aino has lived in Stockholm, Lund, and Cambridge, but she is now back in Aarhus, Denmark, where she lives with her family, and a growing collection of plush cephalopods.   Social Media/ Website LinkedIn https://www.linkedin.com/in/aino-vonge-corry-9a23801 Twitter: @apaipi Website: https://metadeveloper.com   Books/ Resources Retrospectives Antipatterns by Aino Corry https://www.amazon.co.uk/Retrospectives-Antipatterns-Aino-Corry/dp/013682336X Coaching Agile Teams by Lyssa Adkins https://www.amazon.co.uk/Coaching-Agile-Teams-ScrumMasters-Addison-Wesley/dp/0321637704 Agile Retrospectives by Diana Larsen, Esther Derby https://www.amazon.co.uk/Agile-Retrospectives-Making-Pragmatic-Programmers/dp/0977616649 Retrospectives for Organisational Change by Echstein https://www.amazon.com/Retrospectives-Organizational-Change-Agile-Approach-ebook/dp/B07NS796KY Fearless Change Patterns by Linda Rysen https://www.amazon.com/Fearless-Change-Patterns-Introducing-Ideas-ebook/dp/B0054RGYNQ Prime Directive by Norm Kirk https://retrospectivewiki.org/index.php?title=The_Prime_Directive   Full Interview Transcript Ula Ojiaku: Many thanks Aino for making the time for this conversation and for being my guest on the Agile Innovation Leaders podcast. Aino Corry:  And thank you for inviting me, Ula. It was great to have you in the course, you had a lot of good questions. And that's how we met. And I've been looking very much forward to this day. Ula Ojiaku: So could you tell us a bit about yourself, you know, who is Aino Corry? Aino Corry: Yeah, so Aino Corry is 50 years old, she lives in Denmark, she's got three children. And she, she's always wanted to teach. Actually when I was in primary and secondary school, I wasn't so happy with mathematics teaching, so I decided after school, I wanted to be a mathematics teacher in secondary school. Actually, I thought about it and I thought I didn't really like school. So maybe I should be a teacher in high school instead. And so I decided to try to go to university to study mathematics to become a high school teacher. But then I had to do some programming in the mathematics course. And I really, really fell in love with that. So I changed subject to computer science. And then I did my Master's degree with a focus on design patterns, which was very new at the time. And when I finished, I wanted to continue working with design patterns. And that's why I applied for a Ph.D. I applied for a Ph.D., actually, just to prolong my university studies to make more of the fun thing that I've done. And then when I finished, I thought, I wanted to be a researcher and a teacher and I had a job at the university as an assistant professor. Aino Corry: And then I decided that I wanted to go out in industry instead, because I, I had a child already, and I wanted to have another child. And I really, I was dead poor, so I wanted to earn a lot of money, so I went down industry to get some money. And that worked, I got some money. And after a few years there, I went back to university to do some research and some teaching, because they had a research project, which was interesting. It was when Bluetooth was quite young and was about programming pervasive computing devices, what you would call IoT today, yes. And then I was there for a few years, and then went back to the industry, and was there for a few years. And then I went back to university. And then I did my research in how to teach computer science and how people learn. So that was also interesting. But then I wanted to stop again because then I was full-time at university and I also did some consulting in the IT industry. So I thought I would go back to the industry. Aino Corry: And then I thought, Naah, I want to do something else. I want to be my own boss, I don't want to work that much anymore. I had three children at the time. So I decided to be an independent IT consultant, thinking that then I would work less, that was a huge mistake. I, I like having my own company, but I wouldn't say that I work less because if you have a job and you have a boss, you can tell your boss ‘Oh, it's too much. I don't want to do that much. And please take some of the tasks away from me.' But when you're your own boss, and you're a time optimist, like I can be, you think ‘I can do that. And I can do that.' And especially now with COVID, it's even worse because at least prior to this, I had to calculate time in to get from one meeting to another, you know, from one client to another from one country to another. But now I can actually I can work with clients in four different countries in a day. And I've actually, one week I spoke at six different conferences in one week. So normally I would only be at one conference. So it's actually made me a little bit confused and looking very much forward to actually spending time on trains and planes and cars again, Ula Ojiaku: To have the downtime… Aino Corry:  Yes, I thought I'd never miss that, but I do, so I guess I guess that's my career. Ula Ojiaku:  Great. Now, just a little bit more about your research you did on teaching, on how to teach computer science. Now I would expect there would be an intersection of you know, disciplines; it wouldn't just be computer science itself. Was there an element of maybe psychology (of), you know, how people learn and all that? Aino Corry: Yeah, it was a lot of that it was about, well, the psychological aspects of how people react to different, being in different situations, and being spoken to in different ways. And there was something that I don't think maybe you call it neurology but thinking about how to model the brain in order to make it remember what you're saying. And just something like what does it actually mean to learn something? And in Danish, the word for teaching and learning is the same word, but in English teaching and learning are two different words. And that's actually a subtle difference, which is a big difference, which makes it maybe even harder for me as a Dane to start thinking about this because you think about it as the same process. Aino Corry: But it's two very different processes. And one of the biggest things that I learned when I started doing research and teaching, and that was after having taught for 16 years or something like that, the thing that I learned was that I was so immensely focused on how to condense this book into presentations and assignments so that the students could listen to me and do the assignments. I didn't think enough about the relation between the student and the material. So I was thinking more about the relation between me and the material, and me and the student. So the really important thing is that, when you have any sort of conversation with people, it's a student, or it's a presentation that you're doing, what you want to do is that you want to change their brains really, right. But you can't see the change in the brains. So you need to figure out how can I, how can I assess that they've changed the brain? So, the first thing you have to do is think about what is it actually that you want them to be able to do differently? Do you want them to say something else? Do you want them to be able to program, to design, to facilitate, what is it that you want them to do? Because then you can set up? What is the assessment? How do you assess what they can do? Do they actually have to look at the design at an oral exam? Do they have to process some words in a written exam? What is it that you want them to do? And then when you know what you want them to do to assess it, then you can figure out what is it that you want them to do while training do you want them to do the same when you're training them, that they have to do in the assessment. Aino Corry: So that the exam is actually what they have been doing for the past hour, month, year, instead of examining something completely different than what they have been doing. And then when you know all that, then you start thinking about okay, so what material do I need for them to read? And that's, that's actually the last thing. And prior to this, I would take a book and I would think, this is the thing that I want to put in their brains. And then at the exam, I would ask them, do you understand that? Can you explain that, but maybe they never explained it during the course, maybe they just did exercises or something like that. So that was one of the most surprising things is I guess, maybe it's neurology, maybe it's psychology, it's definitely different. It's lending, from different fields. And, and you can say that the computer science part of it is actually the least part. But the interesting part about computer science and teaching computer science or natural sciences is that it's mostly not so much about discussing things. It's more about being able to understand things and relate things and apply things. Now, I guess well, you can say that all issues, all subjects are like that. But with the natural sciences, it's much more about understanding the world, changing the world. So yeah, I think it's very interesting, but also trying to explain difficult subjects to people. How do you actually do that? Ula Ojiaku: So you've already mentioned that you, you know, started your business because you wanted to be an independent, and then you realized, oh, well, there are other things because as a business owner, you probably would do all the other admin tasks that someone else would have in person. Yeah. Now, am I right? In the understanding, you still run, you know, your business, which is the meta developer, right? Do you have employees right now? Aino Corry: No, I don't, and I don't want to. And I've had a lot of people asking me over the years if I want to employ somebody and I, I did try once for just a small gig that I needed a helping hand and I employed that person and that person was not a problem, but all the extra paperwork, with taxes and insurances, and what do I know. So if I'm working with people, now they have their own company, and then they can send me an invoice and then I can pay them like that because I really want to be independent and five, no six years ago, my family and I, we moved to Cambridge in the UK for a year. And it was so easy for me, I could just do it because even though I had to really work a lot less because I didn't have my network in England and I had three kids who had to move to a different country so I had to focus on them. I could just do it, I could just work less and not make any money or almost no money. Because I didn't, I wasn't responsible to anybody, I was only responsible to myself. That gives me the freedom that I want to have. And during COVID I lost everything in my book. My calendar just was empty. Wow. And I didn't know how to continue with the company. But I only had to worry about myself. I didn't have to worry about anybody that I employed. So that was nice. Ula Ojiaku: Yes, I completely agree. I mean, it would be a lot of responsibility, having other people's livelihood as well as yours to think about that. Yeah,  Aino Corry: Especially. I mean, this is such a fluid thing. It's difficult to promise anything. Ula Ojiaku: Now, but hopefully, with the, you know, lockdown restrictions on I mean, unfortunately, we're still not out, you know of the red and unfortunately, many lives have been lost, and many people have been affected but it seems like there is light at the end of the tunnel with the (covid) vaccination (roll-out) and all that. So would you say your calendar is filling up again? Aino Corry: Yes, it actually became overfilled, yeah during COVID. Because my book came out. So I had hoped that when my book came out, I would travel everywhere in the world and sign my books. Unfortunately, that couldn't happen because of COVID. But that's the least of the things that could happen to people during COVID. I've been very lucky. But my book came up... Ula Ojiaku: Retrospectives Antipatterns… Aino Corry: Yes. and, and that meant that there were a lot of people who wanted to talk to me about retrospectives, which was why I wrote the book. So that was great. So I don't know if it had filled up as easily without the book, but it definitely helped, I think. But I'm looking so much forward to getting out and speaking at conferences again. I taught at the university yesterday, and I will again tomorrow. And that was in real life. It was so nice, people were laughing and we were clapping. And we were like doing icebreaker exercises where we were standing up and moving towards each other. And it was really nice. Ula Ojiaku: Yeah, I mean, nothing can ever replace that, you know, face-to-face in-person interaction. Whilst we're grateful for technology, you know, for bridging the gap, you know, but once in a while, it's definitely important. Yeah. Great. Now, so since you've shown us your book, Retrospectives Antipatterns. And you've talked about it briefly, why don't we delve into that a bit. And for the audience who are listening either (via) audio or video only, there will be the links to the, you know, to the book, and other resources that we touch on in the show notes. So what you said people were, you know, asking you lots of questions about retrospectives, and asking for advice, which was one of the motivations for writing the book. Could you tell us the story behind that? Aino Corry: I love to tell the story behind the book. Thank you for asking, Ula. So I started facilitating Retrospectives because Linda Rising gave me a book by Norman Kerth called Project Retrospectives. And then I started facilitating them. And then Diana Larsen and Esther Derby wrote a book about Agile Retrospectives - Making Good Teams Great, which condensed all the retrospective activities into smaller bite-sized ones that you can use after each sprint. And I facilitated retrospectives at in the time I worked for a company called Trifle, inside Trifle with the customers. When I went back to university, I facilitated retrospectives there. And I just really, really liked it. I even facilitated retrospectives with my family and myself, and everybody basically who couldn't get away. And I, I got a lot of experience. And then once I was at a conference that I'd been part of organizing the conference and inviting speakers and what I do at these conferences is that if a speaker gets sick, or can't be there, then I fill in with a presentation. So they came to me and asked me is ‘Could you fill in with a presentation? Just 20 minutes?' ‘Okay, I said, When do you want it?' And they said ‘In 20 minutes, and we would want it to be a new talk, could you do that?' I was like, how can I? How can I prepare a new talk in 20 minutes for a 20-minute talk? And then I thought the only thing that I really, really know about that I can talk about for lengths, are all the mistakes that I'm continuously making when facilitating retrospectives So I thought this is definitely something I can talk about. So I just, I just, I think I drew some pictures, or I found some pictures online. And then I just spoke out from those I, I spoke about three different things that I called Antipatterns for Retrospectives, things that often go wrong for me and how to solve it. So not just explaining the problems, but also how to get out of the problem situation. And they really liked it. And then I started giving that talk. And I extended it to 45 minutes to an hour, I extended it to a day. And people kept asking me, ‘Where can we read more about this?' And I said you can't really because it's, it's in my head. And then somebody said ‘Maybe we you should write a book.' And so I thought I'm not going to write a book, I already did my Ph.D. dissertation, and I'm not doing that again. Not the best part of it for me. But then I started just writing, you know, first, it was just a few Word documents that I shared with people in my retrospective network. And they gave me feedback on that. And then I started a Leanpub book. And it turned out people wanted to buy the Leanpub book. So I thought, well, maybe I should add some more chapters. And then I thought it would be interesting to see if there's any publishers who would like to publish it. Aino Corry: And luckily, I have a very good network in IT, so I asked a lot of people who are already authors and, and Martin Fowler introduced me to somebody from Pearson, Greg Dench, and he, he read my book, the PDF that I sent from Leanpub, and he said that they thought they'd like to publish it. And there was a lot of back and forth and back and forth. And could you change the title? Because Antipatterns sounds so depressing and negative? And I said, but it is an Antipatterns, so I cannot. And then those things about I want this octopus, this big octopus? Ula Ojiaku: Yes, yes. Aino Corry: Well, it looks a little bit like a children's book, are you sure you want it to look like a children's book and I said actually, I'm, I'm really like a child myself. So I want it to be me. And then I said, and it has to be printed in color. Because I want all these Antipatterns to have not just a name, but also a picture. Because with Antipatterns, what you do is that you create an awareness, so I described, this is the context you're in, this is what normally happens, but that's the Antipattern solution. That's actually another good solution that gives you these drawbacks. But then you have the refactored solution, which gives you these benefits. And I want the patterns as well as Antipatterns, it sort of enables you to have a discussion and a higher level of extraction. So you can say, for instance, with patterns, you can say, then I use the observed or I implemented composite, and then you don't have to explain all the nitty gritty details. And it's the same with these Antipatterns. So instead of saying, ‘Well, we tried to vote, but then some people held up their vote, and I allowed them to do so. But maybe I could have done it differently', you can just say, well, then I ended in political votes. And there's also the name and then the picture because for some people, the name is easy to remember, but for other people, the picture. Ula Ojiaku: The pictures, yes. Aino Corry: I definitely am very visual. So I, I really remember pictures like that. And graphs, it really helps me understand I love UML, and when I work with architecture, it's very important for me to be able to draw these things. So that's how the book came about. And there were other publishers who didn't want it because they thought it was not technical enough or they didn't like the Antipatterns in the title or they thought it was too negative, but Pearson wanted it, so that's great. I'm very grateful for that. Ula Ojiaku: That's fantastic. Again, we'll have the link to the book in the show notes. And I mean, so I do identify with, you know, the things you said or where you kind of held your ground and in terms of how the book was meant to look for pictures. And if it's playful, it's easier to absorb. There is the saying in English, you know, a picture is worth more than a thousand words. Definitely. And in that way, you're kind of trying to cater for different people with different learning styles, because there are some of us who can read you know, but pictures kind of makes it, breaks it up and kind of, you know, conveys the message even more effectively in some instances. On that note though, are you, do you already have an audio version of it? Or do you think it would bode well as an audio version? Aino Corry: Yeah, that's a bit embarrassing, Ula, because I have narrated, I think five of the chapters. But then I stopped, but I will narrate it. I am doing it and it will happen, hopefully, yeah, but it turns out it's much more difficult to make an audiobook than you think I want to narrate it myself. I agree. Have you tried it? Ula Ojiaku: Well, no, just with, you know, starting the podcast and you know, kind of speaking, there is a whole lot to it. So I can imagine trying to bring a book to life, you know, kind of enunciating, and there'll be some places you need to emphasize. That's why I've never done it yet. But I can imagine. Aino Corry: Yeah, well, I could have hired an actor to do it, but I wanted it to be me, because it's my experience. It's, it's my voice that should be in this book. And then so I'm Danish and English is my second language. I normally think, Okay, I'm pretty good at English, I can speak fluent English, people understand what I'm saying I can express myself and the book is written in English. But then when you start recording it, and you'll listen to it afterwards, you make so many mistakes, or at least I do. So I have to repeat that again. So it just takes a lot longer than I thought, but it will be there, it's my plan. Ula Ojiaku: We'll be looking out for it, definitely, yeah. Okay, so, in your view, what are Retrospectives, and why are they important? Aino Corry: Well Retrospectives is a way for a team to set time aside to reflect on where they are, inspect, you'd say, and learn from, that, appreciate what happened, and see how can we improve going forward, the way that we communicate, the way that we work, the way that we program or design, or whatever we do. It's simply taking time aside to appreciate and inspect and then adapt to the situation. In a sense, it's the core of Agile, right, inspecting and adapting. And for a team to have regular Retrospectives, I think it's so important. Sometimes they'll think we don't have anything to talk about, we don't have any problems. But there's always something that can be improved, even if it's a small thing. And having those regular Retrospectives helps you remember, to continue to improve in all different aspects, but also, I think Retrospectives is a way to gain trust between team members, it's not the only thing you need to gain trust, but that sharing thing that showing, “Okay, that didn't go very well”, or “I need to learn this”, or “I got stuck with this”. But also, “I was really happy about this”, ”this made me so energetic, and really optimistic about these things”. It helps people understand each other as human beings and as sort of parts of the machinery or parts of the system, that's the team or even the organization. So I think it's important in all aspects. And for everybody. Ula Ojiaku: It's interesting, your definition of what a retrospective is, and I'd never really thought about it as a way for team members to, you know, build trust with themselves, so thanks for mentioning it, that really stood out for me, do you have any examples in your experience where, you know, this happened where there was maybe little or no trust and, you know, subsequently through the Retrospectives the team, started having more trust towards themselves? Aino Corry: I would like to say yes, but I have to say that when I realized in the retrospective that there's not enough trust, it is something that you have to work with also between the Retrospectives in a sense if there is not enough trust to share anything, then, then the retrospective will not be trust-building in itself, but it can help you reveal that there is not enough trust, and then you can start working with it, and to me trust is sort of the equation between relationships and that you can rely on people that you rely on people and you have a relationship. So if you have a relationship, if you know a little bit about each other as human beings, it makes it easy for you to trust people. And also if you can rely on other people, for instance, if they say, ‘Oh, I'll do this', then they'll do it. Or they'll say they can't do it, that's part of the trust as well. And if you understand, if you learn at the retrospective that there isn't enough trust, the retrospective can become a waste of time. Aino Corry: Because if they don't want to share the things that are really difficult, then you will just talk about the meal in the canteen, or whether we should have a meeting that's two hours long, or one hour long, or something like that, which is not really changing anything. It's usually things about how to give feedback or whether the code reviews can be done in this way or the other and whether we need to learn something more. So, but you can definitely be aware that there's trust issues that you can work on outside the retrospective, but then I think another important thing is that if they have already sufficient trust to be able to share things, then I've heard from a lot of people that it can, it can feel almost like team therapy to have a retrospective because they don't have to think about it, they can sort of relax and let the facilitator carry the conversation forward sometimes. And then if it can help them say, now, we talk about this, Now perhaps we've talked enough about this, now we should talk about this or could you see this from the other side, which is something that I sometimes do as well. So it can be a little bit conflict handling as well to be a facilitator to say what did you hear him say right now? Or can you imagine what his day was like yesterday or something like that? So it can be therapeutic if you want to, but that depends on the facilitator. You can also have a retrospective facilitator, which is perfectly fine, but only wants to talk about how we can improve the way that we actually design things, the architecture we make, the meetings we have, it can still be helpful, doesn't have to be therapy, but it can. Ula Ojiaku: Yeah. In running the retrospectives I would assume, I would imagine, there would be some sort of advanced preparation from a facilitative perspective. Now, would you when you get asked to do this by you know, other organizations and teams? Do you normally have a point person and you'd get the brief in terms of what they're trying to achieve from the point person, and that would set the agenda? So have you always found yourself sticking to the agenda? Or have you ever had to kind of flex depending on what you sense the team needs? Aino Corry: Yeah, I've definitely had to change my agenda. So if I get invited to facilitate a retrospective, I talk to the one who sponsors me to ask them why, why have you reached out? Do you already have Retrospectives? If you have Retrospectives, why do you need an external facilitator? What normally works for you in retrospective? What doesn't work? Is there any conflict? I should know about it? Is there anybody who's really quiet? Anybody who's really a loudmouth? Is there anything that can help me plan this retrospective in the right way? Then sometimes they say, oh, we'd really, really like this retrospective to focus on how they can learn as a team, or we'd really like this to focus on their communication with other teams. And then in some, sometimes I'll say, okay, so, so we'll say that's the theme for the retrospective. And then I'll let people know that that's a theme for the retrospective. But other times, if it's a new group, then I'll probably encourage that sponsor to allow me to make some, just a generic retrospective. So for a new group who has to work together, maybe he or she will allow me to create a futurespective for them, which is the kind of retrospective where you imagine that you're in the future, looking back at what happened. And then they say, okay, then we, then somebody got fired, or this didn't work, or the users hated it. Aino Corry: And the way that I have this futurespective, with the new team is that then I get to understand and they get to understand about each other. What do they hope and what do they feel will happen in this project, and then we can have action points, which will allow them to get the things that they hope and avoid the things that they fear. So sometimes I'll let the sponsor know, well, actually, we should do it a little bit different way. And sometimes I'll say, that's fine, we'll focus on that. But it is often so that you need to have an extra agenda when you prepare for a retrospective, at least a little bit. Because sometimes you suddenly end up in a situation where you have somebody who's speaking all the time or somebody who's really quiet. And then all the plenary discussions that you decided on, you can't have those because plenary discussions are not very nice if you have like a big difference in how much people wants to speak. And then you have to divide them into smaller groups, or you have to change it in writing. Or you have to make round robins where everybody takes turns in saying something, so just as an example. But it could also be that you notice that all the things that they're talking about are problematic, turns out to be things that we think are sort of out of their hands, not really something they can do anything about. And then if you spend all the time discussing things that you can't change, then it's just like a session where you're just complaining about everything. And in those cases, I sometimes get out the soup exercise that I learned from Diana Larsen where you make the three circles, things the team can do, things the team can influence, and then you have the soup outside. And then I say well out of all these problems that you're complaining about, how many of these are things you can do something about, how many of these things you can influence, how many of these things are in the soup, and for the things in the soup, you might just have to accept that this is the world we live in, like Corona right now. Yeah, It's what it is. Ula Ojiaku: Amazing. So, so what would you say would be, from what you've observed, I'm sure you've had a spectrum of or a continuum of teams from what you'd consider high performing to maybe people… I mean, a team that's still up and coming. What would be your view of the characteristics of a high-performing team? Aino Corry: Yeah, that's a good question. In my experience, it's not so much the individual's skill set that makes a high-performing team, an individual with the highest skill set can do a lot on its own. But if we talk about a high-performing team, it's about a team that can communicate, it's about a team where you feel there's psychological safety to say when you're stuck, or when you need help. Because if you're only working on what you want, first and foremost, and only helping other people, if you really have to, then it's not really high performing, and things will clot up and it'll be slow. One of the symptoms that I see in teams that are high-performing is that they're laughing together. So I evaluate sometimes teams based on how much they laugh, and not how much they laugh over each other, but how much they laugh together. And how, yeah, I think, I think it's a good litmus test. Because if they laugh together, then it makes them happier for each other, because the laughter starts, you know, all the happiness hormones in your brain and sensing around your body. So if you laugh together with somebody, you like them a bit more. And if you like them a bit more, you might trust them a bit more. And if you trust them a bit more, you might reach out and ask for help. Or you might offer help, when you see that somebody needs it. And if you are in an environment where you will you think that you can work freely, and you can speak freely, and you feel nice, then you're much more efficient together with other people. So that's what I see in high-performing teams. Ula Ojiaku: I mean, everything you've said because I was going to ask you to define for the benefit of the audience who might not be familiar with the term what psychological safety is? So would you say, you know, it's pretty much what you've broken down, you know, how much they laugh together, how safe they feel in asking for help, and, you know, yeah, being able to work together. Aino Corry: Yeah, I think that Gitte Klitgaard has, has taught me one of the most important things about psychological safety. And that is that it's actually not about being comfortable all the time, but it's about feeling comfortable about being uncomfortable. So even if you're saying something, which doesn't feel nice, you should still feel comfortable about it. And I think that's an interesting difference. So it's not just about making everybody feel good all the time and not having problems and only laughing and talking about positive things. That's not psychological safety. It's being okay to say I have a down day, or it's being okay to say that I don't understand what you're saying, or I feel negative, or I'm worried about this, or I don't think that this was done well enough, we could do it differently, that to me is psychological safety. Ula Ojiaku: Would you say that psychological safety, you know, having an environment that encourages the sense of psychological safety, is that only up to the team to foster? (If not) So who else would be involved, in your view? Aino Corry: I think that there's a culture in an organization and there can definitely be a culture of organizational safety and there can be a culture of non-psychological safety. And if, if the management is also showing that they're comfortable with saying uncomfortable things, I think that helps. If they're comfortable with saying, ‘Oh, we didn't do very well about that, or I made a mistake, or, if they're okay with telling people to do things differently, instead of making it really awkward or being very angry about it. That's, that's brilliant. And I remember one of the great managers, I had once that I made a huge mistake, that was really embarrassing. And when I noticed it, I felt so bad. I was beating myself up about it, but I had to tell my manager, and I had to come forward and say I messed up completely. And the way that he reacted was just wonderful. He said, ‘Well, we'll have to look into that. We'll have to figure out how we can change the process so that that doesn't happen again.' Because of course, I mean, I probably could have avoided that mistake if I thought about things in a different way. But what he said was that we should have a process where you know, that you should do this at this point in time, that should help you, support you. And I thought that was one of the things that created psychological safety for me because now I felt much safer about saying that I had a problem or made something wrong. Ula Ojiaku: In facilitating retrospectives, because you mentioned earlier that if there was anything you could talk about at length, you know, without needing preparation, it would be about the mistakes you've made in facilitating retrospectives. And hence, maybe they could also be some of you know, lead to some of the Antipatterns, could you share some of these Retrospective Antipatterns that you've observed? Aino Corry: So one of the Retrospective Antipatterns that I see most often or that I ran into most often myself is the one that I called Prime Directive Ignorance. So the Prime Directive is what Norman Kerth wrote about retrospectives. There was a longer text that states ‘everybody did the best they could at all times, and remember that before you enter a retrospective', but the problem is that, at least in some of the organizations that I've worked in with some of the people that have worked, they thought it was a bit ridiculous to expect that everybody did the best they could all the time. And to really believe that they couldn't have done any better, because they knew that somebody was slacking. They knew that somebody was being lazy. They also knew that they themselves didn't do the best they could. Aino Corry: So how could they really, genuinely believe that? So sometimes I've had retrospectives where I didn't, I didn't state that, I didn't say it out loud, I didn't state in an email or the invitation, I didn't say remember, this retrospective is not about finding a scapegoat or naming and blaming, it's about figuring out how we as a system of people can move on better together. And then I've had some awful retrospectives where some people had been made scapegoats, and they got really sad, and some of them left the retrospectives because they didn't feel safe. And then, and I think some of them may never have entered a retrospective again because it really ruined it for them because in their head now, the retrospective is a free for all, just sending arrows towards somebody, some poor person and shaming them and blaming them. So I think that the Prime Directive Ignorance Antipattern is one of the most important ones and the refactored solution, obviously, in the Prime Directive Ignorance is not to ignore the prime directive. So remember to bring it, put it on the poster in the wall, say it out loud, write it in the email, you can do it with your own words, it doesn't have to be in Kerth's words, if you like your own words better. But just make sure that people try to do that. Because the thing that Norman Kerth wanted to achieve with this was that people had the mindset of everybody did the best they could. But it's difficult to have that mindset. We're probably all brought up with our parents asking who left the milk out on the morning table? Who broke that vase, who started that fight, right? We're always trying to find a scapegoat and punish them. Although it's not very constructive, not even with children, and not even with grownups either to find that, it's, it's better to figure out how can they play? And where can they play so that they don't break the vase? How can we remind people to put milk into the refrigerator? Instead of saying you're stupid, you're forgetful, you're lazy, right. But I also appreciate that it might be a bit naive, that you might think, okay, but they could have just done a little better. But helping them out with processes, I think it's a good idea. Ula Ojiaku: With reference to the Prime Directive, you know, one of my mentors said something to me that also stuck which is that, you know, most people come to work wanting to do their best job, but sometimes it's the system that restricts them. So if we, like you said, you know, kind of move away from trying to find a scapegoat or someone to point the finger at, you know, to blame for what's going wrong, can we look at how we can shape the system in such a way that those things, you know, it would be hard to fall into those mistakes because the system is already shaped in a way that would help them focus on the right behaviours and practices and not fall into the wrong undesired ones? Yeah. Amazing. Any other Antipatterns you'd like to share? Aino Corry: Yeah, I think that the other one I'd like to share is one that I am becoming more and more aware of how important it is with so many people starting to facilitate retrospectives, because so many people are understanding how powerful it is. A lot of people who maybe aren't, let's say fully dressed, not very experienced in facilitating retrospectives are being thrown into facilitating retrospectives, by people thinking that it's easy. And it's not easy. It's really, really hard. It's hard to do it right. It's easy to understand, but it's difficult to do, it's like that one minute to learn, a lifetime to master. And a lot of people become disillusioned. So one of my retrospective anti-patterns is called the disillusioned facilitator. Because a lot of people are thrown into this role of oh, you can start facilitating retrospectives next week. And then they, maybe they hear something in a podcast like this, oh, this is an activity, you should definitely try it, or they read it online, and then they do it. But then probably they haven't done it before. They're doing it in real life the first time and they might be a bit, not really sure about it, not really having the heart in it. And people can feel that right away. And then they won't put their heart into it either, and then it will fall to the ground, you won't get what you expect to get out of it. So, I always encourage people when they start facilitating to try doing it in a sandbox, first, try out the activities with somebody that you trust and know, maybe you have some other people who want to learn how to facilitate retrospectives, and then you can try these activities out with them. Because explaining these activities can be difficult, coming up with examples that make people understand what they should do can be difficult. But also, really understanding what is the expected outcome, as we talked about right in the beginning Ula, the learning goals, what is it actually that you want to achieve? You're not doing the activity to do the activity, you're doing the activity to achieve something, to figure out what it is you want to achieve makes it easier to perform the right way. So with the disillusioned facilitator what I'm trying to say is, don't worry, you're doing your best the prime directive holds for you as well. Try it out with people, start with things that you're absolutely sure of, take boring activities for a start if you understand how to explain them. And if you understand what the expected outcome is. And we remember to debrief after the exercises to make sure that the people in the retrospective understand what they just got out of it. Because sometimes if you go just from one activity to the other, maybe they're wondering, why did we do that? Why did we spend half an hour on that? They don't understand that actually, what we got out of it was sharing this experience, or perhaps seeing the weight, how many people thought this or something like that? Ula Ojiaku Yeah, never assume, I guess is the cardinal rule there, don't assume, explain why you're doing what you're doing. You're carrying them along on a journey. And you have to (do so) like a good tour guide. This is what I, I tell the teams I coach or some of the coaches that I'm coaching: you're a tour guide, so you have to, you know you're saying ‘this is the destination we're going (to)' and as we get to some notable, you know, attraction points, call it out to them, because you can't assume that everyone is following. Aino Corry No, no Ula Ojiaku Amazing. Now what books, in addition to yours, can someone who wants to learn more about retrospectives and activities, ideas for activities to run during retrospectives? What books would you recommend to them? Aino Corry Well, the interesting thing about retrospectives is that there's a lot of different books that apply. Like when we talked about teaching computer science, it's not just computer science. It's also psychology, ethnography, neurology, things like that. And when you want to become a good retrospective facilitator, you also have to look at other things. You have to look at books about body language. A book that I keep returning to is the book Coaching Agile Teams (by) Lyssa Adkins. It's not necessarily about retrospectives, there is a little bit about that in there, but Coaching Agile Teams is about all the different ways of thinking about helping people coming from this place to this place. And that's actually what retrospectives is about. But also Jutta Eckstein has written the book Retrospectives for Organizational Change. And I think that's important as well to think about retrospectives in a different setting because then you might see that okay, so these retrospectives that you have been asked to do every sprint for a team, maybe that's actually something you can use for the whole organization to help a change or something like that. So I think sort of not just talking about the retrospective books, but other books in general about coaching or communication are very important. Ula Ojiaku: Fantastic. So are you on social media? And how can the audience who would want to get in touch with you do so? Aino Corry: Yeah, I'm on LinkedIn. LinkedIn, I think Aino Corry, just that link, and I'm on Twitter with my name, @apaipi. I'm also on Instagram, but I never use it. So that's the best place to reach me. And it's really easy to Google me because as with you, we probably have very unique names. Ula Ojiaku: Yes, yes, definitely. Aino Corry: And I have to say, Ula, thank you for that thing from the coaching that you said about pointing out the different parts of the landscape in the journey that people might not have noticed. I think that's a very, very good analogy that I'll use in my retrospective teaching as well. Ula Ojiaku: You're very welcome for that. Thank you for that. Thank you. You're welcome. Any final words before we just wrap this whole thing up? Aino Corry: Yeah, make sure you have something that you enjoy every day in your life. Ula Ojiaku: Amazing. Thanks again Aino.

On today's podcast, Bill speaks with Jutta Eckstein, who shares her passion for sustainability and concerns that agile may increase our carbon footprint. Jutta shares how you can make a difference in your personal life and career using the three pillars of sustainability: People, Planet, and Profit.     Article: Leveraging the Agile Manifesto for More Sustainability Website Sustainability Twitter LinkedIn

Die Klima-Katastrophe ist eine der wichtigsten Herausforderungen, denen wir uns stellen müssen. Dieses Panel diskutiert, was Software-Entwicklung dazu beitragen kann. Links SoftAWERE: Tools and Labels for Energy-efficient Software Applications scaph repl schnittstelle Scaphandre: metrology agent dedicated to electrical power consumption metrics Intel RAPL Intel: Running Average Power Limit Energy Reporting Stackoverflow: How does Intel's RAPL estimate the power consumption? Reading RAPL energy measurements from Linux Intel Open Source Blog zu RAPL EET: A Device to Support the Measurement of Software Consumption Buch: Software Sustainability mit einem Kapitel von Jutta Umweltbundesamt: KPI4DCE: Das ressourceneffiziente Rechenzentrum – Kennzahlen und Indikatoren Umweltbundesamt zu KPI3DCE 2.0 Open Source Library für das Messen von Strom/Embedded CO2 einer Server-Side Software Anwendung von Max Code Repository Blog The Hippocratic License Hippocratic - An Ethical License for Open Source Projects Developers for Future Artikel in der c't zum Thema Episode zu Klimawandel & Software Architektur mit Martin Lippert und Stefan Roock

Welcome to the New Year! In this special episode of the ACN, we talk with members of the Supporting Agile Adoption Initiative about their unique perspective on hybrid work trends with companies. Plus, what the data tells us about the effectiveness of hybrid work, work-life balance, and other advice to help make this way of work successful in your business.  Joining the episode are  Hendrik Esser of Ericsson,  Eric Abelen of ING,  Darja Smite of Blekinge Institute of Technology, Jutta Eckstein of IT communication, Jorgen Hesselberg of Comparative Agility, Jens Coldewey of Improuv,  Marcin Floryan of Spotify, and Ray Arell of Agile Alliance.  (00:00) Introduction(02:25)  Meet the Supporting Agile Adoption Initiative members(13:40)  Hybrid Work(50:52)  Wrap upThis podcast is licensed under CC BY-NC-ND 4.0.  If you want more information about the Agile Coaching Network.  Please go to AgileCoachingNetwork.org   Also, become a member of our nonprofit!  It supports our show and helps to build a great Agile community. Support the show (https://www.agilealliance.org/membership-pricing/)

Unser #AgileGrowthCast, diesmal mit Jutta Eckstein, einer Frau, die mehr Agilität gelebt und gestaltet hat, als die meisten von uns. Hör Dir dieses faszinierende Interview an und erfahre mehr über die Anfänge von Scrum und Agilität, Juttas Lernerfahrungen aus ihrem Burnout und wie sie Aufträge auswählt, die zu ihr passen.

Gisela Strnad spricht mit Jutta Eckstein, Buchautorin, Softwareentwicklerin und Coach über „Agil und BOSSAnova – Neuer Trend / neue Welle – was muss sich verändern!“. Jutta Eckstein sagt: „Agil ist cool und ich bin überzeugt, das es immer noch ein Trend ist. Es wird sich aber sicherlich niemand trauen zuzugeben, dass Software nicht agil entwickelt wird.“ Bei Agiler Software betreten alle Beteiligen „Neuland“. Agilität ist nicht nur in der Softwareentwicklung wichtig, auch in der Unternehmenswelt müssen wir agiler werden. Wir leben lt. Jutta Eckstein in einer „VUCA Welt“ – Volatil, Unsicher, Complex und Mehrdeutig (ambiguous), daher wird es immer schwieriger langfristige Pläne aufzustellen. Durch die immer notwendige Nachhaltigkeit muss in Zukunft ein stärkeres Bewusstsein geschaffen werden, das Software Nachhaltig entwickelt werden muss. 2030 wird die IT etwas 21 % des Stromverbrauches benötigen. Um auch weiterhin, Software in dem Masse entwickeln zu können, wie sie benötigt wird, müssen wir Frauen für den Beruf der Softwareentwicklerin begeistern. Nur dadurch können wir das Gap der offenen Stellen Mittel- und Langfristig verkleinern. „In den nächsten Jahren muss in der Softwareentwicklung, ein stärkeres Bewusstsein für Nachhaltigkeit und Diversität erfolgen“, sagt Jutta Eckstein.

In this episode I speak with Jutta Eckstein & John Buck about the Bossa Nova framework. This integrated approach combines Beyond Budgeting, Open Space, Sociocracy and Agile to improve company wide agility. --- Send in a voice message: https://podcasters.spotify.com/pod/show/comparativeagility/message

Agile Projekte bieten spezielle Herausforderungen für Architekt:innen. In dieser Folge diskutiert Jutta Eckstein diese Herausforderungen und wie man mit ihnen umgehen kann.

Ein Auszug aus dem Buch „Unternehmensweite Agilität“, auch „BOSSA nova“ genannt, von Jutta Eckstein und John Buck (Vahlen Verlag 2019)

Lesung der Kurzgeschichte „Cost of Delay“ von Jutta Eckstein aus dem Buch Agile Short Stories

Scrum ist vor kurzen 25 Jahre alt geworden. Grund genug sich mit einigen Urgesteinen unserer agilen Szene zu unterhalten und zu ergründen, wie die Anfänge im DACH-Raum waren und was diese von heute unterscheiden. Es hat sehr viel Spaß gemacht sich mit Andreas Schliep, Christoph Mathis, Jutta Eckstein und Jean-Pierre Berchez auszutauschen. Ich wünsche euch viel Spaß beim Zuhören.

Robby speaks with Jutta Eckstein; coach, consultant, trainer, speaker, and author. They discuss the importance of being able to deliver continuously, the difference between technical debt and gold plating, and the challenges of synchronous vs asynchronous communication during a global pandemic. Jutta also talks about why teams need to consider the carbon footprint of their cloud infrastructure and doing what we can to reduce e-waste.Helpful LinksJutta's WebsiteJutta on LinkedInJutta on Twitter[Book Recommendation] Invisible Women: Data Bias in a World Designed for Men, Caroline Criado PerezSubscribe to Maintainable on:Apple PodcastsOvercastSpotifyOr search "Maintainable" wherever you stream your podcasts.

Welcome to the New Year!  In this special episode of the ACN, we are talking with members of the Supporting Agile Adoption Initiative about their perspective on Agile as it gains or loses momentum within companies.  We also explore how Agile moves forward as it hits its 20th anniversary as a mindset and set of methodologies.    Joining the episode are  Hendrik Esser of Ericsson,  Eric Abelen of ING,  Bjarte Bogsnes of Equinor, Jutta Eckstein of IT communication, Jorgen Hesselberg of Comparative Agility, Jens Coldewey of Improuv,  Marcin Floryan of Spotify,  John Buck of Governance Alive, and Ray Arell of Agile Alliance.  (00:00) Introduction(01:28)  What each member learned in 2020(16:11)  Waves in Agile(30:25)  Agile at 20 and what is next(49:52) Wrap upThis podcast is licensed under CC BY-NC-ND 4.0.  If you want more information about the Agile Coaching Network.  Please go to AgileCoachingNetwork.org   Also, become a member of our nonprofit!  It supports our show and helps to build a great Agile community. Support the show (https://www.agilealliance.org/membership-pricing/)

Viele Unternehmen wollen sich komplett agil aufstellen – anhand von Arbeitsprinzipien, wie sie im Agilen Manifest beschrieben sind. Der Haken: Diese Prinzipien beziehen sich auf Prozesse. Unternehmen haben aber auch eine Struktur und eine Strategie. Wollen sie agil werden, müssen sie auch die verändern. Mit dem Agilen Manifest allein klappt das nicht, sagt Agilitätsexpertin Jutta Eckstein – und schlägt einen reicher bestückten Werkzeugkoffer für die agile Skalierung vor.

Viele Unternehmen wollen sich komplett agil aufstellen – anhand von Arbeitsprinzipien, wie sie im Agilen Manifest beschrieben sind. Der Haken: Diese Prinzipien beziehen sich auf Prozesse. Unternehmen haben aber auch eine Struktur und eine Strategie. Wollen sie agil werden, müssen sie auch die verändern. Mit dem Agilen Manifest allein klappt das nicht, sagt Agilitätsexpertin Jutta Eckstein – und schlägt einen reicher bestückten Werkzeugkoffer für die agile Skalierung vor.

Viele Unternehmen wollen sich komplett agil aufstellen – anhand von Arbeitsprinzipien, wie sie im Agilen Manifest beschrieben sind. Der Haken: Diese Prinzipien beziehen sich auf Prozesse. Unternehmen haben aber auch eine Struktur und eine Strategie. Wollen sie agil werden, müssen sie auch die verändern. Mit dem Agilen Manifest allein klappt das nicht, sagt Agilitätsexpertin Jutta Eckstein – und schlägt einen reicher bestückten Werkzeugkoffer für die agile Skalierung vor.

Ich spreche mit Jutta Eckstein über den Data Driven Approach für Unternehmensweite Organisationsentwicklung und der Narrathon auf dem Weg zu einem Kulturwandel!

Too many products have been developed that serve one kind of client only. The reason is that the composition of the teams leads (subconsciously) to the development of products that serve only people that resemble the people in the team. One “famous” example is the soap dispenser that only works if your skin is white. If teams are really cross-functional and are resembling the diversity of the market, the products they’re creating are also better. Thus, if the whole team has the full business expertise, knows the market, reflects the full diversity of the clients, then it can even disrupt the market and isn’t waiting for some person (e.g. the Product Owner) to decide on priorities. With this real cross-functionality, the team can fully understand the company’s business and has a holistic view of it, knowing its contribution to the company’s value stream. Join us in a Panel dialogue with Jutta Eckstein and Maryse Meinen about that real cross-functional teams are an essential building block for implementing company-wide agility and the organization benefits by creating better and in a way more real products and by having more options when entering the war of talent.

Jutta Eckstein is the guest of episode 10. She will share her thoughts on the heuristic “Favor continuous improvement over delayed perfection” front he Xebia Essentials repository (https://essentials.xebia.com/improve-continuously/). We will discuss the trade-offs between goals set in stone and agility, and how values can help in that journey. Using reflection as a foundation to improve through experiments, where individuals, teams and organisations can generate new insights. As an example, using continuous retrospective, where the retrospective honours the context. We end up discussing the skills of the new generation of leaders and how organisations should face VUCA times. Jutta recommends BOSSA Nova (https://www.agilebossanova.com/) as a resource for this episode. Jutta (@juttaeckstein) is an experienced independent coach, consultant, and trainer for agile software development. Her know-how in agile processes is based on over twenty years of experience in project and product development. She is an experienced agile process coach and trainer. She has worked with teams using agile processes successfully on medium-sized to large mission-critical projects. As a coach, she is focusing on the process as well as on the quality and soft factors like communication. She also works as a facilitator for retrospectives. With retrospectives, she helps her clients to improve their way of working. She has presented work in her main areas of expertise at different European and American conferences. She is a member of the Agile Alliance, where she served the board of directors, a supporter of the Manifesto for Agile Software Development and a member of several Interest Groups. She is a partner of IT Communication.

Hvordan skal vi organisere arbeidstakere så det ikke er en dissonans mellom det som er strategien og det de ansatte ser på som mulig å oppnå? Og hvilken evne og kompetanse må organisasjonene ha for å klare å gjennomføre digital transformasjon? I denne episoden av #LØRN snakker Silvija med Rådgiver innen digital transformasjon og prosjektleder for Kompetanseløft Trøndelag, Eirin Folde om Strategi, struktur og kultur i en teknologidrevet verden. — Vi vil bort ifra en "null-feil-kultur" i offentlig sektor, det skal være lov å gjøre feil for det er da vi lærer, forteller hun i episoden. Dette LØRNER du: Strategi og kultur Livslang læring Strategi og kultur i digital transformasjon, Å minske gapet mellom det man sier og det man gjør Budsjettering for fremtiden Anbefalt litteratur: Digital transformation av Pernille Kræmmergaard Company-Wide Agility with Beyond Budgeting, Open Space & Sociocracy: Survive & Thrive on Disruption av Jutta Eckstein og John Buck. Agile Practice Guide ved Project Management Institute Machine, Platform, Crowd: Harnessing Our Digital Future av Andrew McAfee og Erik Brynjolfsson Seeing: "Den tredje industrielle revolusjonen: En radikal ny delingsøkonomi" ved Jeremy Rifkin The Third Industrial Revolution: A Radical New Sharing Economy See acast.com/privacy for privacy and opt-out information.

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

Craig and Tony are at YOW! conference in Brisbane and chat with Jutta Eckstein, author of “Agile Software Development in the Large“, “Agile Software Development with Distributed Teams“, “Retrospectives for Organisational Change” “Diving for Hidden Treasures: Uncovering the Cost of Delay in Your Project Portfolio” with Johanna Rothman and “Company-wide Agility with Beyond Budgeting, Open … Continue reading →

An exclusive interview with the Supporting Agile Adoption Initiative at their yearly meeting in Stockholm, Sweden.   Attendees included Hendrik Esser of Ericsson,  Eric Abelen of ING,  Bjarte Bogsnes of Equinor, Jutta Eckstein of IT communication, Jorgen Hesselberg of Comparative Agility, Jens Coldewey of Improuv,  Marcin Floryan of Spotify,  John Buck of Governance Alive, Elena Vassilieva of Ericsson, and Ray Arell of Agile Alliance.  We talk about organizational design in Agile companies to promote higher contextual awareness and coordination between parts within companies.  We also talk about sustainability and how development teams can help innovate and create a  sustainable future.      (00:00) Introduction(02:35) What is the Supporting Agile Adoption Initiative (07:47) Organizational Design and Octopus Structures(36:31) Sustainability(46:54) Wrap upThis podcast is licensed under CC BY-NC-ND 4.0Support the show (https://www.agilealliance.org/membership-pricing/)

Richard Kasperowski interviews Jutta Eckstein. Jutta is an Agile coach, consultant, and trainer. She is the author of the books "Company-wide Agility", "Retrospectives for Organizational Change", and "Agile Software Development with Distributed Teams". Jutta and I chat about the importance of small rituals and striving to build great development teams. She then reveals to us the secrets of the Bossa Nova approach to business agility! Connect with Jutta on Twitter at https://twitter.com/JuttaEckstein or on LinkedIn at https://de.linkedin.com/in/juttaeckstein and visit her web-site at www.jeckstein.com. Read the full transcript at https://kasperowski.com/podcast-26-jutta-eckstein/ ‎

Diana and I were kicking around a few topics for this episode, and we ended up selecting “Agile and Leadership, friends or foes?” The idea is to talk about how Agile and Leadership play together (or not) In this episode, we talk with Diana Larsen and Jutta Eckstein about what problems Leaders try to fix with Agile, what challenges they have when they try to adopt Agile, and we will do this with the focus on the Scrum Master role, and what they can do by working with the leaders of the organizations they work within. Full show notes are available at https://scrum-master-toolbox.org/. About Diana Larsen and Jutta Eckstein Diana Larsen co-founded and collaborates in leadership of Agile Fluency™ Project. Diana co-authored the books Agile Retrospectives: Making Good Teams Great; Liftoff: Start and Sustain Successful Agile Teams; Five Rules for Accelerated Learning; and the seminal “Agile Fluency Model: A Brief Guide to Success with Agile” article. You can link with Diana Larsen on LinkedIn and connect with Diana Larsen on Twitter.    Jutta Eckstein works as an independent coach & consultant.  As a developer, she started with XP in 97/98, started scaling agile in 2001 (and published about that in 2004), and am now Jutta focuses on company-wide agility. You can link with Jutta Eckstein on LinkedIn and connect with Jutta Eckstein on Twitter.  You can learn more at Jutta Eckstein’s website, and check out Jutta’s books on Amazon and LeanPub. Jutta’s Agile Bossanova book is available here. 

Rob Fitzpatrick on The Art of Product, Joshua Kerievsky on Being Human, Marty Cagan on Build by Drift, Jutta Eckstein and John Buck on Agile Uprising, and Jocelyn Goldfein on Simple Leadership. 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 June 24, 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. ROB FITZPATRICK ON THE ART OF PRODUCT The Art of Product podcast featured Rob Fitzpatrick with hosts Ben Orenstein and Derrick Reimer. They talked about Rob’s book, The Mom Test. He wrote it for “super-introverted techies” like himself but found it resonated with a wider audience. He explained that one of the reasons he self-published the book is because, when he took it to a publisher, they wanted him to increase the word count simply because they believed, with no evidence, that business books below 50,000 words don’t sell. The hosts asked Rob to describe “The Mom Test” in his own words. He described how, just as you shouldn’t ask your mom whether your business is a good idea because she’s biased, you need to be careful when asking anyone whether they think your business is a good idea. This, he says, puts the burden on them to tell you the truth. Instead, he says you should put the burden on yourself of coming up with questions that are immune to bias, so immune that even your mom would give you an unbiased answer. Rob talked about how the value of customer conversations is proportional to how well the problem you are trying to solve is defined. For products like Segway or Uber or a video game, asking customers questions about the problems they want solved is not as effective as it would be when the product is enterprise software. Derrick talked about how, when The Lean Startup started becoming big, it led him to what he calls “idea nihilism” where he started to believe the idea doesn’t matter at all, it is one hundred percent the journey, and the future is unpredictable, so just build something. The next few things he built while in this mindset either did not get off the ground or led him to ask himself why he built a business he hated. Eventually, he concluded that the idea matters a lot. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/90-the-mom-test-with-rob-fitzpatrick/id1243627144?i=1000440137442 Website link: https://artofproductpodcast.com/episode-90 JOSHUA KERIEVSKY ON BEING HUMAN The Being Human podcast featured Joshua Kerievsky with host Richard Atherton. What I loved about this interview is that Joshua described many of the inspirations behind the Modern Agile principles. The first principle, “make people awesome,” was inspired by Kathy Sierra and her focus on making the user awesome. They originally called it “make users awesome” and realized that there is a whole ecosystem besides the end consumers, including colleagues, management, and even shareholders, to make awesome. He clarified that the word “make” is not coercive, but about asking you what you can do to empower others. Regarding the second principle, “make safety a prerequisite,” he talked about being inspired by a story in Charles Duhigg’s The Power of Habit about Paul O’Neill and his turnaround of the hundred-year-old Alcoa corporation. Just as Amy Edmondson had connected psychological safety to physical safety in a previous podcast, Joshua connected psychological safety to product safety. He clarified that making safety a prerequisite doesn’t mean avoiding risk. Speaking about the third principle, “experiment and learn rapidly,” he told the story of the Gossamer Condor, the human-powered aircraft that was created to win the Kremer prize. The team that built the Condor engineered their work so that they could fail safely. The airplane flew two or three feet from the ground and the materials they used were expected to break and be repaired quickly. This let them do multiple test flights per day while their competitors would go through a waterfall process that led to large times gaps between test flights. Finally, he described the fourth principle, “deliver value continuously,” as finding a way of working where you can get feedback early and learn from it, delivering value each time. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/62-modern-agile-with-joshua-kerievsky/id1369745673?i=1000440221993 Website link: http://media.cdn.shoutengine.com/podcasts/4081235a-554f-4a8f-90c2-77dc3b58051f/audio/303a9472-75ef-4e7f-94e5-414a3018750a.mp3 MARTY CAGAN ON BUILD BY DRIFT The Build by Drift podcast featured Marty Cagan with host Maggie Crowley. Marty says that when he shows teams the product discovery techniques he described in his book, Inspired,he finds that they understand the value of the techniques but too often they are not allowed to use them. Instead, their leaders hand them a roadmap and tell them to just build features. When he talks to these leaders, he asks, “Why are you doing this? You know this isn’t how good companies work.” The answer, though not always admitted, is that they don’t trust the teams and, as a result, they don’t empower them. They talked about the defining characteristics of an empowered product team. First among them is for the leadership team to give the product team problems to solve rather than features to build. They also need to staff them appropriately because, if they have been running things the old way long enough, they don’t have the appropriate staff to run things the new way. For example, they may have somebody called a product manager, but they are really a project manager with a fancy title or a backlog administrator. Or they may have designers who are just adding the company color scheme and logo or engineers who are just writing code. Maggie asked what a product leader can tell a stakeholder who is used to thinking in tangible features rather than the problem to be solved. Marty says there is nothing wrong with talking about features, but it is when they get etched into a roadmap that we get into trouble because it becomes a commitment and the time spent on the feature could be better spent on figuring out how to solve the problem. They talked about Objectives and Key Results or OKRs and how they are a complete mess at most companies. The concept is simple and easy if you are already in the empowered team model, but otherwise it is theater because you’re still doing roadmaps while simultaneously trying to tell people the problems to solve. Maggie started describing how they do product discovery and development at Drift and Marty immediately pointed out how the language she used makes the work sound like it occurs in phases as it would in a waterfall project. She explained that they use this notion of phases to communicate out and he pointed out that, even if it is not currently waterfall, there is a slippery slope between speaking about phases and landing in a waterfall mindset. He talked about three things he cares about that distinguish his process from waterfall: 1) tackling the risks upfront, 2) product managers, designers, and engineers literally coming up with prototypes side-by-side instead of having hand-offs, and 3) iterating towards achieving your KPIs rather than having a phase where you’ve declared the design done and have started implementing.  Maggie asked him to enumerate what he thinks product leaders should be doing. First, he said that they need to coach their product managers to get them to competence, which he says should take no more than three months. In the case of hiring product managers straight out of school, the product leader needs to commit to multiple-times-a-week or even daily coaching. Second, he said that product leaders need to take an active role in creating product strategy. This comes back to OKRs where product leaders provide business objectives that product teams translate into problems to solve. The more product teams you have, the less you can expect those teams to be able to see the whole picture on their own, which makes it more important for product leaders to connect the dots for them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/we-talked-to-product-management-legend-marty-cagan/id1445050691?i=1000440847157 Website link: https://share.transistor.fm/s/da82dbda JUTTA ECKSTEIN AND JOHN BUCK ON AGILE UPRISING The Agile Uprising podcast featured Jutta Eckstein and John Buck with host Jay Hrcsko. Jay asked Jutta how she and John came together to produce the ideas described in their book Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy. Jutta and John met at an Agile conference in Atlanta and got the idea to investigate what Sociocracy could bring to Agile. They soon found themselves thinking, “That’s not really all of it,” and immediately agreed to write a book together about it. Jay started going through the book, beginning with four problem statements: Existing concepts cannot be directly applied to company strategy, structure, or process in the VUCA (volatility, uncertainty, complexity, ambiguity) world. Companies make decisions from the top down but often people at lower levels who are closer to the realities of the product or market have valuable insights that are currently ignored. There is a collision of values underlying shareholder interests in short-term profits and a focus on the needs of the customers. For a company to be agile, all departments must be agile. However, existing agile systems struggle when applied to non-engineering departments. Jutta described Beyond Budgeting. She said that it sounds like it only has relevance to the finance department, but there is a close relationship between how companies deal with finance and how they are managed. In contrast to Agile, which originated from the experiences of consultants, she says, Beyond Budgeting originated in the experiences of CFOs. She gave examples of the problems with traditional budgeting: In the first scenario, a company’s budget is set annually and, at some point during the year, a project team that had been allocated a certain budget determines that the market has changed and they no longer need a budget as large as they originally thought. She’s never seen this situation lead anyone to give the money back. In the second scenario, the market changes such that the budget needed for the company to succeed in the market exceeds the original budget and it’s too late for anything to be done. Jay brought up the distinction made in the book about the three distinct uses of budgets: 1. a target, 2. a forecast, and 3. capacity planning, and the fact that these should not be combined. Next, they discussed Open Space. John talked about the Open Spaces you often see at conferences and how they increase creative thinking and allow people’s passions to emerge. In the same way, Organization Open Space, where you can come up with a project, line up some people, and go to work, gives you passion bounded by responsibility that leads to creative companies.  John pointed out that the combination of the three concepts, as he and Jutta developed the book, started to interact and come together in ways that made it greater than the sum of its parts. That’s why they gave it a name: BOSSA nova.  Jay brought up how he has already benefitted from what he learned about Sociocracy in the book. He was able to help his colleagues learn about the difference between consent and consensus. The participants in a meeting had been locked in an argument over a maturity model when Jay restated the subject of the disagreement in terms of consent, asking if there was anyone who needed to put a stake in the ground for their position or would they all be willing to let an experiment proceed. This quickly unblocked the stalemate. John related a similar story about helping a group of professors make some decisions about forming a professional association. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/bossa-nova-with-jutta-eckstein-and-john-buck/id1163230424?i=1000440982639 Website link: http://agileuprising.libsyn.com/bossa-nova-with-jutta-eckstein-and-john-buck JOCELYN GOLDFEIN ON SIMPLE LEADERSHIP The Simple Leadership podcast featured Jocelyn Goldfein with host Christian McCarrick. Jocelyn talked about her career, including some time starting her own company, rising in the ranks at VMWare, arriving at Facebook at a critical time in its history, and becoming an angel investor and a venture capitalist. Christian asked about one of Jocelyn’s tweets about motivation as a management superpower. She says that engineers have a lot to offer the discipline of people management because they know how to think about systems problems and most organization problems are systems problems. On the other hand, engineers sometimes lose sight of the fact that human systems are different from programmatic systems in that they have feelings and don’t always behave rationally, but people respond to incentives. Explanations of the importance or urgency of a particular effort and attaching a bonus to it are blunt instruments, but praise and encouragement satisfies people’s needs and engenders long-term loyalty in a way that other incentives don’t. They talked about one of my favorite blog posts of Jocelyn’s on culture. She says that culture is what people do when nobody is looking. It is not people following an order. It is people knowing what to do when they don’t have orders. She says that people often think that culture is a set of traits or qualities and that you can interview for those traits to find someone who is a “culture fit.” She disagrees with this because companies are different from one another and people are obviously portable between companies.  Christian brought up the example of companies that have posters on their walls describing their culture. To Jocelyn, people are less than 10% influenced by the poster on the wall and more than 90% influenced by what successful, powerful people in the company do. When these are in conflict, you get cynicism. She talked about how compensation can be a motivator, but she noted that other people cannot judge your success by your compensation because they don’t know it, so they look for other indicators like title, scope of responsibility, influence, and confidence. So she says you need to be careful when handing out overt status symbols like titles and promotions because people will emulate the recipients of such symbols. The classic example, she says, is the brilliant jerk. When you elevate the brilliant jerk, you’re sending a message that people who succeed in this company and get ahead are jerks. The poster on the wall may not say that, but people will attach more weight to your behavior than what you or the poster say. Jocelyn talked about the undervaluing of soft skills. Engineers are taught early on that their work is fundamentally solo work and she says that is a lie because, if you want to do anything significant, if you’re going to go from rote work to meaningful creative work, the crucial skills are the soft skills we’re taught to disdain or neglect. Regarding recruiting and hiring, she talked about the tendency, at least at Facebook, to treat the phone screen like an on-site interview and create false negative rates that are too high. She did her own test where she brought in for on-site interviews a set of candidates who had previously been rejected at the phone screen stage and found that the same number got hired from her screened-out pool as were hired from the pool of candidates that passed their phone screen. She talked about the benefits and disadvantages of the centralized hiring model. On the plus side, it reduced silos, made teams friendlier to one another, and made employees become citizens of the company first and citizens of the team second. The downside of the centralized model is that there is no hiring manager taking responsibility, so the responsibility passes to the recruiter. Her preference is a blended model that is mostly centralized but with hiring managers taking responsibility and receiving rewards and praise for taking that responsibility. I loved what Jocelyn had to say about diversity and inclusion. She said that when we’re working at these high-growth companies, we’re desperately seeking to hire, we’re interviewing everybody, and we’re hiring everybody who is above our bar. When we look at the result and it is only 5% or 10% female and single digit percentages black or hispanic, some part of us is thinking that must reflect the inputs and to get a different population I would have to lower my bar and accept people who are failing. But this assumes a few things: that your interview bar is fair and that the population who applies to work at your company is the population who could apply to work at your company. If you really value having a more diverse environment, you will go looking for them. If you just sat there and only looked at applicants, you would never have hired that one signal processing engineer you needed or that one esoteric role that is not there in your applicant pool. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/how-to-improve-your-management-skills-jocelyn-goldfein/id1260241682?i=1000440957474 Website link: http://simpleleadership.libsyn.com/how-to-improve-your-management-skills-with-jocelyn-goldfein 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/c/TheKGuy Website:

Sociocracy.  Openspace.  Beyond Budgeting.  Agile.  All these ideas are out there in the ecosystem, but can you combine them all to realize true agilty in your organization and create an agile environment that can't help but to succeed...?  In this episode Jutta Eckstein and John Buck sit down with Jay to discuss BOSSA nova, and how these concepts can all work together to enable true growth.  Enjoy!   Agile BOSSA nova website Jutta's Twitter John's Twitter BOSSA nova @ Amazon

Welcome to the KnolShare with Dr. Dave podcast, hosted on Grokshare.com and streamed on iTunes, Google Play, and Spotify.   You are listening to Episode #10 of the Agile For Humanity Tucson Meetup Webinar Series featuring Jutta Eckstein.  The topic is BOSSA nova: Beyond Agile – Preparing for Digitalization.  BOSSA is an acronym that means: Beyond… The post EAFH-10: Jutta Eckstein – BOSSA nova: Beyond Agile – Preparing for Digitalization appeared first on Leaders share how-to practices - KnolShare with Dr. Dave Podcast on GrokShare.com.

Als heutigen Interviewgast darf ich Jutta Eckstein begrüßen. Sie bezeichnet sich selbst als Dinosaurier in der agilen Szene und hat bereits einige Bücher veröffentlicht. Schon seit den 90-er Jahren ist sie als Beraterin und Change-Managerin bei der Umsetzung von agilen Prozessen tätig.  Als Überraschung verlosen wir Juttas aktuelles Buch „Bossa Nova“ am Ende der Folge und zwei weitere Bücher von mir. In dieser Podcastfolge sprechen wir über Juttas Definition eines passionierten, leidenschaftlichen Teams und welche wichtigen Kriterien dafür zu beachten sind. Zudem stellen wir dir Juttas neues Buch „Bossa Nova“ vor.   Agilität bedeutet, als Team ein gemeinsames Ziel zu haben Um ein passioniertes, leidenschaftliches Team zu beschreiben, steht für Jutta im Mittelpunkt, ein gemeinsames Ziel vor Augen zu haben. Dadurch kann jeder gleichermaßen auf seine Art und Weise dazu beitragen, das Ziel gemeinsam zu erreichen. Jedes Teammitglied sollte zudem genau verstehen, weshalb das Erreichen des Zieles so wichtig ist.   Wenn das verbindende Element fehlt, gibt es kein Miteinander   Es ist sehr wichtig, ein gemeinsames Ziel zu definieren. Wenn dies nicht geschieht, kann auch keine gemeinsame Teamleistung erbracht werden. Das Ziel dient sozusagen als verbindendes Element.  Ebenso ist auch eine gewisse Offenheit wichtig, um etwas Neues zu lernen und die Bereitschaft, Wissen an andere weiterzugeben.     „Bossa Nova“ - so machst du dein Unternehmen mit Agilität, Beyond Budgeting, Open Space und Soziokratie fit für die Zukunft   Das Buch, welches Jutta Eckstein gemeinsam mit John Buck geschrieben hat, besteht aus vier Elementen. Daraus setzt sich gleichzeitig der Name des Buches zusammen.  Diese Elemente beschreibt uns Jutta im Interview genauer: B = Beyond Budgeting  OS = Open Space S = Soziokratie  A = Agilität   Weiterentwicklung ist der einzige Weg Um deine agile Reise zu starten, möchte dir Jutta Folgendes mit auf den Weg geben: Entwickle dich ständig weiter, da sich unser Markt fortlaufend verändert. Erwarte nicht, dass es für alle Situationen vorgefertigte Rezepte gibt, sondern beleuchte deine aktuelle Situation und handle entsprechend.

Joe Krebs speaks with Jutta Eckstein about Beyond Budgeting, Open Space and Sociocracy to enable company-wide agility. Jutta shows the synergies to Business Agility and how an agile mindset, driven by the Agile Manifesto is essential for successful company-wide agility.

Jutta Eckstein co-authored together with John Buck the book with the title "Bossa Nova" which covers company-wide agility with Beyond Budgeting, Open Space Technology and Sociocracy. Jutta links company-wide agility to the values, principles and mindset off the Agile Manifesto and proves it still to be up-to-date. The subtitle of the book "Survive and Thrive on Disruption" outlines why agility is so crucial when agile is applied across all parts of an organization.

A special holiday episode with the Agile Alliance's Supporting Agile Adoption (SAA) initiative team talking about the 12 principles of Agile in Amsterdam. Hendrik Esser, Jens Coldewey, Jorgen Hesselberg, Jutta Eckstein, Bjarte Bogsnes, Boris Kneisel, Marcin Floryan, and Eric Abelem. (01:09) SAA team introduction, (02:40) Is it really just about software?, (11:12) Reflecting on our work, (18:20) Business people and developers working together daily, (27:25) Self Organization and motivated individuals, (36:13) Welcoming requirements even late in development, (43:15 ) Face-to-face communications is it outdated?, (50:02) What is Supporting Agile Adoption?, (52:44) More info on Beyond Budgeting, (53:20) Wrap up.Support the show (https://www.agilealliance.org/membership-pricing/)

In dieser Episode reden wir mit Jutta Eckstein darüber, was unternehmensweite Agilität bedeutet und welche Voraussetzungen ein Unternehmen erfüllen muss, um wirklich agil zu werden. Dazu gehören nicht nur die agilen Werte, sondern auch der richtige Umgang mit Investitionen, die richtigen Strukturen und Formate, die Innovation fördern.

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jutta Eckstein and John Buck about their new book: Company-wide Agility with Beyond Budgeting, Open Space and Sociocracy – BOSSA-Nova Why listen to this podcast: • The pressing question: if democracy is good, why aren’t businesses using it • The new book is a theoretical framework for organizations to help agile spread philosophy across whole organizations • Just using Agile company-wide is not enough • In the VUCA times we live in require that companies are able to make quick and fast decisions – sociocracy provides this ability • Beyond Budgeting provides guidance on how finance, accounting, HR and management needs to change in the new environment • Open Space is a great way to bring alignment and commitment into the organization More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2PNUOOp You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2PNUOOp

What do the Brazilian dance Bossa Nova and company-wide agility have in common? According to Jutta Eckstein and John Buck, both are created from a combination of different elements. While the dance is a synthesis of samba and jazz, company-wide agility can be created using the following elements: Beyond Budgeting, Open Space, Sociocracy and Agile - BOSSA nova for short. Jutta is a coach, consultant and trainer with a M.A. in Business Coaching and Change Management. John Buck is a Certified Sociocratic Organizational Consultant. Listen to how they encourage organizations to use these time-tested concepts to begin experimenting at your company to become Agile, and how sociocracy can ensure that the power structure of an organization will uphold company-wide agility, not hinder it. This episode of Agile Amped is part of a series in partnership with the Business Agility Institute. Register for the Business Agility Conference in New York March 14-15 and use code solutionsiq-founding-member to save 25% off registration:businessagilityconf.com/ To find out more about Jutta & John’s book in progress, visit: leanpub.com/bossanova Follow our guests on Twitter: @JuttaEckstein@johnabuckAnd find our podcast host:@howardsublett Podcast library: www.agileamped.com Subscribe to our newsletter: www.solutionsiq.com/agile-amped/ Submit a topic idea: www.solutionsiq.com/submit-a-topic/ Connect on Twitter: twitter.com/AgileAmpedFollow us on Facebook: www.facebook.com/agileampedFind us on Instagram: www.instagram.com/agileamped/

Jutta Eckstein berät seit 1998 vor allem große Firmen und begleitet sie auf ihrem Weg zu mehr Agilität. Während des Retrospective Facilitatörs Gathering 2016 in Sagres habe ich ein Gespräch mit ihr aufgezeichnet.

Im Februar 2001 war das Agile Manifest geboren. In dieser Roundtable-Diskussion machen wir eine Bestandsaufnahme, Reflektion, Analyse: "Was haben sieben Jahre Agile Entwicklung gebracht?"

Guest: Jutta Eckstein Host: Daniel Steinberg Agile software development methods grew up in a context of in-house development, collocated teams, and relatively shared cultural expectations. This made their emphasis on face-to-face communication and common code ownership. But these days, software development is as likely to be developed by international teams as it is by teams sitting in the same room. Terms such as "outsourcing", "offshoring", and "nearshoring" indicate the degree to which agile software developers must work in a context rather different from the one in which their methods have been honed. Over the last decade, Jutta Eckstein, of IT Communication in Germany, has developed a wealth of experience developing object-oriented applications in large organizations, precisely the ones most likely to develop software with distributed, international teams. She has identified ways in which it is possible for such teams to overcome the challenges that global software development, as well as the success factors for implementing an agile software development process within such constraints. Eckstein will teach a tutorial at ooPSLA, titled Agile in Face of Global Software Development, that shares this experience with conference attendees. In this podcast, Eckstein joins Daniel Steinberg of DimSumThinking to talk about how agile software development in the face of trends toward global teams. She offers concrete suggestions for overcoming problems of distance, culture, and time zone in implementing agile approaches.

Guest: Jutta Eckstein Host: Daniel Steinberg Agile software development methods grew up in a context of in-house development, collocated teams, and relatively shared cultural expectations. This made their emphasis on face-to-face communication and common code ownership. But these days, software development is as likely to be developed by international teams as it is by teams sitting in the same room. Terms such as "outsourcing", "offshoring", and "nearshoring" indicate the degree to which agile software developers must work in a context rather different from the one in which their methods have been honed. Over the last decade, Jutta Eckstein, of IT Communication in Germany, has developed a wealth of experience developing object-oriented applications in large organizations, precisely the ones most likely to develop software with distributed, international teams. She has identified ways in which it is possible for such teams to overcome the challenges that global software development, as well as the success factors for implementing an agile software development process within such constraints. Eckstein will teach a tutorial at ooPSLA, titled Agile in Face of Global Software Development, that shares this experience with conference attendees. In this podcast, Eckstein joins Daniel Steinberg of DimSumThinking to talk about how agile software development in the face of trends toward global teams. She offers concrete suggestions for overcoming problems of distance, culture, and time zone in implementing agile approaches.

In this Episode, Arno, Bernd and Markus interview Jutta Eckstein. Jutta is a pioneer and expert on using Agile software development, specifically in larger teams. In the interview we talk about the agile manifesto, the role of personal relationships and trust in software projects, differences between agility in the small and in the large, as well as offshoring.

In this Episode, Arno, Bernd and Markus interview Jutta Eckstein. Jutta is a pioneer and expert on using Agile software development, specifically in larger teams. In the interview we talk about the agile manifesto, the role of personal relationships and trust in software projects, differences between agility in the small and in the large, as well as offshoring.

In this Episode, Arno, Bernd and Markus interview Jutta Eckstein. Jutta is a pioneer and expert on using Agile software development, specifically in larger teams. In the interview we talk about the agile manifesto, the role of personal relationships and trust in software projects, differences between agility in the small and in the large, as well as offshoring.