Podcasts about jorgen hesselberg

This week, Dan Neumann is joined by Justin Thatil and Mike Dionne to discuss the topic of Agile assessments. Let's assume it: No one likes to be assessed since it tends to feel deeply uncomfortable. In this episode, these three colleagues discuss the meaning of an assessment, its purpose (that changes according to different environments), and how to conduct assessments following the Agile methodology.   Key Takeaways First: What are you trying to assess? Remember that data can be changed and looked at in many different ways (what could be a problem). The Assessments at the Scrum Master level are meant to evaluate the current state of a Team. Start with a series of questions for a health check: Do you feel you are listened to by a Team? Do you feel you have a voice? Do you feel the Team acknowledges you? Do you feel safe in that environment? If the answer is “Yes” to all four questions on a 1-5 scale, give it a 5. If the answer is affirmative to only a couple of the questions, give it a 3 or 4; if the answer is ‘Yes” to only one, put a 0 or 1. This process must be repeated, and you will realize that people answer with varying honesty over time. Over the journey, you will notice how the Team dynamics start to pick up. As a result of the assessment, the Scrum Master becomes better informed in his or her role. How is the Team performing? Velocity isn't everything! Other parts of the overall assessment can also give a good perspective regarding a Team's performance. Scrum enables problems to surface faster so that they can be addressed quicker. Velocity is only suitable for predicting how long it can take to finish a group of backlog items. Start with the Team's identity and move to the things that improve the Team's performance to reach the goal you had set. After that, find what you want to improve next. Repeat this process once a quarter. We can control the process, not necessarily the outcome. The whole organization needs to pull in the same direction. The Team needs to be willing to participate in the assessment. If the Team feels the measurement is unnecessary or useless, the assessment won't be used as a tool for improvement, and this metric won't have the value that it was expected to have. Assessments also exist for organizations. How long does it take to develop an idea? Does the organization have the ability to improve?   Mentioned in this Episode: Check this episode: “Jorgen Hesselberg on Data-Driven Continuous Improvement”.   The Tools: 5 Tools to Help You Find Courage, Creativity, and Willpower — and Inspire You to Live Life in Forward Motion, by Phil Stutz and Barry Michels   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!  

This week, Jorgen Hesselberg discusses the efficacy of assessments in helping to guide an agile journey. Assessments are a tool to help coaches coach and to answer the question of where are we in our journey toward being more agile.  Jorgen last appeared in SPaMCAST 557 in 2019 (http://bit.ly/2MiBw4K). Jorgen Hesselberg is the author of Unlocking Agility and co-founder of Comparative Agility, a leading agile assessment, and continuous improvement platform. A proven thought leader of numerous successful enterprise transformation efforts since 2009, Jorgen provides strategic guidance, executive counsel, and coaching to some of the world's most respected companies, both as an internal change agent and an external consultant. He has trained thousands of people on agile and Scrum, disruptive innovation, and enterprise transformation strategy. Contact Information Email: jorgen@comparativeagility.com  LinkedIn: linkedin.com/in/jhesselberg  Comparative Agility:  https://www.comparativeagility.com/product/ Re-read Saturday News! Chapters 14 and 15 of Badass Agile Coaching: The Journey from Beginner to Mastery and Beyond are titled Badass Role-Based Coaching and Context-Based Coaching. Written by Jennifer Fields, the chapters explore role-based and context-based coaching dynamics. The two chapters are intertwined; I view roles as a specialized type of context. Jennifer presents several scenarios in both chapters on how she would approach coaching events for different roles and contexts. Week 1: Badass Role-Based Coaching and Context-Based Coaching - http://bit.ly/3IjYEfU  A quick advertisement: Controlling work entry requires preparation, knowledge, and building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com   Next SPaMCAST In the next Software Process and Measurement Cast, we continue our journey into the use of flow metrics to plan work. Next week we will tackle something more complex. We will also return to the QA corner with the regular version of Mr. Barriault's column.  

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/)

In this episode, Richard interviews Jorgen Hesselberg, a co-founder of Comparative Agility and the author of Unlocking Agility: An Insiders’ Guide to Agile Enterprise Transformation. He tells us how luck is not necessarily a product of coincidence and how your team can truly become an architect of its own luck. Read the transcript of the episode at https://kasperowski.com/podcast-64-jorgen-hesselberg/

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/)

