Podcast appearances and mentions of henrik kniberg

Henrik Kniberg shares insights from his recent video and book 'Generative AI in a Nutshell,' which went viral. The discussion explores how AI can reduce the need for large teams, allowing for more efficient, smaller teams. Henrik explains his current project on building an AI agent platform and its implications for the future of work. We also delve into the evolving role of product discovery and how AI is transforming traditional agile practices. The conversation wraps up with thoughts on how to stay ahead in the rapidly evolving tech landscape and what elements of traditional work practices, like time sheets, might be rendered obsolete by new AI capabilities.00:00 Introduction 01:20 Guest Introduction: Henrik Kniberg02:46 Henrik's Current Projects and AI Insights03:57 The Evolution of Agile Teams05:57 Impact of AI on Work and Society07:21 Writing and Promoting the Book11:16 Future of Work with AI23:01 Designing for AI Stakeholders26:35 Building and Managing AI Agents27:40 Real-World Applications of AI Agents31:58 The Future of Product Development33:50 Effective Product Discovery38:28 Integrating AI in Product Development40:20 Learning and Staying Ahead in AI43:54 The Importance of Eliminating Time Sheets46:45 Conclusion and Final Thoughts⚡️ In each episode, Paddy Dhanda deep dives into a new human Superpower to help you thrive in the age of AI.Host: Paddy DhandaPaddy works at the largest Tech training organisation in the UK and is passionate about helping tech professionals build human skills to thrive in the age of AI.Contact Paddy: paddy@superpowers.schoolSubscribe to my newsletter:

No guests today! Instead, I'll be taking questions from the Building Better Games discord and answering them. I cover10 questions including the challenges with AAA dev, the rise of co-dev, and what production careers look like. Enjoy! Question #1 : How do you ensure that you (the royal you) are making a game that will be fun for players, not just fun for its designers to make? (Or maybe in this context - what are the ways in which production can support product management and ensure the sprint-to-sprint goals align with what internal player advocates are asking for?) Question #2 : What would you say needs to happen to make the big players more competitive / successful again? Question #3: Do you think there's an observable trend towards an increased amount of codevelopment as a way to mitigate costs/risk? What issues do you see this posing for coherent design and production if there is an increasing reliance on external development partners?   Question #4: There are clear signs when certain aspects of a game are lacking - incoherent design, low quality assets, buggy software. What are the player-facing symptoms of a game that is lacking in production or leadership competencies?    Question #5: Production organizations at larger game studios often suffer from issues of structure, such as a substantial number of producers, senior producers, and even lead producers all rolling directly up into an overburdened production director, because there doesn't seem to be an understood space for a “producer manager” between frontline production and executive/director-level production leadership. What is the rationale for this gap when manager is a well-understood conceit in other gamedev disciplines (e.g. designers will have design managers reporting to a design director, artists will have department managers reporting to a director, engineers have managers between them and directors, etc.)?  Is it just that production is typically not a large enough organization to merit managers? That producers are seen as organized and not in need of more traditional personnel management? Question #6: How can you become better at your role as a producer when you aren't at your job? Or in other words, how can you get better at what you do aside from getting more experience?   Question #7: For mid- and senior level producers: What does a career development track look like? Often it seems like the only future for a highly competent producer is executive producer (a stretch for many and not a realistic path for most) or production director, which itself is a rarified commodity at larger developers. What are the progression opportunities an IC producer should be considering? Question #8: As the only Production guy on my team (and 1 of 3 "operations people"), how would you deal with getting questions and answers when you have nobody around to rubber ducky with?   Question #9: When talking about the past, how can you learn to abstract experiences and look past the specifics? Are there any resources you recommend for learning how to tell stories so that you're not bogged down in the details of history?   Question #10: How are game developers selecting and setting up test groups to see their players are enjoying the game and it's a good market fit? Are there aspects of this process that could see refining and improving? Or common pitfalls other developers tend to see in this process? LinkedIn for Steve Bromley (https://www.linkedin.com/in/stevebromley/) and Graham McAllister (https://www.linkedin.com/in/grahammcallister/) Steve Bromley's Book: https://gamesuserresearch.com/book/ Graham McAllister URL: https://grahammcallister.com/ Steve Bromley URL: https://gamesuserresearch.com/ Agile Game Development: Build, Play, Repeat by Clinton Keith: https://www.amazon.com/Agile-Game-Development-Addison-Wesley-Signature-dp-0136527817/dp/0136527817/ Lean from the Trenches by Henrik Kniberg: https://www.amazon.com/Lean-Trenches-Managing-Large-Scale-Projects/dp/1934356859/ Creativity, Inc. by Ed Catmull and Amy Wallace: https://www.amazon.com/Creativity-Inc-Expanded-Overcoming-Inspiration/dp/0593594649/ Turn the Ship Around by L. David Marquet: https://www.amazon.com/Turn-Ship-Around-Building-Breaking/dp/0241250943 Our discord community is live! Join here to engage with leaders and producers in game dev looking to make our industry a better place that makes better games: https://discord.gg/ySCPS5aMcQ   If you're interested in an online course on becoming a better game producer, head here: https://www.buildingbettergames.gg/succeeding-in-game-production   Subscribe to our newsletter for more game development tips and resources: https://www.buildingbettergames.gg/newsletter   Ben's LinkedIn: https://www.linkedin.com/in/benjamin-carcich/ YouTube Channel: https://www.youtube.com/@buildingbettergames Spotify Podcast: https://open.spotify.com/show/6QD5yIbFdJXvccO8Z5aXpm   Help us create more amazing content! Join us on Patreon today: https://www.patreon.com/BBGOfficial  

Vi har med Henrik Kniberg som har utvecklats sig från en Agil guru till en AI guru. Vi pratar om AIs framfart och framförallt generativ AI. Vi pratar lite teoretiskt hur det funkar men pratar mest om hur det kan appliceras och hur lång tid det tar innan det på riktigt förändrar våra liv. Försökte skapa denna sammanfattning med ChatGPT 4 men den låg nere ikväll så ni läser text skriven av en människa, inte länge till… Tack till www.crisp.se för att ni gör podden möjlig!  

This episode was recorded during a recent Visual Jam Meetup event with special guest Henrik Kniberg. We delve deep into the fusion of creativity, technology, and visual storytelling. Here are the key takeaways from the event:* The Journey from Music to Technology: Kniberg's transition from an aspiring musician in Tokyo to a tech enthusiast and influential content creator.* Spotify, Lego and working on Minecraft: How Kniberg helped household brands increase their agility.* Generative AI as a Catalyst for Innovation: How we can leverage generative AI in product development.* The Imperative of Human Skills: The importance of human skills in an AI world.* Visual thinking process to go viral: Step-by-step process of Kniberg's YouTube videos that have gone viral.My superpower is the ability to take complicated things and explain them in a simple way - Henrik Kniberg00:00 Welcome and Introduction to Henrik Kniberg00:54 Discovering Henrik's Superpower and Background01:16 Henrik's Journey: From Tokyo to Tech Innovator03:20 Exploring Henrik's Career: Spotify, Lego, and Minecraft11:34 The Future of Tech and AI: Henrik's Insights13:48 Visual Storytelling: The Power of Simplification21:28 Decoding the Video Creation Process21:49 The Power of PowerPoint in Planning22:49 Crafting the Script: Every Word Counts23:50 Visuals and Drawing: Bringing Ideas to Life25:04 Editing and Final Touches: The Painstaking Process26:41 Tools of the Trade: ScreenFlow and ArtRage28:59 The Viral Video Formula: Content, Drawing, and Human Appeal31:42 Interactive Q&A: Insights and Tools Revealed36:55 Embracing AI: Enhancing Creativity and Efficiency40:15 Closing Thoughts and Audience EngagementHenrik KnibergHenrik Kniberg is Chief Scientist and cofounder of Hups.com and Flitig.ai, and consultant at Crisp. Henrik's focus is the practical application of Generative AI in product development and other areas. He explores the frontiers of this technology, builds AI-powered products, and teaches courses and workshops on how to use this technology effectively. He made the video ”Generative AI in a Nutshell” and wrote the articles ”Are developers needed in the Age of AI” and ”WhoDunit – Ai product development on steroids”.Henrik's background is Minecraft gameplay design & development at Mojang, and agile/lean coaching at LEGO and Spotify and other product companies.Henrik is well-known for his books ”Scrum and XP from the Trenches” and ”Kanban and Scrum, making the most of both” and ”Lean from the Trenches”. He is also well-known for viral videos such as ”Agile Product Ownership in a Nutshell” and ”Spotify Engineering Culture” (commonly referred to as the Spotify Model), and silly metaphors like the skateboard metaphor for product development, and ping pong balls to demonstrate the concept of flow. Henrik has also been engaged in climate change – he created the video Friendly Guide to Climate Change and cofounded GoClimate.com.⚡️ In each episode, Paddy Dhanda deep dives into a new human Superpower to help you thrive in the age of AI.

Join Brian and David Bland as they journey into the novel idea of testing assumptions before development to avoid costly mistakes and ensure the right things are being built in the latest episode of the Agile Mentors Podcast—a must-listen for any product owner wanting to determine if their team is working on the right thing. Overview In this episode of the Agile Mentors Podcast, Brian talks all things testing with David Bland, the founder of Precoil and co-author of the book Testing Business Ideas: A Field Guide for Rapid Experimentation. Learn the importance of testing assumptions and experimentation in product development as David shares his journey from working in startups to coaching and consulting and how he realized the need to bring Agile principles into the discovery phase of product development. You can listen in as they explore the concept of testing business ideas and the three-step process of extracting assumptions, prioritizing them, and running experiments. Listen Now to Discover: [01:01] - Brian introduces David Bland, founder of Precoil and co-author of Testing Business Ideas: A Field Guide for Rapid Experimentation. [02:10] - David dives into weaving testing assumptions and experimentation into managing the product backlog for product owners. [02:51] - David discusses how you can determine if you're working on the right things and prevent iteratively delivering something that nobody cares about by applying the Agile principles further upstream. [04:20] - Brain adds insight with the notion of being selective as the product owner, referencing the work of Henrik Kniberg. [05:18] - David breaks down the themes he developed from design thinking and how they apply beautifully to the product backlog: desirable, viable, & feasible [06:50] - Brian asks the question burning through many of our minds, “How do you apply it to testing your ideas?” [07:15] - David lays out the three-step process he uses and applies to testing business, product, and service ideas. [08:32] - David discusses the difference between requirements and assumptions. [10:33] - David provides a practical example of adding wishlist functionality to a website and what testing this idea would look like under his testing framework. [14:47] - Today's episode of the Agile Mentors Podcast is brought to you by Mountain Goat Software's Private Training for Agile transformations. Get your team on the same page through customized training and coaching programs to level-set your team. For more information, visit the Mountain Goat Software’s Private Training page. [16:07] - Brian poses the concept of asking, “How does an idea move the needle” before the idea is developed? [18:14] - David shares his thoughts on running customer-facing acceptance criteria and the product death cycle, a term David coined. [21:06] - David provides an example of a client who puts a positive spin on killing projects that prove not to be viable via testing. [22:33] - Brian asks if there are testing methods that can be applied after a product launch as a lagging indicator of the launch. [24:57] - Brian clarifies the value of testing before making a bet on a new product, even as an entrepreneur working alone, through the example of knowing how a bet will play out in a Las Vegas casino. [25:38] - David lays out the common objections he sees from companies and how you could address them. [27:13] - David lays out one of his favorite techniques for testing, concierge, which he lays out in detail in his book. [30:41] - Brian draws the conversation back to the Agile Manifesto. [31:49] - Brian shares a big thank you to David for joining him on the show. [33:30] - We invite you to subscribe to the Agile Mentors Podcast on Apple Podcasts. Do you have feedback or a great idea for an episode of the show? Great! Just send us an email. References and resources mentioned in the show: David Bland Precoil Testing Business Ideas: A Field Guide for Rapid Experimentation by David Bland & Alexander Osterwalder #25 Scaling with Henrik Kniberg Agile Manifesto Subscribe to the Agile Mentors Podcast on Apple Podcasts Mountain Goat Software’s Private Training Mountain Goat Software Certified Scrum and Agile Training Schedule Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. David J Bland helps companies such as GE, Toyota, Adobe, HP, and Behr find product market fit using lean startup, design thinking, and business model innovation through his company, Precoil. He is the lead author of Testing Business Ideas with Alexander Osterwalder.

Känner du dig också osäker och orolig inför AI? Du är inte den ensam! I veckans avsnitt gästas jag av AI-experten Nils Janse, vi utforskar AI:s roll för HR och HR:s roll för AI.  Varför halkar Sverige efter i denna utveckling? Vilka konsekvenser kan det få för näringslivet och Sverige i stort? Vi diskuterar skillnaderna mellan generativ och prediktiv AI, betydelsen av att skapa effektiva prompts, samt hur man formulerar krav på HR-system och produkter som integrerar AI.  Vi lyfter också skillnaden mellan de olika plattformarna (Bing, Bard, Co-pilot mfl) och belyser möjligheter och risker. Målet är att hjälpa dig inom HR att navigera i AI världen på ett etiskt och tryggt sätt. Avsnittet presenteras i stolt samarbete med Hailey HR som är ett svenskt HR system. Missa inte att agilaHRpodden finns på de sociala plattformarna och på FolkEtt.se Signa gärna upp på mitt nyhetsbrev för att ta del av spaningar och tankar om framtidens arbetsliv, Agil HR, forskning, aktuella händelser och erbjudanden. Tack snälla för att du lyssnar! Generativ AI i Ett nötskal- Youtube beskrivning av Henrik Kniberg

