Podcast appearances and mentions of david hussman

In this encore episode of The Schmidt List from 2018, I interview David Hussman, founder of DevJam, speaker, author, and software development expert. As I look back on my past 200+ episodes, I can't help but feel a sense of joy and nostalgia. Remastering some of my favorite episodes has been an absolute pleasure, and I'm excited to share them with all of you. It's fascinating to see how much has remained the same in software development since this episode (No.016) was published in 2018. It's a great reminder of the timeless principles that guide our work.During our discussion, we discussed the changes in software development that have taken place in the last 20 years and what direction it is going towards, specifically regarding the transition from project-centered to product-centered development. David provided valuable advice on coaching teams to adopt a product-focused approach, especially in larger companies. Highlights:Analyzing and presenting data visually can help teams discover new trends. This approach makes it easier to spot trends and can inspire fresh ideas.Value-aligning teams with customer impact and encouraging developers to interact with customers to understand their needs better.Don't rely solely on technological advances or the competition's roadmap for product improvement ideas.To optimize productivity and minimize handoffs prioritize teamwork.Executives should encourage knowledge-sharing and take responsibility for desired behavior.Executives should encourage and motivate teams to communicate.Communication is vital in software development, especially in large organizations with siloed teams.Customer journey mapping and impact-driven development can help understand the effect of features and investments.According to David, as a technology or design leader, admitting mistakes is the most crucial characteristic. It's essential to be transparent and accountable for your actions; this willingness to take responsibility can inspire trust and respect from your team. So, feel free to own up to your mistakes and work towards finding solutions. It's all part of being a strong and effective leader.I feel incredibly fortunate to have crossed paths with David, as I gained a great deal of knowledge from him in the short time I spent with him, and I will always cherish the lessons he imparted to me.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website. In this episode, we talk about the PO’s role inside the team, and how we can help Product Owners focus on value. The Great Product Owner: The PO who focuses on team success The Product Owner in Scrum is a very difficult role, maybe even a super-human role. Unless we start thinking about the role as part of the success of the team, rather than the only responsible for the product. Great Product Owners focus on helping the team succeed, and learn to say “no” to everything that gets in the way, even if that’s a feature they “love”. The Bad Product Owner: The PO that focuses on the “how” instead of the “why”  When a PO focuses on the “how”, they miss their ability to communicate with the team in a way that describes what value is. The Value should be the center of the PO’s attention, but when the PO starts telling the team “how” something should be developed, they lose time outside the “value conversation”. In this episode, we explore ways to help the PO focus on, and define value for the team. In this segment, we refer to an insight by David Hussman called “Dude's Law” (Value = Why? / How?). Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.   About Charles Rodriguez Charles has been working in software development for 16+ years with roles ranging from a database developer to manager to agile coach all in an effort to 'try to make things better' for future generations joining the IT industry. You can link with Charles Rodriguez on LinkedIn and connect with Charles Rodriguez on Twitter.

The Agile community recently lost its friend and one of its most inspirational members in David Hussman. Craig and Tony were privileged to speak to him in one of his last interviews at YOW! Conference in Brisbane. David Hussman’s YOW! 2017 talk “Learning in Product: How Wrong are You Ready to Be?” “Extreme Programming Explained” is … Continue reading →