This week on the show, Dan Neumann is joined by Jorgen Hesselberg! Jorgen is the author of the new book, Unlocking Agility: An Insider’s Guide to Agile Enterprise Transformation, as well as the co-founder of Comparative Agility — a leading Agile assessment and continuous improvement program.   This episode will be focused on data-driven continuous improvement. Jorgen shares the main reasons to use data to drive continuous improvement, some of the main ways to gather data (and why these methods are used), and important pieces to keep in mind when implementing changes to your team and organization through the data you collect.   Jorgen has a lot to say about this topic as a co-founder of a leading Agile assessment and continuous improvement program so you definitely don’t want to miss his insights and key takeaways!   Key Takeaways Why use data for continuous improvement? Data can help guide you and your teams by asking better questions as well as shining a light where there otherwise would be darkness Helps you reflect on what you’re doing and what you can do better; data helps guide these conversations Optimizes workflow by making the feedback loop faster so you can take action more quickly and therefore see results faster As a change leader, data can help you find out where you can be of most use to help your teams What are some ways to gather data for continuous improvement? And why are these methods used? Objective data (defects in production, trends, etc.) Surveys, even though very subjective, can also be very useful because they can hit some important patterns of ways of working (i.e. psychological safety was discovered through a survey) and highlight other points that wouldn’t naturally come up in conversations because they create anonymity and give everyone an equal voice Structured interviews Gathering data — whether it’s through structured interviews, subjective data, or collecting data electronically — helps to shorten feedback loops What is important to keep in mind when using data for continuous improvement? Subjective, objective, and quantitative data are all great — as long as the data helps you and your team ask better questions, that is the main goal As a coach or change leader, it is important to ask meaningful questions that highlight the issues and challenges your teams are facing and to give them a voice Don’t implement changes all at once that you have gathered from the data because you and your teams will become overwhelmed and end up making no changes (i.e. because you are diluting the focus and creating confusion; people don’t have time to adjust too many different things at once) An important facet to making change based off data is to change at a rate where you can see it ripple through the organization Combine subjective data with objective data Measure technical debt simply by asking your developers Listen to data early on and refresh it periodically to stay ahead of the curve Don’t continually ask your developers how they’re doing — they’ll get annoyed! Understand what ‘normal’ benchmarks are for your niche Data isn’t going to give you answers but it is going to help you ask better questions Use data for information, not evaluation   Mentioned in this Episode: Jorgen Hesselberg Unlocking Agility: An Insider's Guide to Agile Enterprise Transformation, by Jorgen Hesselberg Comparative Agility The Agile Manifesto “Psychological Safety and Learning Behavior in Work Teams,” by Amy Edmonson Mood Marbles Daniel H. Pink Books Strava Agile Coaches’ Corner Ep. 58: “How to Get Past the Two-Week Shelf Life of Your New Year’s Resolution”   Jorgen Hesselberg’s Book Pick: Blueprint: The Evolutionary Origins of a Good Society, by Nicholas A. Christakis   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

This month I was lucky enough to sit down and talk with Jorgen Hesselberg, the Co Founder of Comparative Agility to talk about how to grow and sustain Continuous Improvement in your organisation. Why is this important Change is no longer optional 52% of Fortune 500 companies have disappeared because of digital disruption. If you want to survive in modern business, then adaption is a key skill to master. People and Culture drive your organisation Teams and knowledge work are becoming more autonomous. By empowering them with a culture of learning and managed risk taking you supercharge their ability to adapt to the market. Here is What You'll Learn The Need for a Change Culture Understand the shifts in team culture and the business landscape that requires the ability to navigate change at pace. The 6 Step Process For Continuous Improvement We lay out the exact process you can follow to create real change driven by data, people and leadership. The Pillars of Agile Transformation Understand the pillars and which ones are necessary for your Agile teams to operate at a high performance level. Psychological Safety Learn how to create the culture where people feel empowered to raise imperfections and turn them into improvements. --- Send in a voice message: https://podcasters.spotify.com/pod/show/comparativeagility/message

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/)