Ever wondered how visuals can transform your role as a product owner? Join Brian as he sits down with visual storyteller Stuart Young to unravel the power of visualization in product ownership. Join them on a journey to discover the art and science behind being a successful product owner. Overview Ever wondered how to elevate your product ownership game? In this episode, we delve into the world of visual storytelling with Stuart Young. Join Brian and Stuart as they discuss the diverse tools, such as story mapping and the product disposition canvas, that can bring your product visions to life. From storytelling techniques to the neurodiversity lens, we explore the art and science of communication that transcends traditional boundaries. Listen in to uncover the impactful ways visuals can shape your product strategy. Learn how being more visual can sharpen your skills, foster collaboration, and create a more inclusive and successful product development journey. Listen Now to Discover: [00:23] - Today welcomes Stuart Young, a Certified Scrum Trainer and visual storyteller to discuss storytelling through the product lens and more. [03:32] - Stuart discusses drawing large-scale pictures at conferences and recommends Visual Meetings and Visual Leaders by David Sibbit. [06:54] - Stuart emphasizes the impact of visual storytelling on individuals, highlighting the universal language and information retention through visuals. [08:46] - The benefits of visual representation in capturing the flow of ideas and aiding memory. [10:26] - The importance of varied methods for engaging different learning styles. [11:41] - Stuart discusses the value of visualization tools such as roadmaps, post-it notes, and story mapping to provide clarity and a clear narrative. [12:14] - The importance of blending Stuart references Pixar and Ed Catmull's book Creativity, Inc., discussing the importance of blending exciting elements, like storyboarding, in motivating teams and creating a compelling narrative. [15:13] - Stuart emphasizes the importance of authentic storytelling, even if it doesn't always have a happy ending, he references TEDxHogeschoolUtrecht - Steve Denning - “Leadership Storytelling" for further inspiration. [15:25] - Brian recommends Simon Sinek's TED talk on "Start With Why" as an example of effective storytelling despite not being visually polished. [16:09] - Stuart praises Henrik Kniberg's impactful video on product ownership, acknowledging the simplicity of the drawings but highlighting the potency of storytelling. He recommends the Sketchnote Handbook by Mike Rhodes for those interested in delving further into storytelling. [17:08] - The Agile Mentors Podcast is brought to you by Mountain Goat Software and their Certified Scrum Training Classes. For more information, click on the Mountain Goat Software Certified Scrum and Agile Training Schedule. [18:38] - Stuart highlights the significance of visual elements in crafting compelling visions and underscores the value of utilizing available templates, from sources like the Gamestorming book. [20:06] - Stuart discusses the role of visualization in making the intangible tangible, particularly in the tech space. [21:50] - Brian emphasizes the imprecision of words. He also discusses the value of showing rather than just telling, especially in product requirements, to enhance understanding and avoid delays caused by miscommunications. [23:34] - Stuart reflects on how visual communication can enhance inclusivity. He shares, “For people with reading and writing difficulties, pictures and symbols are better. The worst, the most abstract form, of course, is the word.” [25:22] - The role of a visual storyteller as a "human cursor" connecting diverse conceptual thinkers. Stuart recounts an illustration experience, emphasizing the challenge of visualizing details without clear specifications and underscoring the mantra of "process over art" in product ownership. [28:06] - Stuart underscores the product owner's role in leveraging the unique skills of team members to converge on a shared understanding of what "good" looks like. [29:19] - Brian references the episode of the show they did on Navigating Neurodiversity and the importance of understanding and accommodating different communication styles within a team. He highlights the need for product owners to be aware of the preferences of their team members and adjust communication methods accordingly. [30:54] - Stuart introduces the product disposition canvas and shares a personal revelation. [32:54] - Brian acknowledges the potential superpowers that come with neurodiversity, sharing his own experience of a late-in-life ADHD diagnosis and the benefits of leveraging the unique qualities each team member brings to a team. [33:36] - Stuart reflects on the importance of recognizing individual strengths and blind spots, emphasizing that everyone has a valuable contribution. [34:20] - Stuart encourages recognizing individual strengths for collective success. [35:23] - Listeners can connect with Stuart on LinkedIn and at Agile Nuggets | Agile Tips [37:38] - Please share this episode with others if you found it useful. Send feedback and suggestions for future episodes to podcast@mountaingoatsoftware.com. And don’t forget to subscribe to the Agile Mentors Podcast on Apple Podcasts so you never miss an episode. [38:21] - If this topic was impactful to you and you want to continue the discussion, join the Agile Mentors Community where we have a topic discussion for each podcast episode. You can get a free year-long membership in the community just by taking any class with Mountain Goat Software. References and resources mentioned in the show: Stuart Young on LinkedIn Agile Nuggets | Agile Tips | Cprime Learning Scrum in Under 10 Minutes #76: Navigating Neurodiversity for High-Performing Teams with Susan Fitzell David Sibbet Visual Meetings by David Sibbet Visual Leaders by David Sibbet Creativity, Inc. Sketchnote Handbook by Mike Rohde TEDxHogeschoolUtrecht - Steve Denning - “Leadership Storytelling" Simon Sinek: How Great Leaders Inspire Action | TED Talk Agile Product Ownership in a Nutshell by Henrik Kniberg Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers Subscribe to the Agile Mentors Podcast on Apple Podcasts Certified ScrumMaster Training and Scrum Certification Certified Scrum Product Owner Training Advanced Certified Scrum Product Owner® Advanced Certified ScrumMaster® Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Stuart Young, a Certified Scrum Trainer and Visual Storyteller, merges Agile methodologies and design thinking to empower individuals and teams. As a thought leader, he champions Visual Storytelling for engaging stakeholders, addressing customer needs, and expediting learning. Through workshops, Stuart encourages teams to embrace visual methodologies to achieve business success.

Join Brian as he rediscovers and relives the most captivating topics, memorable guests, and impactful topics from the first year of the “Agile Mentors” podcast. Overview From deep dives into Agile methodologies and practical tips for using your knowledge to benefit others and foster change, the first 50 episodes of the “Agile Mentor” podcast have been filled with fascinating topics and memorable guests. In this episode, Brian Milner embarks on a retrospective journey through the inaugural year of the show. Listen in as he shares the real stars of the podcast, the moments that surprised him, those that took him out of his comfort zone, and the ones that inspired him to push to be better every day! Plus, what’s next for the show. Listen Now to Discover: [00:45] - Brian introduces the retrospective episode to celebrate one year and 50 episodes of the "Agile Mentors" podcast and share what's next. [01:54] - A thank you for YOUR role in the show. [02:17] - The role of marrying the right topic to the right guest. [02:56] - The format that allows listeners to choose the episodes that interest them the most. [04:03] - Pointing you toward the best of the best. Our first several episodes were focused on the Agile Framework and some core topics, including having Mike Cohn on to talk about the different roles and generally accepted practices. [05:13] - Sending out thanks to a few of our guests, including the trainers at Mountain Goat Software, including Lance Dacy. [05:45] - Kert Peterson joined us to share his knowledge, and Scott Dunn shared his insight from the product owner's perspective. [06:05] - On episode 16, Mitch Lacey joined us to discuss The Hidden Secret Ingredient And Julie Chickering brought a great perspective from a project management background and applying that to some of the stuff we've discussed here on the show. [06:39] - The time when one of my mentors joined us on the show to discuss transformation. [07:08] - Learning about coaching and marketing from the best! [07:27] - Roman Pitchler joined us to discuss product roadmaps and planning things from a product owner perspective. And John Miller shared about using Scrum in the education environment. [07:46] - On EP25, Henrik Nieberg came on and talked to us about scaling, and on EP27, Tricia Broderick walked us through leadership without blame. [08:18] - How Scrum can be applied outside of software development and mob programming. [08:42] - The key to working with humans. [09:03] - The episode that surprised Brian a little bit. [09:34] - Three episodes all about change: The first one was about how one organization uses Scrum to help impoverished micro-entrepreneurs succeed (and change their lives). The second featured Chris Li sharing his insight on how to know when it’s time to strike out on your own, and Karim Harbott walked us through the difficulty of transforming an organization's culture. [10:25] - The episode that inspired Brian to try to push in different ways to get better. And how to cultivate an Agile culture in a virtual world. [10:53] - Why transformations take people, how to assess a company’s culture before you accept their job offer, and lean thinking in Agile with Bob Payne. [11:49] - The real stars of the podcast. [12:30] - What’s ahead for the podcast? [13:02] - Stepping off the gas a bit. [13:45] - Virtual dial—targeted tips. [14:32] - The lifeblood of the “Agile Mentors” podcast. [15:06] - Mike Cohn and Brian are both presenting at Agile2023 in Orlando, July 24 through 28th. [15:39] - The most significant benefit of BIG conferences. [16:41] - Thank you for getting us to a year and 50 episodes! Join the Agile Mentors Community to continue the discussion. If you have topics for future episodes, email us by clicking here. And don’t forget to subscribe to the “Agile Mentors” Podcast on Apple Podcasts so you never miss an episode. References and resources mentioned in the show: Agile2023 | Orlando, Florida | Agile Alliance #1: Scrum vs Agile & Keys to Success with Mike Cohn #3: What Makes a Great Product Owner? With Lance Dacy #9: Scrum Artifacts with Kert Peterson #10: Why User Stories are the Best Way to Capture Requirements with Mike Cohn #17: Getting There From Here: Agile Transformations with David Hawks #18 Coaching in an Agile World with Lyssa Adkins #21: Agile Marketing Teams with Stacey Ackerman #22: How to Create Helpful Product Roadmaps with Roman Pichler #23 How Agile Works in Education with John Miller #25: Scaling with Henrik Kniberg #27: Leading Without Blame with Tricia Broderick #29: Influencing Up with Scott Dunn #32: Scrum in High School Sports with Cort Sharp #33 Mob Programming with Woody Zuill #34: I'm Trained, Now What? with Julie Chickering #37: Servant Leadership, Not Spineless Leadership with Brad Swanson #38: Using Agile for Social and Societal Transformation with Kubair Shirazee #40: Is it Time to Go Out on Your Own? Tips and Insights with Chris Li #41: Cultural Transformation in Organizations with Karim Harbott #42: The Importance of Self-Mastery with Bob Galen #43: Cultivating Agile Team Culture in a Virtual World with Richard Cheng #44: Transformations Take People with Anu Smalley #46: How to Assess Company Culture Before Accepting a Job Offer with Christina Ambers #47: Exploring Lean Thinking in Agile Development with Bob Payne Mountain Good Software's Certified Product Owner course Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.

Fredrik snackar med Lars Albertsson om data engineering - att hitta och agera på möjligheter i sin data, att förändra processer och arbetssätt, och vara med på att man kanske behöver ändra mycket fler saker för att få full effekt av en förändring. Lars går på djupet både i nyttan av att använda sin data på bra sätt, och i varför det är så svårt och så många projekt inte ger värst stor utdelning. Tidningars förhållningssätt är värdefullt i sammanhanget - gör något som är nyttigt för någon nu. Få ut värde tidigt. Gör inte som Lego. Drivs av use case. Följ värdeströmmarna och organisera längs med dem istället för att hamna på tvären och dämma upp dem. Lars tar också upp hur man sprider tillgången på data på ett bra sätt, och inte minst vikten av att ta ansvar för sin data och hur man hanterar den. Alla sätt att sprida data är definitivt inte bra. Ett stort tack till Cloudnet som sponsrar vår VPS! Har du kommentarer, frågor eller tips? Vi är @kodsnack, @tobiashieta, @oferlund, och @bjoreman på Twitter, har en sida på Facebook och epostas på info@kodsnack.se om du vill skriva längre. Vi läser allt som skickas. Gillar du Kodsnack får du hemskt gärna recensera oss i iTunes! Du kan också stödja podden genom att ge oss en kaffe (eller två!) på Ko-fi, eller handla något i vår butik. Länkar Lars Albertsson och hans företag Scling Øredev Lars presentationer på Øredev 2022 The 7 habits of data effective companies (pdf av presentationsbilder) Data engineering in 10 years (pdf av presentationsbilder) Lars andra presentationer och framträdanden Data engineering Data divide Eli Goldratt The goal Beyond the goal - introducerar teorin om begränsningar och de fyra frågorna Bra presentation av Dan North där han dyker ned i Goldratts fyra frågor Material resource planning Vattenfall Rational unified process Hadoop Data lake GDPR Rabobank - holländsk bank öppna med sitt arbete Bonnier news Peter Frey Joel Abrahamsson Henrik Kniberg Mojang Lego universe Henrik Kniberg om Lego vs Minecraft Palantir Peter Thiel Silicon Valley Blackwater Lean manufacturing Dataops och boktips Data swamp Data contracts Data products Extreme programming Accelerate - bok State of devops report Bonusboktips: Fundamentals of data engineering Titlar Titta på folk och prata med dem samtidigt Vad man gör med den data man har Förmågan att få ut värde av sin data Informationen finns därute Gapet i förmåga Ett optimeringsproblem Goldratts glasögon Man häller ner all sin data på ett och samma ställe och sedan så händer det bra saker Konsultbolag har ingen data Nej är det snabba svaret Något som är värdefullt för någon nu Ta sig data över huvudet Tvärs emot värdeströmmen