In this episode we (01:07) A few words on the passing of David Hussman, (03:14) Agile Narrative Project: How do we build physiological safety in companies, (20:11) What is the benefit of waiting until Sprint Planning to task out a story instead of doing it in a Grooming session when the team is larger, (26:40) What are useful metrics to show leadership, Leadership wants to see metrics. (32:18) What is a best practice around Agile release planning, and (43:16) Can agile adoption on one team be different from another team.Support the show (https://www.agilealliance.org/membership-pricing/)

From being a recording engineer at Prince's Paisley Park studios, to playing with the big-hair metal band Slave Raider to founding a successful Agile coaching business called Dev Jam, David Hussman has been forging his way one untraditional step at a time.  Our interview with David quickly pegged him as the 'accidental behavioral scientist' and that played well throughout the discussion. We talked about chaos monkeys, constructionism, how important it is for Neil Young to know G-C-D chords (and to know what to do with them) and to do things that focus our attention on things that make people smile.  Unlike pies and cakes, software development is never done. The behavioral aspects of how people interact with software - from the photo app on your phone to the way GPS could alert you gas stations nearby when you're low on fuel (connecting to your car's fuel system) or eateries (connecting your journey to the time of day) - need to be better constructed for the world we live in. Hendrix vs. Van Halen - who would have thought it was such a difficult question. Listen in and find out. And check out David on Twitter at @davidhussman and let him know that Hendrix is the only correct answer.  

Guest: David Hussman @davidhussman Full show notes are at https://developeronfire.com/podcast/episode-315-david-hussman-from-success-to-fulfillment

Episode 20 of the Modern Agile Show features an interview with David Hussman, veteran agile leader, product geek and founder/CEO of DevJam. We discuss his talk, "Learning in Product: How Wrong are You Ready to Be?" We reminisce about Extreme Programming and the nature of the early community that formed around it. We discuss how to handle known vs. unknown software work, how we change the way we work when moving from complicated to complex efforts, as well as what David's been up to in the Chaos community.

On today’s show, I’m talking to David Hussman, founder of DevJam, speaker, author and all around brilliant individual.We discuss how software development has been under an enormous transformation over the past two decades and where it’s headed. 

On this edition of The Guardian Podcast with Ryn Melberg, David Hussman joins Ryn to discuss all things chaos, including "Chaos Day". David is well known for his web site and location in Minneapolis both called DevJam. David is a busy man with an extremely active mind and Ryn discusses some of his most recent breakthroughs on the show. To learn more about this and other topics go to www.rynmelberg.com.

In this episode, I spoke with David Hussman about products, pricing and experiments. David is an agile authority, thought leader and frequent speaker in the Agile Community. He received the Gordon Pask award from the Agile Alliance and as a musician makes great associations between his favorite pastime and agile products. David founded and shaped the company DevJam which he recently sold. In this episode, David makes references to product agility, which I invite you to give a visit for further research.

Jochen (Joe) Krebs speaks with David Hussman about products, pricing and experiments.

In this edition of the Guardian podcast we will be talking with David Hussman. David is someone I know and worked with before and am very happy he is with us. Among other things, David now leads a company he founded called DevJam (http://devjam.com). But he is also involved with another effort called Product Agility, and founded Agile Twin Cities. The web site for that is www.agiletwincities.org. And like always, there is more information about the Guardian Podcast along with articles and other interesting and free material on my web site which is www.rynmelberg.com.

A wonderful discussion with David Hussman. David and Brian look back at what all we've learned in XP, TDD, and other Agile methodologies, where things have gone awry, how to bring the value back, and where testing fits into all of this. How to build the wrong thing faster Agile vs Agility Product vs Process Where testing fits into software development practices. "Integration tests, there's a name that needs to be refactored desperately." Integration tests are "story tests". They tell the story of the product. XP and TDD and the relationship with tests To test for design, use microtests, xUnit style. User Advocy tests are often lacking, but are needed to learn about the product. "I just keep writing tests until I'm not scared anymore." - Kent Beck Dude's Law: Value = Why/How People often focus so much on the how that they forget about why they are doing something. Subcutaneous Tests "The hardest part of programming is thinking." Refactoring vs Repaving Agility means being able to quickly change direction During experimentation and learning, what matters isn't how much you got done, but how much you learn. "The best way to get automation is to make developers do manual tests." Special Guest: David Hussman.

  Where should Product Owners look to engage with others in Product Discovery? The notion of not “knowing” what should be done can be uncomfortable or straight scary to a lot of people. However, the notion of learning more about our product and how our users can, and are already benefiting from it is a great topic to explore. In this episode, David Hussman joins the show to talk about his riffs on how great product teams make meaningful impacts and explore ideas.     Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - Looking for a co-host David Hussman - http://devjam.com/   @davidhussman David Hussman - Products over Process David Hussman - Effective Product Discovery and Dude’s Law Henrik - Agile: Where are we at? Kevin Eikenberry - How to Respond to “We’ve Tried That Before”  

Amos King interviews John Krewson and David Hussman following their presentations at Agile Dev East

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, Shane Hastie, InfoQ Lead Editor for Culture & Methods, talks to David Hussman, founder and “The Dude” from DevJam and CardBoard It!, a tool for story mapping. Why listen to this podcast: - Put value first – it’s not about building more stuff but making sure we build the right thing for the right people - Dude’s Law: Value = Why / How - Identify the impact that a product needs to make on someone’s life - Constrain complexity using thin slicing and “minimum viable learning” - Have an intentional discovery-delivery cadence to speed up the learning cycles – design and delivery sprints tightly coupled - “Done” is not enough – value is only delivered when the item has been validated with real customers - Validation can happen in both discovery and delivery Notes and links can be found on InfoQ: http://bit.ly/2eegjYf - 1m 41s Introducing “Dude’s Law”: Value = Why divided by How. - 3m 05s Think about the intent, not the process, when looking at product development. - 3m 17s Focus on Product over Process and finding the intent, identifying the impact that the product will have. - 3m 30s Large “transformations” are often never-ending and not very successful; successful products come from finding the thing that impacts someone – that makes someone’s life better. More on this: Quick scan our curated show notes on InfoQ. http://bit.ly/2eegjYf You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/2cMnjfW

The post MBA081: User Story Mapping with David Hussman appeared first on Mastering Business Analysis.

Joe Krebs speaks with David Hussman about Story Mapping, discovery techniques and agile product management

Jochen (Joe) Krebs speaks with David Hussman about story mapping and customer journeys and how they relate to agile processes for example Scrum. Within DevJam, David created a tool called cardboardit.com that helps user experience designer, producers and product managers alike map out journeys. He builds the link to Lean UX as well as to development teams.

In this episode, Bob and Josh sit down with David Hussman ( @davidhussman (https://twitter.com/davidhussman) ), of DevJam Studios, at the Agile Development Practices and Better Softare Conference in Las Vegas.  David brings great insight to the podcast and helps us cover quite a few topics, including whether or not Agile has "jumped the shark" and shares a few "pithy comments" (as requested from Bob) about how individuals and teams can get better. Support this podcast

David Hussman and Tor Stenstad discuss about their experience working together on the transition of GMAC-RFC to an agile delivery approach.  “Better Faster Cheaper, Everyday…It’s a competitive advantage.?Customizing Agile for a large implementation.-bob