[Versione ITALIANA del Talk]Organizations place business agility as one of their top strategic priorities, yet there are multiple reasons enterprise transformations fail. How do you know you're on the right path? What are some of the concrete signs that your organization is becoming more agile? In this talk, Jorgen Hesselberg goes beyond the tools, frameworks, and hype to outline 7 concrete signs that show you're on your way to unlocking agility.Speaker:Jorgen Hesselberg

Organizations place business agility as one of their top strategic priorities, yet there are multiple reasons enterprise transformations fail. How do you know you're on the right path? What are some of the concrete signs that your organization is becoming more agile? In this talk, Jorgen Hesselberg goes beyond the tools, frameworks, and hype to outline 7 concrete signs that show you're on your way to unlocking agility.Speaker:Jorgen Hesselberg

SPaMCAST 557 features our interview with Jorgen Hesselberg.  We talked about his book Unlocking Agility,  assessing agility, and whether leadership and structure lead culture when adopting an agile mindset.  It is a thought-provoking and fun interview. Jorgen’s irrepressible nature shines through even when tackling tough topics!  Jorgens Bio: “Jorgen Hesselberg is the author of Unlocking Agility and co-founder of Comparative Agility, a leading agile assessment, and continuous improvement platform. A proven thought leader of numerous successful enterprise transformation efforts since 2009, Jorgen provides strategic guidance, executive counsel, and coaching to some of the world’s most respected companies both as an internal change agent and an external consultant. He has trained thousands of people on agile and Scrum, disruptive innovation, and enterprise transformation strategy.” Contact Information Email: jorgen@comparativeagility.com  LinkedIn: linkedin.com/in/jhesselberg  Comparative Agility:  https://www.comparativeagility.com/product/   Re-Read Saturday News Chapter 14 continues the discussion of cognitive biases and heuristics.  In Chapter 14 of Thinking, Fast and Slow we explore the representative heuristic.     Remember, if you do not have a favorite, dog-eared copy of Thinking, Fast and Slow, please buy a copy.  Using the links in this blog entry helps support the blog and its alter-ego, The Software Process and Measurement Cast. Buy a copy on Amazon,  It’s time to get reading!   The installments: Week 1: Logistics and Introduction – http://bit.ly/2UL4D6h Week 2: The Characters Of The Story – http://bit.ly/2PwItyX Week 3: Attention and Effort – http://bit.ly/2H45x5A Week 4: The Lazy Controller – http://bit.ly/2LE3MQQ Week 5: The Associative Machine – http://bit.ly/2JQgp8I Week 6: Cognitive Ease – http://bit.ly/2VTuqVu Week 7: Norms, Surprises, and Causes – http://bit.ly/2Molok2 Week 8: A Machine for Jumping to Conclusions - http://bit.ly/2XOjOcx  Week 9: How Judgement Happens and Answering An Easier Question - http://bit.ly/2XBPaX3  Week 10:  Law of Small Numbers - http://bit.ly/2JcjxtI  Week 11: Anchors - http://bit.ly/30iMgUu  Week 12: The Science of Availability - http://bit.ly/30tW6TN  Week 13: Availability, Emotion, and Risk - http://bit.ly/2GmOkTT  Week 14: Tom W’s Speciality - http://bit.ly/2YxKSA8    Next SPaMCAST SPaMCAST 558 will feature our essay Story Points – Leave Them, Don’t Love Them.  I use them when needed but I am becoming less enamored with story points every day.   We will also return to the QA Corner and spend some time with Jeremy Berriault.  