Transcript: Joe Krebs 0:20 Today I'm here with Staffan Noeteberg, who is the author of two books that is mono tasking that was released in 2020. And a little bit earlier, Pomodoro technique illustrated, I believe it was in 2011 that was forwarded by the one of the creators of the Pomodoro Technique, Francesco Cirillo and Henrik Kniberg. So what we have here with Staffan is a person that is very well connected with the Agile community as well as it is super interesting topic of mono tasking, what we want to talk about today, he's an Agile coach. He lives in Stockholm, Sweden, as well as in Istanbul, Turkey. If I'm informed here correctly, he has trained 1000s of people on improving their personal productivity. He has sold over 700,000 copies of his book. I'm super thrilled to have you on the podcast. Thank you for being here.Staffan Nöteberg 1:22 Thank you for having me. Joe Krebs 1:23 Yeah, this is this is awesome. We want to talk today really about mono tasking, that is that is obviously your latest book. And we want to connect a few dots because this could be super interesting for everybody listening to this podcast today from two angles. One of them is individually improving productivity as a as a person you know, in everyday life situations as well as professionally at work. But also how we can connect mono tasking maybe to agile teams and agile roles, maybe we can touch on that as well. So I think these are the two angles we want to explore here a little bit today. Mono as part of that title, if I go back in times and I'm like just thinking about audio mono was something that I would now relate with something negative right mono is like it's simple and and everything we're like all thinking about stereo at this point Dolby Stereo. Using mono in terms of tasking is something for the future. What is mono tasking, Staffan? Joe Krebs 2:30 It is interested that you mentioned that mono mono is something negative, because I think that the in job ads maybe 10 years ago, 20 years ago, there were often the demand for people that were they were looking for property property that said you you can juggle many balls at the same time, that's where our, that's what we're looking for. And nowadays, maybe they say you should be able to finish something to complete something. And that's and in order to do that maybe you shouldn't stop so many things and all these Kanban things that has been popular now for 20 years in software industry is very much about this stop starting and start finishing. So weekly meats and things like that, but I mean the mono tasking method then came out I wrote this Pomodoro technique book which is a personal productivity method. It's a particular concern about focusing on focusing. So, how do you really focus but I wanted to see this broader and I read many many personal productivity books and I think most of them almost everyone or almost none of them consider complexity and cohesion. I will explain what I mean by cohesion they like these books are often create order these books this these methods these processes are often made by engineers people like like you and me programmers or software engineers and the idea in them is often to like keep a list or multiple lists of in like in shipshape and Bristol fashion, you say ship ship in Bristol fashion in the US, or is that a British idiom?Joe Krebs 3:36 Which one is that?Staffan Nöteberg 4:28 Ship shape and Bristol fashion is one of my favorite idioms. We are doing everything under control and everything. We need to add the unit at the link in the show notes. Joe Krebs 4:51 We will definitely be in the data link for that. Yes.Staffan Nöteberg 4:53 Yeah. So so the idea of most personal productivity method is to have a lot of lists and they should be be perfect all the time. And they should contain a lot of ideas, everything that you you plan to do and why you're doing it. And so, and then there's the processes are often kind of, if else logic. So, if this happened to that, if that happened if this, but they are, I mean, that may work for you and me and other engineers, but for most people, it demands too much discipline. And it doesn't really accept that there are humans that are willing to use these methods, I wanted to create something that is more creative and more suitable for humans. So it's not like you're a silo, and you are fed from the top with the new tasks, and you work on them, and you complete them and just throw them out. Because there is some cohesion, you have your co-workers and, your teammates, and you have your stakeholders, your your product managers, you have your customers, and all these people, they change the mind, sometimes sometimes they say they want something. But they changed, they changed the mind, or they didn't explain it in a way that you understood, really started to do something else. So it's not really only about taking it as completing it. And doing that as fast as possible. And with the highest quality. It's more like you're putting in a big ecosystem. And you need to manage within that ecosystem. And I think that in that way, if you think of personal productivity in that way, it can be hard to have, like saying that you should do exactly like this, and exact like that maybe we should think more in arranging your environment and your circumstances, to have the best the best possibilities to succeed. So I started to read a lot of books and papers about what science says about human cognition, and evolutionary psychology and so on, I tried to create a method, which is little bit different from other methods that like embraces the human intuition and the human cognition and human heuristics, so that you don't have to maintain your there, you don't have to maintain all this list and doing all this documentation, and instead can use your intuition and in most cases, do the correct choices anyway, because we as humans are very good in this complexity, if we use our intuition to see what is most important than what what is not most important.Joe Krebs 7:52 Right? So it's interesting, right? So first and foremost, I'm thrilled to hear that I'm not the only one who experiences stakeholders changing their minds on things. So I'm kidding. Obviously, I think this is a, this is a huge problem in our, in our, you know, work in general, I think that's typical. But it's also fascinating what I've heard, I don't know if you would second that is that humans are pretty much incapable of multitasking. Right? So it's some basic things we can do. We can walk and talk at the same time, or I don't think that's going to cause a conflict. But we cannot work on two different kinds of systems at the same time, that causes a conflict, obviously. And that's where we're transitioning. So you're saying already with mono tasking, you're saying like, work with a reduced list of task, right? I believe you were mentioning something about like five shortlist or something like that, or like five items, or five tasks or something. And why is that? Why is why is the list? Short? We're not saying we're working on five items at the same time, right? We're just saying there's a list of five items. Where, Why? Why the number five? And why is it so short? Or why does the list exists? What What's your reasoning behind it? I'm just curious.Staffan Nöteberg 9:12 So you're right about multitasking that most people we cannot multitask if you don't have to pay attention to things like breathing and work at same time. But most people can't pay attention to more than one thing. And when we think that we are doing that, like we're listening to lecture and we're taking notes, were actually task switching. So we're switching back and forth. And when we're task switching, we make more errors, science shows and researchers and we're slower and we forget about good ideas. And in general, it's not the best way to complete things from what we learned in Lean, for example, when we're doing many things and so one one idea here in the book is our in this method is the shortlist as you mentioned, and the shortlist is like, in the morning, from the top of your head, write down five things on a paper on the piece of paper, instead of looking at your, you know, in, in my trainings, I am an exercise where we're asked people to, to, to write down every source of tasks that they have. And they think less about them and say, I have some things in my brain, I have something in my email inbox, I have some things in Trello. And I have some things in JIRA, I have some things on my refrigerator, and I have some post it's on my display. And there's a lot of sources of all these tasks. And then the next step is to look at all these and say, roughly how many tasks do I have in each of these. And usually, it aggregates to something between 80 and 200. So like, if you have 200 tasks there, if you have 100 tasks, it's impossible to make a prioritization to choose the best one because you can think about 100 tasks at the same time and see which one of these is most important right now. So instead, when you start morning, write down maximum five tasks on a piece of paper in front of you. Maximum five, and these are small tasks, so they should estimate them. If you estimate roughly you don't have to write down, it should not be things that takes more than two hours or something like that should be things that the tasks that take 10 minutes, two hours, some something in this, if they're bigger than YouTube, break something out and put them on on your list. And this is not the plan. It's not a competition or some kind of gamification, so that this is the sort of fight that I'm doing to complete today. It's more like moving away the tension of of gamification, instead of saying, These are my five candidates for my next, the one I'm going to pay attention to next, right, and then you don't have to think about anything else, all the other 100 tasks that you have promised someone or that you have thought about that you pressed you do. So because you have in front of you only these five, five is not magic, of course, but five is, is a number that usually we can look at five things and maybe compare them together. If it comes to 6, 7, 8, 9, then we have to make to look at some of them. So maybe you should have have have less than five, but not not more than five, I believe for most people. Yeah. And then then you pick one of these and say, I'm going to focus on this one. And you set an alarm, maybe to the next hour or something like that, to remind you to not stay too long, because maybe when you have worked with at one after an hour, you need to take a break or maybe you should reprioritize because he didn't believe that this was this was going to take this long time that that it took so you need some alarm to wake you up and then use your stop focus on on that that single task. And during the day if if something comes up, you get a new idea, either either you should write it down and put it somewhere else. Or you need to trade away something from your shortlist. You should never have more than five things on your on your shortlist. And this this many people try this and say it works for some people doesn't work but you need to you need to try yourself and be you know you we are different. So it might not be suitable for everyone.Joe Krebs 14:04 But I think you just answered my next question. I just want to clarify because that is the bridge to my next topic about agility here is so that the list is maximum five, right? Let's say this as a as a number here to work with, right? What would happen if like that stakeholder out there changes his mind and there would be a sixth item or a seventh item, because there is the risk that the list is going to grow. So you're saying like keep it at five, right? Something has to go from there. Yep. Just to keep it manageable,Staffan Nöteberg 14:35 maximum five, maybe have completed something so you'll have four three. Okay. And of course, these numbers are heuristics. You can use any number but it's good to put the limit and see how much but five is a good starting number. According to me at least.Joe Krebs 14:54 Yeah, there is also in your book. I don't I don't know the from the top of my head. Add, I don't know the exact details here right now. But you also have some advice on the time-boxing, right? How much time would be dedicated to these tasks. So let's say you're starting a task, let's say at 10.25am. In the morning, that timer would be set to 11 o'clock or something like that, right? So there's some some concrete advice at your book. But the time box is relatively manageable and short too right?. So it's short working increments before you take a break. Staffan Nöteberg 15:24 Yeah, a break or reprioritize, you looked at your shortlist again, and see, should I continue with this one? Or do that? One, do something else, maybe because I completed that one, or maybe something else became more prioritized. But you trust during that period that time box, your trust, your prioritization, I think that you shouldn't you distinguish between focusing and prioritizing. So when you have decided to focus, then you need to explore it. That and oh, and trust that you have chosen the right one, if something else comes up, write it down or, or something like that, but don't change your business idea. Every few minutes, just because something comes up.Joe Krebs 16:15 Yeah. Interesting. So so what I what I would like to touch on is and I think that is to connect with you have with the Pomodoro Technique, right, where it's also a time or is involved in time intervals. So time boxing, just in the Agile world, in general is a is a is a good strategy. Now, I do know that let's say in Scrum, the product backlog is not necessarily a list of tasks, why but it's just to see a container of things to be to be worked on eventually, but also the sprint backlog has has items in it. Let's say a product backlog very often has more than five items in it. How would you idea like map to like some some agile teams, you know missing? Some of those mono tasking techniques could be applied to a personal level? Is there anything we can do as a team is anything as an Agile team could do like a scrum team or a kanban team or somewhere that says like, we're gonna start introducing and mono tasking techniques to make us more productive, effective as a team. But also help us with the prioritization ordering effort as well, as you know, just like staying focus is is there any connect between those techniques?Staffan Nöteberg 17:33 I think so one thing is, of course, you can learn from my monitor skin that and then scale it to the team level and think what would that mean to do the same thing on the team level. But another thing is that what I talked about cohesion, so the team members are part of the same ecosystem as you are. And if you're a team, then you probably have a shared goal, you have the same goal. Otherwise, you're more like a group of people that have the same manager or something like that. But if your team you have the same goal, so So what what you're looking for, is to succeed with the school together. And if you're all skilled in this method, the monitors method, which which is a lot a lot of thing about how to progress and how to cooperate and how to treat stakeholders and recharging and so. But if you're all successful, I think you also responsible since you have a shared goal, to support each other, to help each other to be better at Mono tasking or whatever personal productivity method you're using. So you, as I said, we want to arrange an environment and circumstances so that we can be productive as individuals. But that also, since we have a shared do need that we need to create circumstances environment for teammates, so that they can be successful, then there are, of course, mob programming and pair programming, and then you're working together. But when we work individually, we need to help each other to work individually in a good way. Also, it's not not only that, I take care of my environment and my circumstances so that I can do mono tasking or Pomodoro, or GTD (Getting Things Done) or something else. It's also the issue to help other people with thatJoe Krebs 19:26 Yeah. So one thing I wanted to clarify and this is this is a great connect between the team and the individual and how this technique applies on different kinds of levels. I think that's great. There's obviously a lot to take away from teams have a very long laundry list of things to do, right? And just feel like they are not getting you know, like their time or they're not using their time necessarily wisely. That's what they're thinking and but they might not know like, what is the what's the missing thing and maybe it is something like that to really focus on on a few things. Now, here's something that I want to clarify this with you? If I read this, right, if I heard thi right, it's fascinating because, you know, way, way back when I was running, I did like cross country kind of running myself, there was always this thing of, if there was a hill, let's say, you would always try to run up the hill. And if you if you had to take a break, you know, for whatever reason, it was right on the top of the hill, not before the top of the hill, because you wanted to make sure it's easier to restart running again. So stopping at the hill was always like seeing something like very hard to restart running again, because you're already in the middle of a hill. But it was always when you're on the top of the hill was very easy for you to run. Now you're mono tasking is like by task. The second is don't finish the task at the end of the day. Because it makes it easier to start and transition into the next day. When I saw that, I was like thinking about that. I was like, that is very interesting. Tell me like how, because it's so opposite to how people think. Right? So it's like finishing a task before they go home. And let's say at the end of the day, and might put these 1015 minutes extra in, and then I would just want to finish my tasks, but you're saying mono tasking says don't finish it all by the end of the day? Because it makes it easier to start in the morning. Can you elaborate a little bit on this? Because I think that's great.Staffan Nöteberg 21:20 Yeah. So there was a researcher 100 years ago in Berlin called Bluma Zeigarnik. I think she came from Russia originally. But she worked in with psychology research in psychology in Berlin. She and her friends went to the coffee shops in Berlin. Every day and sister was psychologist, they had some psychology researchers that had a lot to talk about with each other. And so they stayed there for hours. And they ordered things and they discussed things and then they ordered more and discuss things. And after some hours, they call for the waiter and said, Hey, waiter can can we pay now. And then the waiter always knew exactly how much they had ordered, even though he didn't take any notes. And that was a little bit provocative to a group of psychologists, researchers. So they made an experiment one day. So they they sat there discussing ordering, discussing ordering, and they say hey, can we pay, and the waiter knew exactly how much they had ordered, and they paid. But then they stayed there for another 30 minutes, then the call for the waiter again. And when the waiter came there, they asked him, Hey, how much did we pay 30 minutes ago? And what do you think he answered?Joe Krebs 22:56 He didn't know.Staffan Nöteberg 22:58 He didn't know. He said, I've dropped out How could I know now. So he knew about it, as long as it was like an open Task to remember this. But as soon as, as they had paid it dropped it. So it didn't take in place in in his brain. And this was interesting, but this experiment is not very scientific, because it was only one person's very small sample. But Illuma went back to her office and made an experiment with, like, the first 150 people or something like that. And they got 20 tasks each small things like creating a clay finger or translating something from German, to to French, or, or something. And what it didn't know was a part of this experiment was that in 10, out of these 20, they were interrupted. So blue mark came there and said, Oh, I see you're working with task number six. Yeah, stop that and go on and work with task number seven. And afterwards, when when when they had finished everything. Bluma said like, can you write down now all the 20 tasks that you worked on on paper? And you know, if you have 20 things you have done, you won't remember all of them. So then she counted at the fact was that those that are interrupted in the remember twice as many of these compared to those that they had completed. So things that we haven't finished that we have started but we haven't finished demand room in our brain. But you can see in a positive way that we are still analyzing them and working on them and thinking about them. So if we end the day, usually, if you're commuting, and you think that before I go home, I need to complete this. And then I will take a bus or take my car or something home. But if you think in the other way, and think like, before I leave the office, I need to stop something, and leave in the middle I should have a read test if I'm a software engineer. So you stop something and you leave in the middle, then the next morning, you will be much eager to start with that one. And we knew about procrastination, that the hardest time that whatever we procrastinate, most is in the morning, if we can just stop procrastinating in the morning, then we will continue for the whole day because we have started something. So if instead stop something before we go home, then then we will be very eager to start with on that one. Immediately, when we come to the office usually will not tell this in trainings, someone raises their hand and say like, Hey, I'll try that. And if I do that, I can't sleep for the whole night because I have a problem. Of course, you shouldn't try it, you shouldn't do this. But for many people who are trying this, this is really helpful.Joe Krebs 26:19 Wow, this is this is cool that this is quite interesting that that person had sleep problems by trying this. Why? Because part of mono tasking is also you know, taking care of things like sleep and breaks and, and healthy living. Why? Why is that like part of money? It's an interesting, it's an interesting approach. It's so with all that research and science that goes into something like this. It's also like to do take breaks, and to purposely slow down. I don't know if that's exactly at those time limits of these tasks are describing but also to, to just to sleep, and have a healthy lifestyle that includes nutrition and everything. Why why is that so important? Staffan Nöteberg 27:05 so the method or the book is divided into six different areas where one is called recharge, creative thinking. So these sorts of things, the six things that I suggest that you should think about to be able to mono task, to be able to focus. And one of these students reached out creative thinking says, I mean, I'm not the expert of all the Healthy Living, I'm personally. But what I found, and I think most people agree on this is that if you are going to be the best version of yourself, if you are going to be the best due tomorrow, then you will have a much better probability or higher probability of being that if you have a healthier living, if you sleep the same hours every night, if you eat fruits and vegetables, if your exercise. And if you don't do that, it will be much harder to focus and focus on one thing.Joe Krebs 28:11 Yeah, that is that is also important for agile teams, where I would do very often I'm, you know, working with teams or organizations, but that is not part of the ritual, right? And for a variety of reasons, and sometimes it's just like, you know, what the things are in organizations, but it is an important piece to point out like we're humans, we're part of this, of, let's say, any kind of method and recharging is a key thing, right? How is something like that being incorporated into an into an Agile team, right? On an individual level? I think that's a great idea, and probably easier to do, right? Because it's me influencing my own thing, but how does it work on a team? We're not gonna say you guys go into sleeping chambers during the day and taking breaks or anything like that, but how would that look like on a on a team level?Staffan Nöteberg 29:04 I think first I want to say that it's not that you shouldn't be an Olympic athlete, it's more like, you can always be a bit better than than what you were yesterday. But I think in an Agile team, you know, in extreme programming, there's one of these best practices was first called 40 hours a week, and then it was changed to a sustainable pace. If I remember correctly, it was a long time ago, I read this book. I think it's part of this, it. Ultimately, it's a personal responsibility, of course, but as a team, you can create a culture where it's not cool to stay the whole night to fix some bugs or something like that. You need to have a sustainable base. As Kent Beck pointed out already, and if I think no, this is a credit card, that if you overcharge the credit card, you can buy something right now that you couldn't buy otherwise, but you will have to pay with interest in the long term and that that's the same for teams. I think that if they have a culture where they don't take care of the people in the team, when it comes to breaks, and weekends and other things, then they will have to pay with interest in the long term.Joe Krebs 30:33 Yeah. Yeah, no, definitely I agree. And that was part of Extreme Programming even before Agile Manifesto. So this is deeply, deeply rooted, sustainable pace and having you know, if there was an overtime in a sprint, or iteration that there wouldn't be one in the following. So there was some form of balancing going on your book itself, which is great. I like visuals in a book, right? You drew them yourself. Which is, which is also great to see those notes and supported by visuals. I just like to read books like this, I think it just reinforces but you also say in this mono tasking, it's better for teams to or individuals to write by hand. Notes in journaling, rather than on a laptop.Staffan Nöteberg 31:20 I think depends on what you're going to use use it for. If if writing something that you want to distribute to the that you want to save for a long time, it's much better right in a computer, of course. But if you want want your brain to digest things to analyze it, in, we learn from doing things not from listening, when we listen to something like your podcast, you might get inspired but if we don't do something about it, or think about it or discuss it with someone then we will have forgotten about it one week later. So there are a lot of research showing that if if you write down something in need to like, think and that's especially if if you draw something if you make a mind mapping more or try to try to think of it in in pictures, what does this mean all the diagrams connecting,Joe Krebs 32:25 sketchnoting, for example?Staffan Nöteberg 32:27 Yeah, exactly. Then you learn more it stays in your head because in the brain the memory in the brain is not like a structured database. It's not like SQL, it's more like many many fragments of associations. And when you have new you learn something new and when you hear something new, you need to connect it to some of these fragments and when you think about it more then maybe some door opens in there are some fried fragment comes up some other Association and you can connect your your new learning to that one. And if you have a discussion about something like something you hear in this podcast or something new you learn that you have written down or so then it's more much more likely that you will save it actually and have it connected to some some other Association Yeah. And as I understand it, it's not an issue that or memory is not big enough we can read would be it would be possible to know a lot more than anyone has known so far. And the problem is that we it's not structured in in the heads we need to it's a different thing than the computer database and we need to connect it so we can pick it up when it when it's suitable. Joe Krebs 34:00 Yeah very very interesting stuff and obviously the book is filled with lots of material like this a lot of individuals and teams might find useful applying in their in their day to day work. Did you write your book using mono tasking? Did you use some of those techniques like like you basically just you know took your method in your in your own writing.Staffan Nöteberg 34:24 I did exactly like that. But I'm saying that this doesn't mean that this is the best method for everyone. But I think that if you read something like this, a book like this, then you will learn a lot of things and maybe you can try some some of these and test them and maybe some some will suit you and some will not suit you but you will learn more about your own productivity.Joe Krebs 34:53 Absolutely. I also see coaches Scrum Masters leaders working within organizations increasing agility, he's taking some of the research you have put together in that book, and providing the evidence to really run some experiments within the organization. Right. So there's continuous improvement going on, within organizations, change management. And some of those concept could be, could be applied to any of these efforts and run some experiments on are they showing the same impact as they will do in an individual productivity improvement also on on other levels, so I think it's might give some food for thought for. For some, some employees in organizations listening to the answers, I'd take a piece of that and run an experiment and see how that goes to just like the task switching or preventing task switching, and possibly do take the breaks and things like that we discussed. We're not finishing a task by the end of the day, things we have discussed here in this podcast together and just like try some experiments, but again, the book has many, many more. You also mentioned in your in your book, someone I think there was a little side story, where somebody actually got a promotion probably not only because of that, but somebody got a promotion and one thing was that somebody started listening to podcasts in their transition time going from home to work. And using that transition time effectively somebody listened to podcasts and got a promotion out of it now I cannot guarantee by listening to Agile FM that you will be getting a promotion out of this thing but you might be listening to this in your car right now while driving so please drive safely. But transition time is also part of mono tasking and and to use that wisely could be having really really good benefits. So thank you Staffan for being my guest today and sharing your thoughts great thoughts on mono tasking here with me? But more importantly with all the listeners out there that possibly already or will be becoming interested in mono tasking. Thank you so much, Staffan.Staffan Nöteberg 37:02 Thanks, you it's been a pleasure to talk to you.Joe Krebs 37:06 Thank you for listening to Agile FM, the radio for the Agile community. I'm your host Joe Krebs. If you're interested in more programming and additional podcasts, please go to www agile.fm. Talk to you soon.