SPaMCAST 556 features our essay on Socratic Questioning.  Questions are a critical tool that every coach, mentor or leader uses to help shape and improve the performance of those they interact with — I don’t think this statement should surprise anyone.  That said, pushing past the concept of just asking questions, Socratic questioning is a formal and disciplined approach to getting the person answering the questions to synthesize and answer based on knowledge and logic. We also have a visit from Susan Parente.  Susan brings her Not A Scrumdamentalist column to the SPaMCAST. In this installment, Professor Parente discusses being agile in name only. Being agile in name only is not an enviable place to be! Re-Read Saturday News The availability heuristic, introduced in Chapter 12,  states that we make judgments about an attribute based on how easy or hard it is to retrieve information about the attribute. In Chapter 13, Kahneman dives deeper into how the availability heuristic functions, and provides some hints on how it can be used.  Remember, if you do not have a favorite, dog-eared copy of Thinking, Fast and Slow, please buy a copy.  Using the links in this blog entry helps support the blog and its alter-ego, The Software Process and Measurement Cast. Buy a copy on Amazon,  It’s time to get reading!    The installments: Week 1: Logistics and Introduction – http://bit.ly/2UL4D6h Week 2: The Characters Of The Story – http://bit.ly/2PwItyX Week 3: Attention and Effort – http://bit.ly/2H45x5A Week 4: The Lazy Controller – http://bit.ly/2LE3MQQ Week 5: The Associative Machine – http://bit.ly/2JQgp8I Week 6: Cognitive Ease – http://bit.ly/2VTuqVu Week 7: Norms, Surprises, and Causes – http://bit.ly/2Molok2 Week 8: A Machine for Jumping to Conclusions - http://bit.ly/2XOjOcx  Week 9: How Judgement Happens and Answering An Easier Question - http://bit.ly/2XBPaX3  Week 10:  Law of Small Numbers - http://bit.ly/2JcjxtI  Week 11: Anchors - http://bit.ly/30iMgUu  Week 12: The Science of Availability - http://bit.ly/30tW6TN  Week 13: Availability, Emotion, and Risk - http://bit.ly/2GmOkTT    Next SPaMCAST SPaMCAST 557 will feature my interview with Jorgen Hesselberg.  We talked about his book Unlocking Agility and assessing agility.  A thought-provoking and fun interview.  Jorgen’s irrepressible nature shines through even when tackling tough topics! 

We always talk about transformation, and "being agile"...but how does one go about accomplishing this seemingly impossible feat?  Join us as we sit down with Jorgen Hesselberg, the author of the book Unlocking Agility, to discuss the critical dimensions of agility, how to tie your strategy to metrics, and much more!   Jorgen's Twitter Jorgen's Website Unlocking Agility @ Amazon