Join Julie Chickering and Brian Milner as they discuss strategies you can use to get started on the right foot with your new organization. Overview It's the new year, and for many people, that means starting a new chapter in their life, maybe in a new position, with a new team, or possibly an entirely new organization. It's the perfect time for reflection to determine what you can do in these first few days and weeks to set yourself up for success. So, we thought it would be a great time to take this episode of the show to highlight some strategies you can use to hit the ground running. In this episode of the Agile Mentors podcast, Brian Milner and Julie Chickering discuss some strategies to set the stage for success in your new position. We will walk you through the vital steps for settling into your team and making an impact no matter what level of the ladder you are on. Plus, what to ask when you are interviewing to ensure you find the right fit. Listen now to discover: [01:40] - Julie Chickering is on the show to discuss starting strong with your new organization. [02:15] - How to use team retrospective to identify where things are going well to amplify the good stuff while on a discovery mission of what needs work. [03:35] - The one thing that Julie cautions about in one-on-one conversations that will help you avoid being influenced by others' opinions of their team members. [05:22] - How to create curiosity instead of animosity by offering reciprocal grace to help everyone work better together. [07:17] - Brian shares how to use an improvement board to keep a running track of things while identifying your next target, stay on the right track and avoid the worst-case scenario (as referenced by Henrik Kniberg in the Spotify Model - Part 2). [09:23] - What Brian calls his 15-minute' cheat code" for understanding the dynamics of a team. [11:31] - Julie shares her improvement backlog one-on-one ONE thing for Scrum Masters. [12:08] - Essential techniques to help developers make an impact and utilize their skills in their new team. [13:57] - How to get off on the right foot with a new team as a product owner. [14:14] - Julie shares how to determine if an agile framework like Scrum is helping you meet your business goals (or not). [15:34] - If you cannot communicate and collaborate with your stakeholders… you'll never deliver value to them. [16:32] - How story mapping exercises can help product owners. [18:31] - Why communication is the key to top-to-bottom team success. [19:40] - The most important questions to ask when you are interviewing to determine if the organization is a good fit for what you bring to the table. [22:17] - Why it's important to remember every interaction during an interview is a part of the job interview. [22:33] - Brian shares a story of why it's crucial to determine if the company you are going to work for is looking for someone agile or Agile. [24:42] - Why it's essential to do a background check on a company you're considering hitching your wagon to. [25:38] - Start with where you are: how to start strong if you have the skills and are certified but need to gain experience. [28:30] - How can you use your skills to give back and advance in your career? [29:38] - How to highlight your experience and use it to your advantage when seeking various roles within a company. [32:40] - The most powerful question you can ask your team that will help you start the new year fresh. References and resources mentioned in the show Spotify Engineering Culture - Part 2 (aka the "Spotify Model") The Culture Code How does project management work in Agile? with Julie Chickering #7: The Sprint Review is not a Demo with Julie Chickering Agile Mentors Community Meetup #13: What Does Cross-Functional Really Mean? with Lance Dacy Mountain Goat Software Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Julie Chickering is the brains and brawn behind JC Agile Consulting, believes that Lean and Agile practices are packed with potential — to enable positive culture change, business agility, and breakthrough results. Julie is a past president and board member of the Agile Project Management Network (APLN), a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), as well as a traditional Project Management Professional (PMP).

Join Julie Chickering and Brian Milner as they discuss strategies you can use to get started on the right foot with your new organization. Overview It's the new year, and for many people, that means starting a new chapter in their life, maybe in a new position, with a new team, or possibly an entirely new organization. It's the perfect time for reflection to determine what you can do in these first few days and weeks to set yourself up for success. So, we thought it would be a great time to take this episode of the show to highlight some strategies you can use to hit the ground running. In this episode of the Agile Mentors podcast, Brian Milner and Julie Chickering discuss some strategies to set the stage for success in your new position. We will walk you through the vital steps for settling into your team and making an impact no matter what level of the ladder you are on. Plus, what to ask when you are interviewing to ensure you find the right fit. Listen now to discover: [01:40] - Julie Chickering is on the show to discuss starting strong with your new organization. [02:15] - How to use team retrospective to identify where things are going well to amplify the good stuff while on a discovery mission of what needs work. [03:35] - The one thing that Julie cautions about in one-on-one conversations that will help you avoid being influenced by others' opinions of their team members. [05:22] - How to create curiosity instead of animosity by offering reciprocal grace to help everyone work better together. [07:17] - Brian shares how to use an improvement board to keep a running track of things while identifying your next target, stay on the right track and avoid the worst-case scenario (as referenced by Henrik Kniberg in the Spotify Model - Part 2). [09:23] - What Brian calls his 15-minute' cheat code" for understanding the dynamics of a team. [11:31] - Julie shares her improvement backlog one-on-one ONE thing for Scrum Masters. [12:08] - Essential techniques to help developers make an impact and utilize their skills in their new team. [13:57] - How to get off on the right foot with a new team as a product owner. [14:14] - Julie shares how to determine if an agile framework like Scrum is helping you meet your business goals (or not). [15:34] - If you cannot communicate and collaborate with your stakeholders… you'll never deliver value to them. [16:32] - How story mapping exercises can help product owners. [18:31] - Why communication is the key to top-to-bottom team success. [19:40] - The most important questions to ask when you are interviewing to determine if the organization is a good fit for what you bring to the table. [22:17] - Why it's important to remember every interaction during an interview is a part of the job interview. [22:33] - Brian shares a story of why it's crucial to determine if the company you are going to work for is looking for someone agile or Agile. [24:42] - Why it's essential to do a background check on a company you're considering hitching your wagon to. [25:38] - Start with where you are: how to start strong if you have the skills and are certified but need to gain experience. [28:30] - How can you use your skills to give back and advance in your career? [29:38] - How to highlight your experience and use it to your advantage when seeking various roles within a company. [32:40] - The most powerful question you can ask your team that will help you start the new year fresh. References and resources mentioned in the show Spotify Engineering Culture - Part 2 (aka the "Spotify Model") The Culture Code How does project management work in Agile? with Julie Chickering #7: The Sprint Review is not a Demo with Julie Chickering Agile Mentors Community Meetup #13: What Does Cross-Functional Really Mean? with Lance Dacy Mountain Goat Software Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Julie Chickering is the brains and brawn behind JC Agile Consulting, believes that Lean and Agile practices are packed with potential — to enable positive culture change, business agility, and breakthrough results. Julie is a past president and board member of the Agile Project Management Network (APLN), a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), as well as a traditional Project Management Professional (PMP).

Henrik Kniberg joins Brian to talk about creating the Spotify Model. Overview There are ways to get things done, and then there are the best ways to get things done. But the only way to arrive at the right way of doing things is to try and fail, to see what works and what doesn't. Henrik Kniberg is a Certified Scrum Trainer who has worked with teams like Spotify and LEGO to help them implement agile culture in their fast-moving and fast-growing environments. He's also the co-creator of the Spotify Model. Today on the show, Henrik joins Brian to discuss his accidental introduction to Spotify and how he inspired the company to transition to Scrum. We discuss the leadership model that helped the startup scale while holding its own against behemoths like Apple and Google. Plus, an inside look at his time as a designer with Minecraft. Listen now to discover: [01:55] - Brian shares Henrik's Agile Product Ownership in a Nutshell that's become required viewing. [02:22] - Brian shares some of the places on Henrik's resume, including Lego, Minecraft, and Spotify. [03:42] - Henrik shares his love for playing accompaniment musical instruments. [04:08] - Brian shares his professional musical background. [04:35] - Introducing the Spotify engineering culture videos that have sparked a thousand conversations about scaling challenges. [05:10] - Henrik shares the story of his accidental introduction to Spotify and how he inspired the startups to transition to Scrum. [8:26] - Henrik describes how the lack of off-the-shelf scaling frameworks led to his work with Spotify. [08:45] - Standard Scrum, by the books, works for small teams, but for scaling at larger teams like the one at Spotify, it's hard to find a "one size fits all" approach. [10:59] - How realizing 'this is what's helping us swim' during their impressive growth got all the technical leaders of Spotify on board with using Agile. [12:50] - Henrik shares the leadership model that helped Spotify scale up. [14:58] - How Spotify used the speed of innovation to stand against goliath-like competitors like Apple and Google. [16:30] - Convincing the investors that being able to iterate quickly (rather than through roadmaps) was the key to winning the game. [18:09] - Fueling future inspiration—why Spotify instituted the twice-a-year hack weeks for their entire organization. [21:36] - Henrik shares why leadership is the key to culture and driving change in an Agile organization. [24:19] - Brian shares why it's wise to make a change where you can benefit a company rather than hanging on to the now-extinct gold watch at retirement. [25:53] - "Go ahead and copy the Spotify model… and don't worry about someone telling you that you're doing it wrong because that's just you adapting." [26:44] - How the Spotify culture videos had the opposite outcome from what Henrik had planned. [29:54] - Brian asks Henrik an important Minecraft question (as posed by his daughter.) [30:36] - Henrik shares insider information about the guiding principles for designers at Minecraft (and how that led to the creation of Striders). [32:34] - Brian shares why copy/paste is only sometimes best. [32:46] - Henrik shares how creating video games differs from life applications. Listen next time when we'll be discussing… Getting to Small with Lance Dacy References and resources mentioned in the show Agile Product Ownership in a Nutshell Spotify Engineering Culture - Part 1 (aka the "Spotify Model") Spotify Engineering Culture - Part 2 (aka the "Spotify Model") Mountain Goat Software Agile Mentors Community Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Henrik Kniberg is former member of the board of directors of the Agile Alliance and enjoys helping companies succeed with both the technical and human sides of software development. A Certified Scrum Trainer he’s worked with teams like Spotify and LEGO to help them implement agile culture in their fast-moving and fast-growing environments. He’s also the co-creator of the Spotify Model.

Henrik Kniberg joins Brian to talk about creating the Spotify Model. Overview There are ways to get things done, and then there are the best ways to get things done. But the only way to arrive at the right way of doing things is to try and fail, to see what works and what doesn't. Henrik Kniberg is a Certified Scrum Trainer who has worked with teams like Spotify and LEGO to help them implement agile culture in their fast-moving and fast-growing environments. He's also the co-creator of the Spotify Model. Today on the show, Henrik joins Brian to discuss his accidental introduction to Spotify and how he inspired the company to transition to Scrum. We discuss the leadership model that helped the startup scale while holding its own against behemoths like Apple and Google. Plus, an inside look at his time as a designer with Minecraft. Listen now to discover: [01:55] - Brian shares Henrik's Agile Product Ownership in a Nutshell that's become required viewing. [02:22] - Brian shares some of the places on Henrik's resume, including Lego, Minecraft, and Spotify. [03:42] - Henrik shares his love for playing accompaniment musical instruments. [04:08] - Brian shares his professional musical background. [04:35] - Introducing the Spotify engineering culture videos that have sparked a thousand conversations about scaling challenges. [05:10] - Henrik shares the story of his accidental introduction to Spotify and how he inspired the startups to transition to Scrum. [8:26] - Henrik describes how the lack of off-the-shelf scaling frameworks led to his work with Spotify. [08:45] - Standard Scrum, by the books, works for small teams, but for scaling at larger teams like the one at Spotify, it's hard to find a "one size fits all" approach. [10:59] - How realizing 'this is what's helping us swim' during their impressive growth got all the technical leaders of Spotify on board with using Agile. [12:50] - Henrik shares the leadership model that helped Spotify scale up. [14:58] - How Spotify used the speed of innovation to stand against goliath-like competitors like Apple and Google. [16:30] - Convincing the investors that being able to iterate quickly (rather than through roadmaps) was the key to winning the game. [18:09] - Fueling future inspiration—why Spotify instituted the twice-a-year hack weeks for their entire organization. [21:36] - Henrik shares why leadership is the key to culture and driving change in an Agile organization. [24:19] - Brian shares why it's wise to make a change where you can benefit a company rather than hanging on to the now-extinct gold watch at retirement. [25:53] - "Go ahead and copy the Spotify model… and don't worry about someone telling you that you're doing it wrong because that's just you adapting." [26:44] - How the Spotify culture videos had the opposite outcome from what Henrik had planned. [29:54] - Brian asks Henrik an important Minecraft question (as posed by his daughter.) [30:36] - Henrik shares insider information about the guiding principles for designers at Minecraft (and how that led to the creation of Striders). [32:34] - Brian shares why copy/paste is only sometimes best. [32:46] - Henrik shares how creating video games differs from life applications. Listen next time when we'll be discussing… Getting to Small with Lance Dacy References and resources mentioned in the show Agile Product Ownership in a Nutshell Spotify Engineering Culture - Part 1 (aka the "Spotify Model") Spotify Engineering Culture - Part 2 (aka the "Spotify Model") Mountain Goat Software Agile Mentors Community Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Henrik Kniberg is former member of the board of directors of the Agile Alliance and enjoys helping companies succeed with both the technical and human sides of software development. A Certified Scrum Trainer he’s worked with teams like Spotify and LEGO to help them implement agile culture in their fast-moving and fast-growing environments. He’s also the co-creator of the Spotify Model.

Scott Dunn joins Brian to talk about how Agile teams and organizations respond in difficult economic times. Overview Right now, the word recession is being bandied about, and big companies like Apple and Facebook are already beginning to scale back. But economic downturns can present opportunities for the right individuals. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with more than 20 years of experience. Today on the show, Scott joins Brian to discuss why now is the moment to hone in on your mission and determine your job market value and how Agile training can prepare you for any opportunity that comes your way. Listen now to discover: [01:52] - Brian shares how the word recession triggers companies to batten down the hatches. [03:19] - How leaning into Agile in an organization creates a natural operating cost reduction. [04:52] - Studies show organizations that invest during recessions are better positioned at the back end of it to, you know, accelerate like a rocket out of it. [06:55] - Scott explains how the Japanese concept of ‘danger opportunity’ offers teams a chance ‘to really do Agile’ and operate efficiently with less. [9:34] - How difficult times help companies prioritize and hone in on their mission and vision and stop trying to be everything to everybody. [12:57] - How organizations create unease and lack of employee trust. [14:46] - How Agile can help workplaces bring humanity back when responding to change. [16:18] -Scott shares a conversation with his daughter about voting with your feet and your values. [19:16] -Scott explains why companies need to invest in top talent to lower their technical debt. [20:17] - Why times like these require ruthlessness in proving out your theories. [22:10] - Scott shares why down economic times are opportunities in disguise for individuals to determine the types of environments they want to help flourish. [25:13] - Determining your job market value and the importance of looking at the total package of an opportunity. [28:30] -Is it really Agile, or is it Agile in name only? [31:33] - How taking classes at Mountain Goat can prepare you to bring your knowledge and skills to any opportunity. Listen next time when we'll be discussing… Scaling with Henrik Kniberg. References and resources mentioned in the show Mountain Goat Software Agile Mentors Community Scrum Alliance Jim Collins The Hedgehog Concept Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with over 20 years of experience coaching and training companies like NASA, EMC/Dell Technologies, Yahoo!, Technicolor, and eBay to transition to an agile approach using Scrum.

Scott Dunn joins Brian to talk about how Agile teams and organizations respond in difficult economic times. Overview Right now, the word recession is being bandied about, and big companies like Apple and Facebook are already beginning to scale back. But economic downturns can present opportunities for the right individuals. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with more than 20 years of experience. Today on the show, Scott joins Brian to discuss why now is the moment to hone in on your mission and determine your job market value and how Agile training can prepare you for any opportunity that comes your way. Listen now to discover: [01:52] - Brian shares how the word recession triggers companies to batten down the hatches. [03:19] - How leaning into Agile in an organization creates a natural operating cost reduction. [04:52] - Studies show organizations that invest during recessions are better positioned at the back end of it to, you know, accelerate like a rocket out of it. [06:55] - Scott explains how the Japanese concept of ‘danger opportunity’ offers teams a chance ‘to really do Agile’ and operate efficiently with less. [9:34] - How difficult times help companies prioritize and hone in on their mission and vision and stop trying to be everything to everybody. [12:57] - How organizations create unease and lack of employee trust. [14:46] - How Agile can help workplaces bring humanity back when responding to change. [16:18] -Scott shares a conversation with his daughter about voting with your feet and your values. [19:16] -Scott explains why companies need to invest in top talent to lower their technical debt. [20:17] - Why times like these require ruthlessness in proving out your theories. [22:10] - Scott shares why down economic times are opportunities in disguise for individuals to determine the types of environments they want to help flourish. [25:13] - Determining your job market value and the importance of looking at the total package of an opportunity. [28:30] -Is it really Agile, or is it Agile in name only? [31:33] - How taking classes at Mountain Goat can prepare you to bring your knowledge and skills to any opportunity. Listen next time when we'll be discussing… Scaling with Henrik Kniberg. References and resources mentioned in the show Mountain Goat Software Agile Mentors Community Scrum Alliance Jim Collins The Hedgehog Concept Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Scott Dunn is a Certified Enterprise Coach and Scrum Trainer with over 20 years of experience coaching and training companies like NASA, EMC/Dell Technologies, Yahoo!, Technicolor, and eBay to transition to an agile approach using Scrum.

It seems these days people are looking for the one-size-fits-all approach to get all of their organizational challenges solved. The problem with that is that there is no single approach that you can map to your organization. How to deal with these challenges?Henrik Kniberg joins Sander to discuss how to grow both culture and frameworks to fit them into your organization and what you can do to support it.  What you'll discover in this show:-        Contrary to popular belief, the Spotify Model does not exist -        Copy pasting cultures and frameworks, does not work -        Finding your corporate culture is an empirical process too Speakers: Henrik Kniberg I code Minecraft @ Mojang, coach teams & leaders, and jam a lot!I do Minecraft design/development at Mojang, and coach the teams using Agile & Lean principles and methods like Scrum, XP, and Kanban. Previously worked with Spotify and LEGO, helping to implement agile culture there and in other fast-moving and fast-growing environments.  I cofounded OperationalExcellence.com together with Niklas Modig.  I accidentally sort of co-created something called the Spotify Model. https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1  I'm into climate change, and co-founded http://GoClimate.com. Help us save the world! Contact Henrik:http://www.crisp.se/henrik.kniberghttps://www.linkedin.com/in/hkniberg/Twitter  Sander Dur (host)Scrum Master, Agile Coach, trainer, and podcast host for ‘Mastering Agility”Sander Dur is a Professional Scrum Trainer at Scrum.org, podcast host of Mastering Agility, Professional Scrum Master and Lead Agile Consultant, and trainer at Xebia. Besides this, he's an avid writer for predominantly Serious Scrum on Medium.com. Sander has a major passion for the human side in complex domains. Ensuring a high level of psychological safety, therefore, is a critical part of his work. Organizations in complex domains can only survive when innovating. Innovation can only take place with the right balance between low social friction and high intellectual friction. While most organizations now understand how to apply Agile frameworks, they struggle with the delivery of value. Psychological safety is the next step in this evolution and Sander has a huge drive to help organizations reach that step.  He gained experience as a Scrum Master, Agile Coach, and Leadership consultant in many different top-tier organizations, including Nike and ASML.   Let's connect! Sander is always up for new connections and discussions! Masteringagility.org https://www.linkedin.com/in/sanderdur/ https://xebia.com/academy/nl/trainers/sander-dur https://sander-dur.medium.com/ Additional resources: https://www.minecraft.net/nl-nlDiscord community: https://discord.gg/6YJamBJxUVSupport the show

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. This story starts with a team that is doing detailed tasking and planning during a refinement session. The Product Owner for that team behaved like a project manager, dictating what each of the team members should do, and in what order. This was not helped by the fact that the team was heavily silo-ed around skills.  In this segment, we discuss the importance of understanding the “flow” in the team, and Jeroen refers to the talk by Henrik Kniberg on the impact of not limiting the work in progress. Featured Book of the Week: Getting Things Done by David Allen In Getting Things Done by David Allen, Jeroen found a method that helps him manage the stress that comes from being deliberate and structured about managing our own work. In this segment, we talk about some of the main aspects of the GTD (Getting Things Done) method, and the lessons we can take from that method and apply with the teams we work with. How can Angela (the Agile Coach) quickly build healthy relationships with the teams she's supposed to help? What were the steps she followed to help the Breeze App team fight off the competition? Find out how Angela helped Naomi and the team go from “behind” to being ahead of Intuition Bank, by focusing on the people! Download the first 4 chapters of the BOOK for FREE while it is in Beta! About Jeroen de Jong Jeroen started his career as a self-employed jack-of-all-trades in IT and is passionate about Agile. He is determined to keep learning and to share his knowledge with others. You can link with Jeroen de Jong on LinkedIn and connect with Jeroen de Jong on Twitter.

Em 2012 Henrik Kniberg criou o modelo Spotify, onde ele descrevia toda a estrutura organizacional da empresa. Dentro deste documento o especialista criou três pilares importantes para o Spotify, eram elas: As Squads, tribos, capítulos e as guildas. Neste episódio, o Rodrigo Pinto, Co-founder da Agile.Inc e Agile School explicou todo o processo e a história de como os capítulos foram criados e a sua importância dentro das empresas atualmente. Ouça o a parte 2 deste episódio aqui. Caso tenha alguma dúvida, você enviar uma mensagem para nós que respondemos: https://bit.ly/3KDAKKQ ou um e-mail para faleconosco@agileschool.com.br • Nosso site: http://agileschool.com.br • Blog: https://agileschool.com.br/category/a… • Ouça nosso Podcast: - Spotify: https://spoti.fi/31GeHfy - iTunes:https://apple.co/31OAxNO • LinkedIn:https://www.linkedin.com/company/agil… • Instagram: https://www.instagram.com/agile.school/ • Facebook: https://www.facebook.com/agileschoolbr/

Em 2012 Henrik Kniberg criou o modelo Spotify, onde ele descrevia toda a estrutura organizacional da empresa. Dentro deste documento o especialista criou três pilares importantes para o Spotify, eram elas: As Squads, tribos, capítulos e as guildas. Neste episódio, vamos continuar o assunto que começamos no anterior. Rodrigo Pinto, Co-founder da Agile.Inc e Agile School explicou todo o processo e a história de como os capítulos foram criados e a sua importância dentro das empresas atualmente. Ouça a parte 1 deste assunto aqui Caso tenha alguma dúvida, você enviar uma mensagem para nós que respondemos: https://bit.ly/3KDAKKQ ou um e-mail para faleconosco@agileschool.com.br • Nosso site: http://agileschool.com.br • Blog: https://agileschool.com.br/category/a… • Ouça nosso Podcast: - Spotify: https://spoti.fi/31GeHfy - iTunes:https://apple.co/31OAxNO • LinkedIn:https://www.linkedin.com/company/agil… • Instagram: https://www.instagram.com/agile.school/ • Facebook: https://www.facebook.com/agileschoolbr/

#Agile_World #AgileWorld #Agile #AgileTalkShow Online Agile World Better English Website Agile World Better English LinkedIn AgileWorld.Better English Facebook Agile World Better English YouTube Agile World Better English Vimeo Hosts Jessey Drewsen Steve Moubray Big Thank You to Sabrina C E Bruce Karl A L Smith Agile World © 2021 Broadcast Media, Hollywood, California | Better English Content by Hosts --- Send in a voice message: https://anchor.fm/agile-world/message