Jorgen Hesselberg and Steven Wolff on Agile Amped, Melissa Perri on Agile Uprising, Eric Elliott on Simple Leadership, Liz Keogh on Being Human, and Alex Schladebeck on Test Talks. 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 March 4, 2019. These podcast episodes may have been released much earlier, but this was the week when I started sharing links to them to my social network followers. JORGEN HESSELBERG AND STEVEN WOLFF ON AGILE AMPED The Agile Amped podcast featured Jorgen Hesselberg and Steven Wolff with host Howard Sublett. I liked what Steven had to say about how new norms can come into being simply through inaction and how we want to be more intentional about creating norms. This comment reminded me of the discussion of norms in the book Influencer: The New Science of Leading Change by Grenny et al., a book I highly recommend. In my own work, I use working agreements with my team to intentionally develop team norms and hold each other accountable for them. iTunes link: https://itunes.apple.com/ca/podcast/change-the-norms-to-change-the-culture/id992128516?i=1000429382285&mt=2 Website link: https://solutionsiq.podbean.com/e/change-the-norms-to-change-the-culture/ MELISSA PERRI ON AGILE UPRISING The Agile Uprising podcast featured Melissa Perri with hosts Colleen Johnson, Troy Lightfoot, and Chris Murman. This episode caught my attention because I enjoyed Melissa’s last appearance on Agile Uprising which motivated me to pre-order her book The Build Trap back in November last year. I learned a lot from the book and it introduced me to the book The Art Of Action by Stephen Bungay, which I talked about in the last podcast episode. I liked Melissa’s description of product managers as bad idea terminators. I see this as more of a behavior during the convergent thinking phase of product design. Lack of focus is definitely a problem I see on product teams, so I can appreciate the idea of having someone to keep people focused on the most valuable problems to solve. iTunes link: https://itunes.apple.com/ca/podcast/escaping-the-build-trap-w-melissa-perri/id1163230424?i=1000429120613&mt=2 Website link: https://agileuprising.libsyn.com/podcast/escaping-the-build-trap-w-melissa-perri ERIC ELLIOTT ON SIMPLE LEADERSHIP The Simple Leadership podcast featured Eric Elliott with host Christian McCarrick. I appreciated Eric’s comment about the myth of the individual contributor engineer because I have seen developers being judged on simple, easy-to-measure metrics like closed ticket counts when a more appropriate metric would be one that takes into account their time spent mentoring and the benefits that such mentoring had on the team. Over the long term, I have seen the damage that judging engineers by closed ticket count does to a culture where everybody is incentivized to work in their individual silo and almost no mentoring takes place even from senior engineers for whom mentoring and coaching should be, in my opinion, a large part of their day. iTunes link: https://itunes.apple.com/ca/podcast/how-culture-can-help-your-teams-scale-with-eric-elliott/id1260241682?i=1000429163879&mt=2 Website link: http://simpleleadership.io/how-culture-can-help-you-scale-with-eric-elliott/ LIZ KEOGH ON BEING HUMAN The Being Human podcast featured Liz Keogh with host Richard Atherton. Liz talked about the Cynefin framework, psychological safety, and real options. I particularly liked her story of a team that invested in making changes easily reversible by creating a rollback mechanism for when a production release goes awry. She remarked on how this technical safety net provided psychological safety as well. I also liked her description of real options, which I have recently been reading about in the book Commitment by Olav Maassen, Chris Matts, and Chris Geary. Liz told a story about how conference organizers gave themselves options by over-ordering on the engraved trophies. The very affecting second half of this podcast episode was focused on the #metoo movement. Liz shared her experiences of being harassed and Richard confessed to his own poor behavior. iTunes link: https://itunes.apple.com/ca/podcast/47-1-complexity-2-exploring-metoo-with-liz-keogh/id1369745673?i=1000429964823&mt=2 Website link: http://shoutengine.com/BeingHuman/47-1-complexity-2-exploring-metoo-with-liz-keogh-73971 ALEX SCHLADEBECK ON TEST TALKS The Test Talks podcast featuring Alex Schladebeck with host Joe Colantonio. The title of the episode, “How to Listen to Your Tests”, immediately caught my attention since I have been encouraging co-workers to develop this skill ever since I read Growing Object-Oriented Software Guided By Tests by Steve Freeman and Nat Pryce, even going so far as to create a 10-minute YouTube video tutorial on how to Listen To The Tests last April. Joe and Alex talked about how she applies her training in linguistics in her career in software testing. It turns out that such training was actually helpful as it taught her how to move back and forth between detailed and abstract ways of thinking. They got into a discussion of test data management, which Alex likened to continuous integration because it is something that starts out being painful when you don’t address it often enough or when you push it onto the testers and it becomes easier the more often you pay attention to it and when you make it everyone’s responsibility. I also liked Alex’s story of a pelican encounter on an early-morning run coming to represent to her the unknown unknowns that exploratory testing helps you discover. iTunes link: https://itunes.apple.com/ca/podcast/240-how-to-listen-to-your-tests-with-alex-schladebeck/id826722706?i=1000429560907&mt=2 Website link: https://www.joecolantonio.com/testtalks/240-alex-schladebeck/ FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/channel/UCysPayr8nXwJJ8-hqnzMFjw Website:

“Agile is not something you become, Agile is something you become more of.” For organizations that are engaged in Agile Transformation, it is often very challenging to get a sense of where you are with respect to successfully adopting a new way of working. Comparative Agility is a tool that has been designed to help Agile coaches and organizations get a deeper understanding of their progress towards Agile transformation. In this interview, Jorgen Hesselberg, co-founder of Comparative Agility, and I discuss how the tool has evolved since it was created in 2008 and how it is now being used by coaches and organizations to not only understand how their transformation is going, but how they are doing compared to others within their vertical, as well. We also talk about the work that Comparative Agility has been doing with the Scrum Alliance and how the tool has been extended to include things like Security and DevOps, in addition to discussing Jorgen’s book “Unlocking Agility.” If you’d like to check out Comparative Agility, you can find it here: https://www.comparativeagility.com If you’d like to read “Unlocking Agility”, you can find it here: https://amzn.to/2setHly Contacting Jorgen Email: jorgen@comparativeagility.com Twitter: https://twitter.com/jhesselberg

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/)

If you've been around Chicago long enough, at least in the Agile community, you would know that the company currently know as HERE (formerly Navteq and then Nokia) has a great reputation for being an Agile company.  The truth is, the Agile movement there started as an experiment - as most things in Agile should. I tag along while Allen Rutzen and Jorgen Hesselberg describe the best example of a true Agile Transformation.