«Нам бонусы за это дадут, мы с этим и будем работать. А помогать вот той команде... А нахрена? Зачем им помогать, если у меня KPI и мне бонусы дают за другое?». «Как выбрать правильную цель — это вообще самый главный вопрос. Потому что, например, приходят фасилитаторы, все веселятся и выбирают пять целей. А компании с этим потом жить. И представим, что хотя бы одна из них неправильная — значит, одна пятая часть ресурсов идет не туда, то есть мы не тем занимаемся». Подкаст выходит при поддержке ProductSense Academy: https://bit.ly/3h5ZeQ9 Собеседник: Андрей Бадин CEO, Product Lab fb.com/andrey.badin Ведущий подкаста: Юра Агеев ФБ: fb.com/ageev.yuri Подписывайтесь на канал анонсов подкаста: https://t.me/mspodcast. О чем говорим: 1:48 Как Андрей перешел от проектного управления в госсекторе к внедрению OKR 3:55 Что такое OKR — инструмент, фреймворк или методология 4:50 Как появились и менялись OKR и почему они старше KPI и BSC 8:39 Основные ошибки при использовании OKR 15:16 Как долго внедряются и закрепляются OKR 16:10 Как правильно формулировать цели. Метрики в OKR 19:20 «Делать» и «быть» в формулировании целей 24:15 Архетипы, проблема выбора и свобода переформулирования целей для сотрудников 28:27 Cинхронзация в работе с OKR и вдохновляющий результат 32:18 Как выбрать правильные цели. Подход Double Diamond 37:21 Как понять, что самое главное. North Star-метрика при использовании OKR. Фреймворк для генерации целей 41:02 Как формулировать OKR: сверху вниз или снизу вверх 44:22 Как контролировать единство целей при их декомпозиции 47:36 Воздействие OKR на разные уровни культуры и синхронизация целей в разных компаниях 53:14 Мотивация в OKR. Суперцели, мастерство и автономия 58:48 Финансовая мотивация, бонусы и амбициозные цели 1:00:57 Альтернативы OKR. Spotify Rhyth 1:05:33 Фреймворк Flow OKR. Scrum и Kanban Мы упоминаем: Статья «flOwKRs. Objectives and Key Results in Flow», Jurgen Appelo https://bit.ly/3IdGycR Презентация «Spotify Rhythm. How we create focus», Henrik Kniberg https://bit.ly/3JLamOD Видео и транскрипция «Spotify Engineering Culture (part 1)», Henrik Kniberg https://bit.ly/36nuK9Z Видео и транскрипция «Spotify Engineering Culture (part 2)», Henrik Kniberg https://bit.ly/3h8tucX Книга Джона Дорра «Измеряйте самое важное. Как Google, Intel и другие компании добиваются роста с помощью OKR» https://bit.ly/3p4LXvx

LeSS zwingt den Product Owner, seinen Fokus auf sie Priorisierung zu legen und die Klärung von Details zu delegieren! Noch klarer bringt es unser Gast Eike Gehler auf den Punkt: "Prioritization over clarification". Eike ist erfahrener Agile Coach und langjähriger Scrum Master - v.a. bringt er aber sehr viel Erfahrung in sehr großen und skalierten Kontexten mit ins Gespräch ein. Er mag keine Blaupausen und mag am Liebsten zusammen mit den Organisationen die er begleitet herausfinden, welcher Skalierungsansatz im jeweiligen Kontext der geeignete ist. Dabei bedient er sich aufgrund seiner Erfahrung gerne im "Baukasten" verschiedener Skalierungs-Frameworks und -Modelle. Dennoch hat er einen Favoriten: das Framework LeSS - kurz für "Large-Scale Scrum". Dennoch betont Eike Gehler, dass die entscheidende Frage der Produkt-Kontext sei, in dem das Skalierungsvorhaben stattfindet. Tim beleuchtet zusammen mit Eike zunächst dessen eigene Weg in die Agilität sowie seine aktuellen Wirkungskreise in oft großen Organisationen. Zusammen rätseln die beiden, warum das sogenannte "Spotify"-Modell (oder zumindest die dort genannten organisatorischen Formate) derzeit so viele Nachahmer hat. Warum muss jetzt plötzlich alles Squad, Tribe, Gilde usw. heißen? Warum legen Organisationen soviel Hoffnung in diese Organisationsmuster, obwohl dies von Henrik Kniberg und Anders Ivarsson, die damals bei Spotify die Transformation begleiteten, nie als Skalierungs-Framework gemeint war. Tim stellt die These auf, dass "Spotify" derzeit sogar SAFe den Rang abläuft. Tiefer geht es dann um das LeSS-Framework. Hier wird vieles reduziert: für bis zu sieben Feature-Teams ist dort nur EIN Product Owner und nur EIN Product Backlog (innerhalb einer Area) vorgesehen. Eike erklärt zunächst den Begriff des Feature-Teams und wie schwer es oft ist, für diese Idee in großen, bislang silo-artig organisierten Unternehmen Befürworter zu finden. Aber wenn es nur einen Product Owner in LeSS gibt - wie verhält es sich dann mit den Scrum Mastern? Wie viele Scrum Master sind z.B. in einer Area mit fünf Feature Teams sinnvoll? Im letzten Teil geht es nach dieser Herleitung dann ganz konkret um diese Product Owner Rolle in LeSS und welche Herausforderungen sie mit sich bringt. Eike Gehler gibt in diesem Zuge auch noch wertvolle Tipps für Menschen, die als Product Owner in LeSS arbeiten. Quellen zum sog. "Spotify-Model" und LeSS: - Die damalige Beschreibung von Henrik Kniberg und Anders Ivarsson der Skalierung bei Spotify... die dann als das Spotify-Model (miss)verstanden wurde: https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf - Spotify Engineering Culture, dieses Video wird üblicherweise als Video über das "Spotify-Model" referenziert: https://blog.crisp.se/2014/03/27/henrikkniberg/spotify-engineering-culture-part-1 - Henrik Kniberg: No, I didn't invent the Spotify model: https://blog.crisp.se/2015/06/07/henrikkniberg/no-i-didnt-invent-the-spotify-model - Heutige Sicht von Henrik Kniberg auf Scrum@Scale im Vergleich zum "Spotify-Model": https://www.scruminc.com/spotify-model-scrum-at-scale/ - Die offizielle Beschreibung von LeSS mit allen Details, die ihr über das (De)Skalierungs-Framework LeSS wissen müsst: https://less.works/ Wenn ihr mit Eike in Kontakt treten wollt, freut er sich über eure Nachricht auf folgenden Kanälen: Eike Gehler Mail : eike@aykey.de, LinkedIn (https://linkedin.com/in/eike-gehler-a2479968/) oder Web (https://aykey.de/) Telefon: 089 208044440 Im Zusammenhang mit dieser Episode ist auch die Folge 41 rund um Skalierung empfehlenswert: Product Owner im skalierten Umfeld mit Björn Schotte Welche Herausforderungen erlebt ihr selbst als Product Owner in LeSS oder Ansätzen die sich an das Spotify-Model anlehnen? Wir freuen uns, wenn du deine eigenen Erfahrungen mit uns in einem Kommentar auf unserer Webseite (https://produktwerker.de/) oder auf unserer Produktwerker LinkedIn-Seite (https://www.linkedin.com/company/produktwerker/) teilst.

0:00 - Intro 2:30 - Réchauffement : Gif ou Gif? 7:03 - Jurgen Apello vs. Henrik Kniberg 13:42 - Sinek vs. Brown vs. Pink 22:12 - Esther Derby vs. Lyssa Adkins 27:35 - Tableau physique vs. Numérique 35:27 - Points vs. T-Shirt sizing vs. Jours personne 41:33 - Estimate vs. #noestimate 46:18 - Sunset graph vs. Release BurnUp Chart 55:01 - Projet vs. Produit 1:01:13 - Scaling vs. Descaling 1:12:47 - Throughput vs. Vélocité 1:16:03 - Scrum vs. Kanban 1:21:00 - Équipe co-localisée vs. Distribuée 1:29:16 - Agile est un Mindset vs. Framework vs. Métho 1:30:29 - Conclusion --------------------------------------------------------------- Karine Castonguay https://www.linkedin.com/in/karine-castonguay/ Liens: Beyond Budgeting : https://www.amazon.ca/Beyond-Budgeting-Managers-Annual-Performance/dp/1578518660/ WiP Run Chart -comme alternative au CFD : https://youtu.be/xRW5-P1B1MI?t=2359

Vi har med Henrik Kniberg och Niklas Modig som tillsammans har skapat ett nytt utbildningsbolag! Vi går in på vad operational excellence faktiskt är! Hur kan man utbilda en hel organisation? Hur kan man skala ett utbildning för att maximera effekten? Hur får man med sig cheferna i transformationen? Det och mycket mer!    Tack till www.delibr.com samt www.crisp.se för ni gör podden möjlig!

Geoff and Paul recap their Prestigious Pints conversation with agile inspiration of theirs, Henrik Kniberg. They talked about the history of the Spotify model, and what made him decide to go back to being a developer again instead of coaching.

In this episode, DuDs and Jimbo discuss a tweet from Minecraft Game Developer, Henrik Kniberg, about ways to make surface aquifers more likely to connect with underground aquifers. Plus, we have a listener comment from Galaxy Fox asking DuDs and Jimbo if they could add any animal (not always angry mob) to Minecraft what would they add? They also sent us an amazing dragon fan art, which you can find on our Twitter and in your-creations on Discord. Also, Is Minecraft getting too easy? DuDs and Jimbo have some thoughts about this age-old question. Henrik Aquifers Tweet: https://twitter.com/henrikkniberg/status/1423367796206051329?s=20 Thank you to our Milk level Patrons: aubni, ChiefBigBear, Crock, DeadWalker, FragileRock, ohbeep, StoneFigure and viperoustuna. Discord: https://discord.gg/gqnKyeZ Patreon: https://patreon.com/thewitheringeffect Website: http://thewitheringeffect.com/ E-Mail: podcast@thewitheringeffect.com Voice Message: https://anchor.fm/thewitheringeffect/message Twitter: https://twitter.com/WitheringEffect YouTube: https://youtube.com/thewitheringeffect Instagram: https://instagram.com/witheringeffect Show Hosts DuDs YouTube: https://youtube.com/DuDs_vs DuDs Twitter: https://twitter.com/DuDs_vs DuDs Twitch: https://twitch.tv/DuDs_vs Jimbo YouTube: https://youtube.com/JimboSlice23Gaming Jimbo Twitter: https://twitter.com/JimboSlice23_ Jimbo Twitch: https://twitch.tv/JimboSlice23_ Digital Producer CarlRyds YouTube: https://youtube.com/CarlRydsGaming CarlRyds Twitter: https://twitter.com/CarlRyds CarlRyds Twitch: https://twitch.tv/CarlRydsGaming Music Master DiiKoj YouTube: https://youtube.com/DiiKoj DiiKoj Twitter: https://twitter.com/DiiKoj

Joel and Jonny are joined by Minecraft game developer Henrik Kniberg to discuss the team effort behind the new terrain generation planned for The Caves & Cliffs Update Part 2, floating around in the Echoing Void DLC, and pleasant surprises surfacing in Minecraft community feedback.

Inscrivez-vous au webinaire du lancement de la formation Yaniro pour un max de cadeaux exclusifs : Ici (places limitées ! )Résumé de l'épisode

Rajiv Srivatsa co-founded Urban Ladder, a top online furniture brand in 2012.  With over 5000 designs across 35 categories such as living, dining, bedroom, study, and decor, Urban Ladder was established as an online-first brand. The company went on to become one of the most loved brands in India and was sold to Reliance in November 2020.  Srivatsa now leads global venture capital firm Antler in India. The firm has plans to invest in over 150 early-stage startups over four years. In this episode, Rajiv talks to us about product-market fit, early-stage fundraising, the professional growth of a founder, and more. You can follow Rajiv on Twitter.  Reference to the minimum viable product meme was from Henrik Kniberg's blog.Get $10,000 free credits to use Freshworks products (including the brand new Freshworks CRM packed with AI-based lead scoring, phone, email, activity capture, and more) by joining the Freshworks for Startups program. Click here to check eligibility.About the GuestRajiv Srivatsa has 18+ years of experience in building scalable products and companies across B2C commerce, B2C tech, mobile and supply chain. He Co-founded Urban Ladder and helped build it towards becoming the #1 omnichannel brand for furniture in India.  He currently leads the deployment and operations of global early-stage VC firm Antler in India.Sign up for regular updates from The Orbit Shift Podcast.The Orbit Shift Podcast is powered by Freshworks Inc. a global SaaS company headquartered in San Mateo, California. If you enjoyed listening to this podcast, consider giving us a five-star rating on Apple Podcasts. Host and Producer - Jayadevan PKAssistant Producer - Shashwath JAudio Engineer - Rajesh Subramanian  

Henrik Kniberg is the author of numerous books, helpful YouTube videos, and currently a team member working on the Minecraft team. Check out the full show notes at TheAgileWire.com YouTube: https://youtu.be/O3tFSHiR1aY

I detta bonusavsnitt snicksnackar jag med Henrik Kniberg och Marcus Castenfors om agilitet och arbetsglädje. Alla var på distans och min mick fungerade inte som den skulle så jag ber om ursäkt för något burkigt ljud, innehållet är däremot mycket intressant!    Tack snälla för att du lyssnar! Missa inte att agilaHRpodden finns på de sociala plattformarna och på agilahrpodden.se. I min Facebook-grupp fortsätter diskussionerna och frågeställningarna, gå gärna med!   Länkar: Spotify Engineering Culture Crisps blog   Crisp Happiness Index  Henrik & Marcus webinarie om arbetsglädje Hapkey

This week I've been playing New World a new MMO coming from Amazon Games Studios. I've always been checking out Marvel's Avengers and another new release called Spellbreak, which is a Mage Battle Royale. I was also very lucky to sit down with Henrik Kniberg from Mojang Studios, developers behind Minecraft and we spoke about a range of topics like prototyping and the value of audience feedback. 00:00 Introduction 3:53 New World Preview 12:00 Marvel's Avengers Campaign 22:41 Interview with Henrik Kniberg 1:03:27 Spellbreak 1:09:34 Charts 1:10:27 Coming soon RELATED LINKS Support This Week In Video Games content https://www.patreon.com/thisweekinvideogames Subscribe to This Week In Video Games YouTube Channel https://www.youtube.com/channel/UCyIiL5xk1ut5HY6pPnBUXlQ Rate & Review the podcast https://ratethispodcast.com/thisweekinvideogames More ways to listen https://anchor.fm/this-week-in-video-games https://gopod.me/thisweekinvideogames Music by Christian Hounslow and Jaya McQuaid.

HENRIK KNIBERG   Henrik Kniberg is an organizational consultant and developer at Crisp in Stockholm. He does coaching and Minecraft development at Mojang, and has previously worked at Lego and Spotify.   He enjoys helping companies succeed with both the technical and human sides of product development using agile and lean principles, as described in his popular books ”Scrum and XP from the Trenches” and ”Kanban and Scrum, making the most of both” and ”Lean from the Trenches”, as well as his viral videos ”Agile Product Ownership in a Nutshell” and ”Spotify Engineering Culture”.   Henrik is also engaged in climate change, he created the video Friendly Guide to Climate Change and is involved with GoClimateNeutral, Trine, and other startups in that space.   https://twitter.com/henrikkniberg     SUPPORT THE PODCAST   This show is brought to you by the Visual Thinking and Sketchnoting Boot Camp online course. This unique and highly practical signature course will teach you all the necessary elements that you need to employ visual thinking for your profession.   With the help of the course, you will boost your thinking and communication skills as well as improve your productivity and effectiveness.   Find more information at https://www.udemy.com/course/visual-thinking-and-sketchnoting-boot-camp/?referralCode=D0574A03FF3E6CADC63F   Subscribe to Yuri's newsletter: http://eepurl.com/gWi_if

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/From his cabin on an island off the coast of Sweden, Henrik Kniberg, author of the viral 'Spotify Culture' video, joins me in this week's episode to share what he learned as a top Agile Coach at Spotify.Henrik is a creative powerhouse with prodigious talent as a musician, coach, author and developer. He brings these skills together to transform the organisations with which he works.In this episode, we talk:- Teams 'self-aligning' for scale- Patient leadership- Why we draw- Achieving Agile Rhythm- Dealing with technical debt  Enjoy! Links:Spotify Culture Video Agile Product Ownership in a NutshellFriendly Guide to Climate ChangeBooks by Henrik

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/From his cabin on an island off the coast of Sweden, Henrik Kniberg, author of the viral 'Spotify Culture' video, joins me in this week's episode to share what he learned as a top Agile Coach at Spotify.Henrik is a creative powerhouse with prodigious talent as a musician, coach, author and developer. He brings these skills together to transform the organisations with which he works.In this episode, we talk:- Teams 'self-aligning' for scale- Patient leadership- Why we draw- Achieving Agile Rhythm- Dealing with technical debt  Enjoy! Links:Spotify Culture Video Agile Product Ownership in a NutshellFriendly Guide to Climate ChangeBooks by Henrik

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/From his cabin on an island off the coast of Sweden, Henrik Kniberg, author of the viral 'Spotify Culture' video, joins me in this week's episode to share what he learned as a top Agile Coach at Spotify.Henrik is a creative powerhouse with prodigious talent as a musician, coach, author and developer. He brings these skills together to transform the organisations with which he works.In this episode, we talk:- Teams 'self-aligning' for scale- Patient leadership- Why we draw- Achieving Agile Rhythm- Dealing with technical debt  Enjoy! Links:Spotify Culture Video Agile Product Ownership in a NutshellFriendly Guide to Climate ChangeBooks by Henrik

Er Danske Banks nye model – Spotify modellen – overhovedet en model? Og i givet fald, hvad består modellen så af? Sammen med dagens gæst, Kristian Haugaard, tager vi disse og andre spørgsmål relateret til Spotify modellen under kærlig behandling. I næste afsnit dykker vi yderligere ned i forudsætningerne for at få Spotify modellen til at virke. Links: Kotter: https://www.youtube.com/watch?v=Pc7EVXnF2aI Scaling Agile @ Spotify https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf Spotify Engineering Culture, part I og II https://youtu.be/4GK1NDTWbkY https://youtu.be/vOt4BbWLWQw The Spotify Tribe (Kevin Goldsmith, Tribe Lead, Spark Conf. 2015) https://www.infoq.com/presentations/spotify-culture/ There is No Spotify Model (Marcin Floryan, Chapter Lead, Spark conf. 2016) https://www.infoq.com/presentations/spotify-culture-stc/ No, I didn’t invent the Spotify model (Henrik Kniberg, blog 2015) https://blog.crisp.se/2015/06/07/henrikkniberg/no-i-didnt-invent-the-spotify-model

A big shout out to IDEO! We respect you! Black Lives Matter! In this episode, we go from bats to hips to Henrik Kniberg's MVP. We also give you a sneak peek at how companies run remote user testing during the pandemic. 00:27 NDI Camera wins the best product of the week 06:35 Hats off to IDEO - BLM! 13:27 'Tiktoking' is a word 15:25 How to do remote user testing right 21:50 Henrik Kniberg's abused MVP 29:09 Swedish Midsummer and Post Pandemic Life 34:00 Why Bats don't die from Corona Virus? 35:48 Hips don't lie, Bats don't die! 38:30 Outro NDI Camera: https://apps.apple.com/us/app/ndi-hx-camera/id1477266080 Mobbin: https://mobbin.design/ Figma: https://www.figma.com/ Mural: https://www.mural.co/ Bats don't die: https://theconversation.com/why-bats-dont-get-sick-from-the-viruses-they-carry-but-humans-can-137151 Hips don't lie: https://www.youtube.com/watch?v=DUT5rEU6pqM --- Gayanjith Premalal (Ganji) LinkedIn: https://www.linkedin.com/in/gayanjithpremalal/ Instagram: https://www.instagram.com/ganjilive/ TikTok: www.tiktok.com/@ganjilive Twitter:https://twitter.com/ganji_09 Medium: https://medium.com/@gayanjith Harshadewa Ariyasinghe (Harsha) LinkedIn: https://www.linkedin.com/in/harshadewa/ Instagram: https://www.instagram.com/harshadewa TikTok: https://www.tiktok.com/@harshadewalk Twitter: https://twitter.com/harshadewa Medium: https://medium.com/@harshadewa Youtube: https://www.youtube.com/c/HarshadewaAriyasinghe Yasith Abeynayaka (sirStinkySocks) LinkedIn: https://www.linkedin.com/in/yasithabeynayaka/ Instagram: https://www.instagram.com/sirstinkysocks/ TikTok: https://www.tiktok.com/@sirstinkysocks Twitter: https://twitter.com/yasiththeba Medium: https://medium.com/@Yasith Youtube: https://www.youtube.com/channel/UCnezQGxnUrxbVCwNYKJEVXg/

Nesse episódio Fernando Cruz, Lula e o Henrique Inbertti, Head de Agilidade no Luiza Labs, conversam sobre o que é Agilidade Organizacional , Times de Alta Performance e o movimento de "Squadificação" das empresas. Referências: Livro A Empresa Conectada: https://www.amazon.com.br/Empresa-Conectada-Dave-Gray/dp/8575223348/ref=sr_1_1?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&keywords=a+empresa+conectada&qid=1582983590&sr=8-1 Paper Scaling Agile at Spotify (by Henrik Kniberg & Anders Ivarsson) : https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf Times de Alta Performance (by Cristina Wodtke) : http://eleganthack.com/designing-high-performing-teams/ Episódio Podcast Castelo de Mentiras: https://anchor.fm/lovetheproblem/episodes/Ep-03---Portflio-Agil-x-Castelo-de-Mentiras-e9uu0e eXtreme Programming (artigos K21) : https://www.knowledge21.com.br/blog/category/metodos-e-frameworks/xp/ Imagem Fluxo de Valor Ágil - K21 : https://www.knowledge21.com.br/escondido/wp-content/uploads/2019/06/cadeia-valor-agil.jpg Evento Product Summit: https://productsummit.com.br/ Perfis e canais: Perfil do Fernando Cruz: https://www.linkedin.com/in/fernando-lopes-da-cruz-461aa111/ Perfil do Henrique Imbertti.: https://www.linkedin.com/in/imbertti/ Perfil do Lula: https://www.linkedin.com/in/lpsrod/ Perfil da K21: https://www.linkedin.com/mwlite/company/knowledge21

Behövs ledarskap? Vad är skillnaden på formellt och informellt ledarskap? Vilka typer av ledarskap behövs? Vem är leveransansvarig? Vad har fyrvägskorsning med ledarskap att göra? Hur kan man applicera agilt ledarskap utanför IT verksamhet? Hur ska man som ledare hantera accountability? Vi får även en formel för produktivitet! Vi kommer även in på Mojang och Minecraft!

В этом выпуске к нам присоединился Кирилл Золовкин, геймдизайнер Gripper, игры-номинанта в категориях «лучший звук» и «лучший нарратив» на DevGAMM 2019. Мы поговорили о том, как делать личные проекты на сложные темы, быть честным с собой и выражать самые глубокие переживания через игровые механики. Gripper — Экшен-RPG на машине в пустыне будущего, вы вырываете из боссов сердца, поющие голосами родных, чтобы открыть себе дорогу домой. В пустыне ты и твоя машина. На связи оглохшая сестра. Ничего страшного, ты тоже не хочешь слышать. Вселенная Gripper — это Burning Man, где андроиды сжигают людей на фестивалях. В мире, где нет никого без физических увечий, у вас остаётся тачка с крюком и совсем немного времени, чтобы научиться убивать. Шоуноуты: — Как эмоции и переживания становятся механиками; — Как сделать «личный» проект; — Инди игры как авторское кино; — Прототипирование и геймдизайн; — Как и где учиться геймдизайну; — Как собрать команду; — Организация командной работы; — Мотивация, ошибки и советы; — О конференциях, прессе и стримерах; — О лицензировании музыки. Материалы и ссылки: Gripper — https://vk.com/gripper_game Digital Banana — https://digital-banana.ru Scream School — https://screamschool.ru GamedevHouse — http://gamedev.house Индикатор — http://indikator.space Книга Scrum and XP from the Trenches by Henrik Kniberg В выпуске использована музыка группы Kill The Barber! Группа в ВК — https://vk.com/killthebarber Альбом FRIEND​|​SHIP — https://killthebarber.bandcamp.com/album/friend-ship Напоминаем, о Международной бизнес-конференции для игровой индустрии White Nights St.Petersburg, которая пройдет 19-20 июня. Расписание и билеты на официальном сайте https://wnconf.com/. Скидка 10% при регистрации с промокодом everypod10.

В этом выпуске к нам присоединился Кирилл Золовкин, геймдизайнер Gripper, игры-номинанта в категориях «лучший звук» и «лучший нарратив» на DevGAMM 2019. Мы поговорили о том, как делать личные проекты на сложные темы, быть честным с собой и выражать самые глубокие переживания через игровые механики. Gripper — Экшен-RPG на машине в пустыне будущего, вы вырываете из боссов сердца, поющие голосами родных, чтобы открыть себе дорогу домой. В пустыне ты и твоя машина. На связи оглохшая сестра. Ничего страшного, ты тоже не хочешь слышать. Вселенная Gripper — это Burning Man, где андроиды сжигают людей на фестивалях. В мире, где нет никого без физических увечий, у вас остаётся тачка с крюком и совсем немного времени, чтобы научиться убивать. Шоуноуты: — Как эмоции и переживания становятся механиками; — Как сделать «личный» проект; — Инди игры как авторское кино; — Прототипирование и геймдизайн; — Как и где учиться геймдизайну; — Как собрать команду; — Организация командной работы; — Мотивация, ошибки и советы; — О конференциях, прессе и стримерах; — О лицензировании музыки. Материалы и ссылки: Gripper — https://vk.com/gripper_game Digital Banana — https://digital-banana.ru Scream School — https://screamschool.ru GamedevHouse — http://gamedev.house Индикатор — http://indikator.space Книга Scrum and XP from the Trenches by Henrik Kniberg В выпуске использована музыка группы Kill The Barber! Группа в ВК — https://vk.com/killthebarber Альбом FRIEND​|​SHIP — https://killthebarber.bandcamp.com/album/friend-ship Напоминаем, о Международной бизнес-конференции для игровой индустрии White Nights St.Petersburg, которая пройдет 19-20 июня. Расписание и билеты на официальном сайте https://wnconf.com/. Скидка 10% при регистрации с промокодом everypod10.

Ash Maurya on Rocketship.FM, Richard Cheng on the Drunken PM, Jeff Gothelf on Boss Level, the mutual learning model on Troubleshooting Agile, and Amy Edmondson on Lead From The Heart. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting May 27, 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. ASH MAURYA ON ROCKETSHIP.FM The Rocketship.FM podcast featured Ash Maurya with hosts Michael Sacca and Mike Belsito. They started by talking about the lean canvas. Ash described the lean canvas as a one-page business planning tool that acts as an alternative to spending time writing a large document and exists because, when we start a new business, we know very little about it. The lean canvas was derived from Alex Osterwalder’s business model canvas and optimized for early-stage entrepreneurs. Ash says the lean canvas addresses the innovator’s bias of spending too much time thinking and talking about the solution. It asks questions like: Who are your customers? Who might be the early adopters? Why would they use your solution? How will you get your solution in front of those customers? How will you defend against competition? Where does the money come from? What is the revenue stream? Ash then described writing a follow-up book to Running Lean called Scaling Lean because readers of the first book wanted a better way to satisfy stakeholders looking for financial forecasts. He sees Running Lean as a book for the entrepreneur-to-customer conversation and Scaling Lean as a book for the conversation between the entrepreneur and other stakeholders. The usual way of sizing a market is by estimating revenue from what percentage of a market one thinks one can take, which Ash calls working top-down. Instead, Scaling Lean works bottom-up by modeling the inputs to customer value (such as a pricing model and a lifetime value model) and using this customer value model to produce a revenue estimate. Scaling Lean encourages a staged launch for your business. He compares this with Tesla’s rollout of the Model 3 by testing the riskiest assumptions of the business model by producing the Roadster, Model S, and Model X first. They talked about Fermi estimation and how you can use it to invalidate a model in as little as five minutes. Regarding inputs to such estimates, he says pricing is the most critical, followed by potential lifetime of a customer. He then says you test your estimate against the minimum success criteria, that is, the minimum number (revenue, impact, etc.) for the years invested in the startup to not have been a waste of time. You use this to build your traction model and, with each milestone, you think in terms of achieving ten times what you achieved in the previous milestone. Returning to the Tesla example, the Model S was intended be sold at ten times the quantity of the Roadster and the Model 3 is intended to sell at ten times the quantity of the Model S. Regarding the order in which to address risk, he says to think of the game Jenga (where you try to find where the stack is strongest and move pieces from there) and do the opposite. You want to build the riskiest parts first. He also shared a metaphor for preferring a focus on the customer’s problem over a solution-focus. He describes a solution-focus as building a key and then looking for a door it will open. Problem-focus, by contrast, is like finding a door that needs to be opened and trying to build a key for it. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/interview-ash-maurya-of-lean-canvas-on-scaling-lean/id808014240?i=1000437174185 Website link: https://omny.fm/shows/rocketship-fm/interview-ash-maurya-of-lean-canvas-on-scaling-l-1 RICHARD CHENG ON THE DRUNKEN PM The Drunken PM podcast featured Richard Cheng with host Dave Prior. They talked about product ownership anti-patterns such as a product owner treating the dev team like they’re her vendor or like they report to her. This puts you in a situation where the team is incentivized to keep the PO happy rather than tell her the unvarnished truth all the time. In these situations, the dev teams don’t tell the PO about problems right away and the later the PO finds out, the fewer options she has for addressing them. Instead, Richard says we need a safe environment where the dev team and PO can be open and candid with each other. They talked about whether or not building prototypes is agile and Dave admitted that he is not a big subscriber to Henrik Kniberg’s “skateboard - bicycle - motorcycle - car” model of incremental development and, if he knows he’s going to have a car in the end, he would prefer you build a steering wheel so he can give feedback on it. Richard pointed out that the danger of this line of thinking is that you get a tendency to build vertical layers instead of horizontal slices. Richard doesn’t want a technical person as his product owner since he believes that technical people favor these vertical layers. I take issue with the idea that a “technical person” is automatically assumed to have no “product thinking” skills. I think a better way to put it is to say he doesn’t want someone who lacks the training in lean startup and product management skills in the PO role, regardless of their technical skills. Other than that, I’m in total agreement with Richard here, especially regarding how the same line of thinking that leads to software being delivered in vertical layers also leads to vertically-layered organizational design. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/the-perfect-product-owner-w-richard-cheng-cst/id1121124593?i=1000436943035 Website link: https://soundcloud.com/drunkenpmradio/richard-cheng-the-perfect-product-owner-april-2019 JEFF GOTHELF ON THE BOSS LEVEL PODCAST The Boss Level podcast featured Jeff Gothelf with host Sami Honkonen. They started with a discussion of humility and the idea of having strong opinions, weakly held. Jeff says we need to admit that the ideas we put forward, even our strategic vision, are just our best guesses. When a leader puts out such a vision, she needs to open up room for her team to discuss and push back on those ideas. Sami added that this change in thinking coincides with a change in terminology to be a better fit for a world of uncertainty where words like roadmap get replaced with words like assumption, belief, bet, and experiment. They then addressed the topic of collaboration. For Jeff, organizing for collaboration means organizing in cross-functional teams and he says that even digital native organizations often get this wrong. He also says that these teams need to be empowered to make their own sprint-level decisions as they are closest to the information and, if they get it wrong, they can correct it in the next sprint. Jeff thinks the motto of every organization today should be to say that they are, in Astro Teller’s words, “enthusiastic skeptics,” excited to figure out the next improvement to their product or service. Sami asked about how organizations can change so that they begin to value continuous learning. Jeff says that we’re fighting a hundred years of manufacturing mindset that says, “The more stuff we make, the more value we deliver to our customers.” In this mindset, people see customer site visits and having engineers talk to customers as somehow less productive. He says that companies resist changing this mindset for two reasons: 1) it feels like it takes authority away from leaders; and 2) incentive structures: we don’t pay people for discovery work or collaboration or agility; we pay them for heroism and for delivery. Jeff says that this is the reason organizations fail to become agile or digitally transform: they buy all the books and training, change language and team structures, build tribes, chapters, guilds, and squads, but they don’t change the performance management system. They still measure people on the old way of working. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/jeff-gothelf-on-sense-and-respond/id1041885043?i=1000437033229 Website link: https://www.bosslevelpodcast.com/jeff-gothelf-on-sense-and-respond/ THE MUTUAL LEARNING MODEL ON TROUBLESHOOTING AGILE The Troubleshooting Agile podcast, with hosts Jeffrey Fredrick and Douglas Squirrel, featured a three-part series on the mutual learning model. The first two episodes covered the first three values of the mutual learning model: informed choice, transparency, and curiosity. The third episode covered accountability and compassion. It started with a definition of accountability from the article “Eight Behaviours for Smarter Teams” and Squirrel told a story about the origin of the word “accountability” from the time of Henry II. Jeffrey described how his relationship of accountability was transformed when he watched a talk by Kent Beck called, “Ease At Work.” Kent talked about accountability as a personal obligation to render an account of his own thoughts and feelings and how this changed Kent’s experience at work. Jeffrey sees this kind of accountability as being important for having a learning culture at work and supporting the previous two values of transparency and curiosity. Jeffrey talked about the connection between accountability and compassion, saying that when people are accountable to one another, it is a lot easier to be compassionate because you start to understand more of what went into their actions and the positions they’re arguing for. Jeffrey then pointed out a place where he finds a lack of compassion for the people in power. They also included a discussion of having compassion for yourself. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/mutual-learning-model-accountability-and-compassion/id1327456890?i=1000437494515 Website link: https://soundcloud.com/troubleshootingagile/mutual-learning-model-accountability-and-compassion AMY EDMONDSON ON LEAD FROM THE HEART The Lead From The Heart podcast featured Amy Edmondson with host Mark Crowley. Amy defined a “psychologically safe workplace” as one in which people believe they can bring their full self to work, speak up, and have their ideas, questions, and concerns welcomed. She says workplaces with high psychological safety are uncommon and organizations often have pockets of both low and high psychological safety. They talked about Google’s use of Amy’s psychological safety research to figure out what makes for high team performance. Mark made a distinction between psychological safety and physical safety and Amy responded that the two kinds of safety actually have a strong relationship. She cited the airline industry discovering through the investigation of black boxes that the majority of crashes involved somebody recognizing a concern and not being heard. She then clarified a common misconception about psychological safety. She said that when she refers to a workplace as being psychologically safe, she doesn’t mean that those in such a workplace are free from criticism or pushback or always feel good about themselves. She actually means the opposite. Psychologically safe workplaces have a high degree of candor. She contrasted this with college campuses that hold “safe spaces” where you cannot say anything that may remotely hurt someone’s feelings. Mark asked why we hold back on candor. Amy says it is a combination of how we’re socialized and how our brains work. We are highly tuned in to other’s impressions of us, particularly in hierarchical contexts. She says that many managers don’t create the conditions for psychological safety because they tend to mimic the behavior of the managers they’ve had in the past and haven’t stopped to connect their own experience of when they’ve done their best work to their management or leadership style so that their employees can do their best work. She says this tendency is a reflex and the problem is that, every now and then, this reflex is given a faulty signal that it works. For example, managing through fear can work in the short term when the task is simple and prescribed, clearly measured, and done individually. But very little of our work today has those attributes: it is complex, collaborative, and requires ingenuity to do it well. Under those conditions, fear doesn’t work. They talked about what you would look for in a candidate for a management position to ensure you get someone who can create a psychologically safe environment. She says that you want to look for people with high emotional intelligence. They should care about other’s opinions and needs but have enough self-awareness to know that their own life doesn’t depend on approval from others. You’re looking instead for passion, curiosity, and drive. Mark brought up a Deloitte study that said that 70% of people choose not to speak up about a problem at work even when they believe that not addressing it will harm the company. Amy says this is not because people rationally weigh the odds but is an unconscious act of spontaneous sense-making and temporal discounting in which we overweight an immediate event and underweight future events. Managers can address this, she says, by being willing to name the challenges faced and by asking questions. Mark asked about what we can learn from the case studies she has written about: the Wells Fargo fraudulent accounts scandal and Volkswagen emissions scandal. Amy asks us to imagine that the goals that the Wells Fargo and Volkswagen executives set for their organizations were not understood to be ridiculous at the outset and may have been intended as stretch goals. She says that when you are eager to set stretch goals, you need to have open ears. Being able to sell eight financial services products per customer is a hypothesis. Being able to create a green diesel that passes emissions tests in the US is a hypothesis. There is nothing wrong with setting these as stretch goals as long as you also encourage the people selling and developing these products to report all of the data that is coming back from the field and you adjust the goals based on this data. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/amy-edmondson-why-psychological-safety-breeds-exceptionally/id1365633369?i=1000431400656 Website link: https://www.blubrry.com/leadfromtheheartpodcast/42334779/amy-edmondson-why-psychological-safety-breeds-exceptionally-high-performing-teams/ 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:

En el episodio de hoy hablamos sobre uno de los roles peor entendidos en desarrollo ágil, el Product Owner – sus responsabilidades principales, su papel como mediador entre stakeholders y desarrolladores para no hacer todo lo que piden o la correlación entre el valor de una historia de usuario y su tamaño. También comentamos una una serie de compromisos entre el equipo de desarrollo y el product owner para reducir los riesgos de inclumplir los plazos razonables para entregar una funcionalidad o producto (por ej.: encontrar un equilibrio entre el trabajo reactivo y el proactivo) y las diferencias entre un product owner y un product manager. Enlaces recomendados: Excelente vídeo de Henrik Kniberg ("Scrum and XP from the trenches") explicando lo que hace un PO en la práctica (subtitulado en español): https://youtu.be/5pm0lpa1VVw Vanesa Tejada, Head of Product Delivery en LATAM Airlines, sobre el product Owner y la labor de conexión entre roles: https://vanesatejada.com/2018/04/29/el-product-owner-y-la-labor-de-conexion-entre-roles/ Spike – ¿Qué es y para qué sirve un spike en Scrum? Alberto Romeu en el blog del informático: https://albertoromeu.com/spike-scrum/ Lectura recomendada: Agile Product Management with Scrum: creating products that customers love. Pichler, R. (2010): https://www.amazon.es/Agile-Product-Management-Scrum-Addison-Wesley/dp/0321605780 Hackers/Founders: https://hf.cx Sitio de Brian Balfour en el que habla de Growth y adquisición de usuarios: https://brianbalfour.com

Så er der et afsnit for dem der virkelig kan lide at nørde når det kommer til Agile. Baseret på en workshop som Tore netop har afholdt, dykker vi ned i de "fysiske love" der gælder, når vi taler produktudvikling, organisering og skalering. Lyt med når vi gennemgår de 3 fysiske love, og lær bl.a. hvad skalering og helvedsmetafoer har med hinanden at gøre! Vi taler i udsendelsen om en video af Henrik Kniberg, og den linker vi til her: https://www.youtube.com/watch?v=CostXs2p6r0 00:12: intro 02:56: Fysikken bag SAFe 40:36: Afrunding og tak for i dag

In this episode Adam talks to Ben Orenstein about the common mistakes people make when working on a new project that prevent them from getting it to the finish line. Topics include: Why deadlines are critical Using manual processes to avoid building features entirely How launching a stripped down version of your idea can help you build the right thing Recognizing when you don't need to solve a problem yet Why you shouldn't design your entire UI up front How evolutionary design applies to both code and interface design Why you should always finish a feature before starting the next one Applying this approach to Ben's current project Tuple Sponsors: Rollbar, sign up at https://rollbar.com/fullstackradio and install Rollbar in your app to receive a $100 gift card for Open Collective Cloudinary, sign up and get 300,000 images/videos, 10GB of storage and 20GB of monthly bandwidth for free Links: The Art of Product, Ben's podcast Tuple, Ben's current project "You Should Take a Codecation" Trailmix.life, Ben's first codecation SaaS Briefs.fm, Ben's second codecation SaaS Nomadlist, by Pieter Levels Airline List Basecamp 6 week cycles "How we structure our work and teams at Basecamp" "What six weeks of work looks like" (at Basecamp) "Making Sense of MVP", by Henrik Kniberg

Frågar du någon i ett utvecklingsprojekt idag, svarar “alla” att de använder Scrum. Eller så svarar hen mer svävande att “projektet är Scrumish”. I den här podden städar vi bland begreppen. Det är en agil metod som kännetecknas av korsfunktionella team. Experten Jonas Bolldén diskuterar med  Jonas Jaani. De förklarar tillsammans vad det är och hur det fungerar. De grundläggande begreppen reds ut: product backlog, user story, krav, sprintar, review, beställare (produktägare), utvecklare (teammedlem), Scrum-master och stakeholders/intressenter. Det är ett ramverk för utveckling, men också ett förhållningssätt, en kultur som betonar engagemang, mod, fokus, öppenhet, respekt - mycket handlar om relationer. Jonas Bolldén poängterar också att metoden inte är ett projekt; med förstudier, tidplaner och budget, utan enbart en metod för genomförandet. Blanda inte ihop de två begreppen! Det är inte svårt. Använd Scrum-guiden, den finns här. 19 sidor senare har du koll! Jonas Bolldén, Jonas Jaani (25:08) PRENUMERERA – podcast Effekten iPhone, Android, e-post Jonas Bolldén Mer material / länkar: Guide - http://www.scrumguides.org/  Bra författare/böcker: Henrik Kniberg - https://www.infoq.com/minibooks/scrum-xp-from-the-trenches-2 Gunther Verheyen - https://www.bokus.com/bok/9789087537203/scrum-a-pocket-guide/ Ken Schwaber Jeff Sutherland Mike Cohn – exv https://www.mountaingoatsoftware.com/blog Utvecklingsprojekt ger del av nyttan (avsnitt 12) -podavsnitt Den digitala trädgården (avsnitt 52) - poddavsnitt Direktlänk till detta avsnitt: https://www.effekten.se/scrum-en-introduktion/ 

Vi har med oss Henrik Kniberg! Vi börjar med att rota i Henriks bakgrund och hur han upptäckte den agila världen. Vad är skillnaden på agilt och lean? Vi pratar om skillnad på organisationsförändring och ett experiment. Vi kommer även in på klimatfrågan där Henrik idag lägger sitt största fokus!

For this episode, my guest is Henrik Kniberg. Henrik is a prominent figure in the agile community. If you’ve seen the video on Spotify engineering culture, that video is created by him. He has also authored several books on agile. Henrik is also one of the early guests of the the podcast and the previous episode we did was about two years ago. Back then we discussed Henrik’s agile coaching work at Lego and Spotify and how he helped his kids win a robot battle against experienced programmers. But now, recently, he has shifted his professional focus towards something more important. He’s focusing on reducing the impact of climate change. We talk about how to be climate neutral, how to invest in climate projects, the community Henrik is running called Climate Crisplet, and how companies should deal with climate change.

Jonathan Beri (@beriberikix) spoke with us about his double life: Particle.io product manager by day, maker by night (and weekends). Jonathan wrote a chapter about piDuino5 Mobile Robot Platform in JavaScript Robotics. Product manager resources from product.careers and Ken Norton's Newsletter. For an alternate take, there is a good cartoon about effective product management from Henrik Kniberg. For getting into open source, see the guide from Github. Also, there is a newi-sh consortium, the TODO group, with guides and resources about running open source projects. There is also the often useful Google's developer documentation style guide. NerdRage’s video on the chemistry of etching The Essential Guide to Electronics in Shenzhen by Bunnie Huang Speaking of Robot Operating System (we did, briefly), IEEE Spectrum had a nice history of ROS.

    One of the most important relationships for a Product Owner, is that of a ScrumMaster or Coach.   This is your main partner in helping the team build awesome products and continually improve.  The healthy tension and focus that a seasoned ScrumMaster brings to the table will amplify the team and help support the product organization. In this episode, your hear from an experienced ScrumMaster and coach Maureen Green, as she talks about how she collaborates with PO’s and how we can complement them.   Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host Gojko Adzic - https://gojko.net/2016/02/01/potentially-shippable/ Henrik Kniberg - http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp Mike Cohn - https://www.mountaingoatsoftware.com/blog/scrummasters-should-not-also-be-product-owners Roman Pichler - http://www.romanpichler.com/blog/every-great-product-owner-needs-great-scrummaster/

Today my guest is Henrik Kniberg. Henrik is well known for his books and for his work with Spotify, Lego and many others. Henrik works through Crisp, a Swedish consultancy that has published their company DNA online. The DNA consists of all the essential principles, processes and agreements with which the company operates. We discuss the unorthodox organizational model at Crisp, Henrik’s work with his clients, and how his kids, aged 10 and 11, won a robot battle against teams of professional programmers.

Renee and Craig catch up with Henrik Kniberg at Scrum Australia 2014 where he tries coffee for the first time in ten years at the Paramount Coffee Project (the best coffee in Sydney according to Renee). Apart from getting his verdict on the brew, they also talk about: First time back in Australia in a long … Continue reading →