Podcast appearances and mentions of doc norton

In this episode of the Mob Mentality Show, we explore the Behavior Framework with the insightful Doc Norton, traversing the foundational behaviors that drive successful software development teams. Drawing from years of experience and real-world examples, Doc shares the principles and practices that have consistently helped teams deliver software products that are not only desirable but also viable and feasible. **Know the Problem You Are Solving** We kick off the discussion by tackling one of the most critical aspects of software development: understanding the problem you're trying to solve. Doc explains why it's not enough to have a manager dictate tasks and why teams must be aligned on the domain or specific set of problems they're addressing. We explore the difference between developers who are "builders" versus those who are "problem solvers" and discuss real-life scenarios where solving the root business problem either succeeded brilliantly or failed miserably. This section also delves into the concept of "Hubris Driven Development" and ties it into the importance of continuous validation before, during, and after development. **Make Your Work Visible** Next, we examine the significance of making your work visible. But what does that really mean? Doc challenges the notion of simply having a manager observe the development process and instead advocates for meaningful visibility that enhances awareness of flow, cycle time, and throughput. We discuss how much visibility is necessary and how to reduce the friction in data gathering by automating the process, ensuring that "updating status" doesn't become an additional burden on the team. **Favor Automation Over Documentation** Doc takes us through the benefits of favoring automation over documentation. From auto-generating status reports via code commits to AI, to using Behavior-Driven Development (BDD) to create historical Gantt Charts, we explore how automation can ease developer pain and streamline DevOps engineering. This approach not only saves time but also enhances accuracy and consistency in reporting. **Work Together** The conversation then shifts to the evolving meaning of "working together" in modern software development. Doc reflects on how teams used to function without strict roles or specialization and how the industry's shift towards hyper-specialization has created silos and Lean wastes. We share stories of Pair/Ensemble Programming, the impact of certificate mills on over-specialization, and the pros and cons of specialization in Agile teams. Doc also discusses the importance of credibility through collaboration rather than positional authority and shares examples of teams successfully filling roles collectively. **Create Simple Things in Small Steps** Finally, we emphasize the power of creating simple things in small steps. Doc highlights the importance of being aware of psychological WIP (Work in Progress) limits and shares a story of how reducing lead time by taking small, simple steps enabled early and accurate validation. We also discuss the dangers of overproduction and the challenges faced when big steps lead to troubleshooting nightmares, all while tying it back to being meticulous about composition. Don't miss out on this deep dive into the Behavior Framework with Doc Norton—packed with practical insights and actionable advice for anyone involved in software development. Video and Show Notes: https://youtu.be/MsMK0q_KUwU 

In this episode, Doc joined Shahin to talk about Beyond Velocity: Mastering Agile Coaching and Collaboration. The following have been topics of our conversation: Coaching, leadership, and software development Exploring different aspects of coaching, including technical, leadership, and agile coaching. Coaching helps clients achieve sense of accomplishment, while also providing accountability. Using velocity metrics in agile software development, with a focus on their limitations and potential misuse. ⁠ Velocity is often misused in Agile development despite being useful for high-performing teams. Challenges of measuring velocity in Agile development. A framework for management behavior, emphasizing connection, excellence, safety, autonomy, diversity, and leadership. Agile's evolution from values-based to practice-focused Emphasizing importance of collaboration, frequent releases, and automation. Check Elevate Change Training & Events (https://www.elevatechange.co/training-and-events/) Follow us Visit us at http://www.leanonagile.com Twitter: http://twitter.com/Elevate_Change LinkedIn: https://www.linkedin.com/company/ElevateChange

Bruce "Doc" Norton is a Vietnam veteran who served as a medic in the 3rd Force Recon Company, 1st Force Recon Company, and with the Navy. He has written 15 books on the Marine Corps history, and he retired as an oral historian with the Corps. Most recently, he has co-authored a book and play titled "Voices From Vietnam." Follow us: http://instagram.com/battlelinepodcast http://twitter.com/battlelinepod For 20% off your first order with Bubs Naturals go to https://www.bubsnaturals.com/?discount=BATTLELINE .. All purchases help to support the Glen Doherty Memorial Foundation For 15% off all Fort Scott Munitions ammo & gear go to http://fsm.com & use promo code: Battleline Photonis Defense is the global leader in night vision solutions providing more high-quality night vision capabilities than anyone. Hunters, shooters, boaters and outdoor enthusiasts rely on Photonis Defense systems to make their adventures safer and more successful. Visit http://photonisdefense.com for more information; or look for Photonis Defense product options from your night vision dealer. For full video of this episode subscribe to our Youtube page: https://www.youtube.com/@battlelinepodcast Learn more about your ad choices. Visit megaphone.fm/adchoices

Todd and Ryan think that tracking individual story points in Dev supervision is a major problem and a red flag. They believe it is a reckless metric that can impact people's behavior and pit teammates against each other. Ryan cites a book, "Escape Velocity" by Doc Norton, which argues that measuring individual velocity fails to give a complete picture and likely gives the wrong impression. It also hides things and can provoke behaviors that are against teamwork. Todd thinks tracking individual story points could lead to fights and is a massive issue that should be avoided.  ⏩ Join Ryan and Todd for a Scrum.org's course: https://buytickets.at/agileforhumansllc

Doc on LinkedIN: https://www.linkedin.com/in/docondev/ Doc on Twitter: @DocOnDev https://twitter.com/DocOnDev Link to by the book ESCAPE VELOCITY: https://www.amazon.com/Escape-Velocity-Better-Metrics-Agile-ebook/dp/B07RWRWKN6?ref_=ast_sto_dp A video of Doc summarizing some of the learns of ESCAPE VELOCITY: Escape Velocity - Better Metrics for Agile Teams | Doc Nortonwww.youtube.com › watch

Doc on LinkedIN: https://www.linkedin.com/in/docondev/ Doc on Twitter: @DocOnDev https://twitter.com/DocOnDev Link to by the book ESCAPE VELOCITY: https://www.amazon.com/Escape-Velocity-Better-Metrics-Agile-ebook/dp/B07RWRWKN6?ref_=ast_sto_dp A video of Doc summarizing some of the learns of ESCAPE VELOCITY: Escape Velocity - Better Metrics for Agile Teams | Doc Nortonwww.youtube.com › watch

Doc on LinkedIN: https://www.linkedin.com/in/docondev/ Doc on Twitter: @DocOnDev https://twitter.com/DocOnDev Link to by the book ESCAPE VELOCITY: https://www.amazon.com/Escape-Velocity-Better-Metrics-Agile-ebook/dp/B07RWRWKN6?ref_=ast_sto_dp A video of Doc summarizing some of the learns of ESCAPE VELOCITY: Escape Velocity - Better Metrics for Agile Teams | Doc Nortonwww.youtube.com › watch

Get Escape Velocity here: ttps://www.amazon.com/Escape-Velocity-Better-Metrics-Agile/dp/0578644835

Twenty years ago, before the word podcast existed, there was .NET Rocks! While at CodePaLOUsa in Louisville, Carl and Richard celebrated the publication of the first episode of .NET Rocks twenty years ago in August 2002. Doc Norton joined the conversation to talk about how agile has evolved and the challenges of making good software today. And a big thanks to all the listeners of the show - we couldn't have done it without you!

Twenty years ago, before the word podcast existed, there was .NET Rocks! While at CodePaLOUsa in Louisville, Carl and Richard celebrated the publication of the first episode of .NET Rocks twenty years ago in August 2002. Doc Norton joined the conversation to talk about how agile has evolved and the challenges of making good software today. And a big thanks to all the listeners of the show - we couldn't have done it without you!Support this podcast at — https://redcircle.com/net-rocks/donations

Twenty years ago, before the word podcast existed, there was .NET Rocks! While at CodePaLOUsa in Louisville, Carl and Richard celebrated the publication of the first episode of .NET Rocks twenty years ago in August 2002. Doc Norton joined the conversation to talk about how agile has evolved and the challenges of making good software today. And a big thanks to all the listeners of the show - we couldn't have done it without you!Support this podcast at — https://redcircle.com/net-rocks/donations

This week, our heroes discuss a recent Doc Norton tweet contemplating the definition of quality software. They dive right into what truly makes quality software and discuss when enough is enough. The post 62. Indicator of Quality vs Measure of Quality appeared first on Retro Time.

This week our heroes chat with Doc Norton, consultant, author, and speaker, about life before Agile, team culture, the state of agile today, how he really feels about best practices, and kiddie pools. The post 53. Great Scott!!! An interview with Doc Norton appeared first on Retro Time.

This week, Peter Maddison is our guest, and he is challenged with the heuristic “Measure what matters” from the Cloud Native Patterns repository (https://www.cnpatterns.org/strategy-risk-reduction/measure-what-matters). We discuss how to measure value and what techniques can be helpful to define metrics for teams creating and delivering software. We discuss how to expand towards measuring organisational performance and the impacts of different industry trends on our profession. He suggests starting measuring what matters: go and ask! Peter recommends: How to Measure Anything by Douglas W. Hubbard (https://www.goodreads.com/book/show/444653.How_to_Measure_Anything)  Escape Velocity by Doc Norton (https://www.goodreads.com/book/show/41046439-escape-velocity---better-metrics-for-agile-teams)  Measuring Outcomes... or how to get meaningful metrics with Gino Marckx (https://www.elevatechange.co/shareable/measuring-outcomes-or-how-to-get-meaningful-metrics-with-gino-marckx/)  Our Xodiac blog posts on metrics (https://xodiac.ca/blog/tags/metrics)  Focused Objectives GitHub repo - Lots of useful spreadsheets (https://github.com/FocusedObjective/FocusedObjective.Resources/tree/master/Spreadsheets)  Peter Maddison (@pgmaddison), coach and consultant with over 20 years of experience n helping organisations improve and thrive.

In this episode of Clean Coders, Chris Powers, author of Clean Code in the Browser for Clean Coders and VP of engineering for Thinkful, joins Chuck. They discuss how the solid principles of clean coding play out in an object-oriented language like JavaScript and the shift in the identity of a frontend developer in the past 15 years. Sponsors Cloud Academy | Get 50% off with promo code CODERS Audible.com CacheFly Host Charles Max Wood Guest Chris Powers Links Clean Code in the Browser Thinkful TypeScript Kent Beck’s 4 Principles of Simple Design The Technical Debt Trap by Doc Norton chrisjpowers.com Check out Chris’ “Clean Code In The Browser” video course

  Doc is Co-Founder at OnBelay, performing Organizational and Leadership coaching to companies for whom software is key.   Links https://docondev.com/ https://twitter.com/DocOnDev https://medium.com/@DocOnDev https://www.linkedin.com/in/docondev/   Resources Monte Carlo Forecasting and other tools from the crew over at Focused Objective Escape Velocity Book More about Technical Debt   "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved   × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

Chris Powers is the author of Clean Code in the Browser for Clean Coders and VP of engineering for Thinkful. He starts the show by talking about the path he sees people following when they come through Thinkful, which includes weekly meetings with a mentor in the industry. Every person that uses Thinkful comes out prepared for an entry-level position or apprenticeship. Chris talks about the importance of having different levels of skill and experience in a team. He and Chuck discuss the different points at which people start caring about clean code, which is all based on a desire to improve their methods of doing things. He talks about different ways to approach refactoring and how clean code and working code go together. They discuss how the solid principles of clean coding play out in an object-oriented language like JavaScript and the shift in the identity of a frontend developer in the past 15 years. For Chris, clean code is code that can be easily changed, and that is the ultimate goal. Clean code can be achieved through design principles and judgment. He and Chuck discuss how to know the right amount each to apply. Chris believes it comes down to solving problems you actually have and making the system legible. At Thinkful, they focus on quality, keeping your work in progress low, and delivering early and often. He talks about how to balance people’s desire to get more features and the need to slow down for business reasons and how to recognize friction between the two. Chris talks about how he takes the lead in writing quality software. The show concludes with Chris talking about some of his current projects.  Panelists Charles Max Wood Guest Chris Powers ____________________________ > "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Clean Code in the Browser Thinkful TypeScript Kent Beck's 4 Principles of Simple Design The Technical Debt Trap by Doc Norton chrisjpowers.com

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, recorded at the Agile India 2019 conference, Shane Hastie, Lead Editor for Culture & Methods, first spoke to Jeremy Kriegel about design innovation and then with Doc Norton about why Tuckman was wrong and how dynamic reteaming makes organisations more resilient. Why listen to this podcast: • Working to bring the design and agile communities together because there is a lot of synergy between and unfortunately there has been a lot of antagonism between practitioners in the two fields • Agile done well compliments UX and design, however some of the agile anti-patterns have burned UX designers • UX designers think holistically because customers experience products as complete things, they don’t experience them in pieces and if the product is built in pieces and those pieces don’t form a cohesive whole then the user experience is compromised • When developers watch someone struggle with their product there’s a dramatic change in the way teams approach their work More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2nQUi9h You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2nQUi9h

In this special announcement for the June Agile Online Meetup, we share about how you can hear from Doc Norton about “Escape Velocity: Better metrics for Agile teams” on June 25th at 2 PM! Register here --- Support this podcast: https://anchor.fm/tom-henricksen/support

SPaMCAST 520 features our interview with Doc Norton. We talked about his new book Escape Velocity, measurement, and why velocity isn’t generally a good measure for teams. By the time teams get to a point where story point velocity is consistent and predictable, they will have better tools that have fewer negative side effects. Doc’s Bio Doc Norton is passionate about working with teams to improve delivery and building great organizations. Once a dedicated code slinger, Doc has turned his energy toward helping teams, departments, and companies work better together in the pursuit of better software. Working with a wide range of companies such as Groupon, Nationwide Insurance, Belly, and JaTango, Doc has applied tenants of agile, lean, systems thinking, and servant leadership to develop highly effective cultures and drastically improve their ability to deliver valuable software and products. A Pluralsight Author, Clean Coders contributor, frequent blogger, international keynote speaker and coach, in his spare time, Doc has been working on his latest book, Escape Velocity: Better Metrics for Agile Teams. You can find his book on LeanPub at www.leanpub.com/EscapeVelocity Twitter: @DocOnDev Web: http://docondev.com/ Can you help keep the podcast growing? Here are some ideas: Tell a friend about the cast. Tweet or post about the cast.  Every mention helps. Review the podcast wherever you get the cast. Pitch a column to me. You are cool enough to be listening; you deserve to be heard. Sponsor an episode (text or call me to talk about the idea). Listen. Whether you do one or all six, being here is a big deal to me. Thank you! Re-Read Saturday News This week we continue on our journey through Bad Blood, Secrets and Lies in a Silicon Valley Startup by John Carreyrou (published by Alfred A. Knopf, 2018 – Buy a copy and read along!) Today we tackle a single chapter.  Chapter 6, titled Sunny, introduces Ramesh “Sunny” Balwani to the story. Sunny, Holmes’ live-in boyfriend (the stress on the live-in part is to shine a light on just how close Holmes was to Sunny), adds another layer of toxicity to the Theranos story. The toxicity feels extraordinary but is not that uncommon when teams break down.   Current Entry: Week 5 -- Sunny - https://bit.ly/2AZ5tRq Past Entries! Week 1 – Approach and Introduction – https://bit.ly/2J1pY2t    Week 2 -- A Purposeful Life and Gluebot - https://bit.ly/2RZANGh Week 3 -- Apple Envy, Goodbye East Paly and Childhood Neighbors - https://bit.ly/2zbOTeO Week 4 -- A Reflection -https://bit.ly/2RA6AfT Next SPaMCAST SPaMCAST 521 will feature our essay on user stories and legacy code.  A common question is how user stories can be developed for legacy code or for problems that crop up in production.  The implication is that creating user stories is too hard when dealing with legacy code changes or too slow when dealing with production problems.  User stories are a core tenet for most agile approaches. We will also have a visit from the Software Sensei, Kim Pries!  

SPaMCAST 519 features our essay on a code of ethics for agile coaches. A code of ethics is a compilation of ethical principles brought together into a framework. Most professions have a code of ethics that guide their behaviors, typically guided by an association that provides credentials. I think it is time to discuss a code of ethics for agile coaches. We also have a visit from Susan Parente, with her Not A Scrumdamentalist column.  Susan discusses how to become an agilist. It is not as easy as learning any individual set of methods and techniques. One of the places to find Susan is at S3 Technologies, LLC. I know I promised a visit from Jon M. Quigley, but I had a minor problem with the drive and did not get the column into production soon enough to make the deadline.   Interested in supporting the podcast? Here are some ideas: Tell a friend (or better yet listen to the podcast with them) about the cast. Tweet or post about the cast.  Every mention helps. Review the podcast wherever you get the cast. Pitch a column to me. You are cool enough to be listening, you deserve to be heard. Sponsor an episode (text or call me to talk about the idea - tcagley@tomcagley.com). Listen. Whether you do one or all six, being there is a big deal to me.  Thank you! Re-Read Saturday News This week we take a slight detour in our journey through Bad Blood, Secrets and Lies in a Silicon Valley Startup by John Carreyrou (published by Alfred A. Knopf, 2018 – Buy a copy and read along!) As we have noted before, the book is at heart a cautionary tale; however, it is easy to pass the shenanigans (in private I might use stronger language) as confined to the boardroom, and therefore not something that can happen inside the boundaries of an agile team or in a department.  Ahhhh, think again. To establish the basis for this brief respite we published a review of some of the common attributes of toxic organizations and toxic leaders. It would be easy to go through both of the lists and a find points in the first six chapters and tick the attributes off almost like you were watching a slow(ish)-motion train wreck. Week 1 – Approach and Introduction – https://bit.ly/2J1pY2t    Week 2 -- A Purposeful Life and Gluebot - https://bit.ly/2RZANGh Week 3 -- Apple Envy, Goodbye East Paly and Childhood Neighbors - https://bit.ly/2zbOTeO Week 4 -- A Reflection -https://bit.ly/2RA6AfT Next SPaMCAST SPaMCAST 520 will feature our interview with Doc Norton. We talked about measurement and why velocity isn’t generally a good measure for teams.

Failure Management and Response with Nickolas Means TableXI is offering training for developers and product teams! For more info, email workshops@tablexi.com. Guest Nickolas Means (https://twitter.com/nmeans) | nickol.as (http://nickol.as/) | VP of Engineering at MuveHealth (http://www.muvehealth.com/) Summary How can you learn from an engineering team's failure? Can you take the examples of how others have dealt with engineering problems to improve your team's day-to-day operations. Our guest is Nickolas Means, a software manager at Muve Health, who is fascinated by engineering failures. We talk about what you can learn from studying disasters, how to create a company culture in calm times that will works smoothly in stressful times, and how a successful engineering team communicates using stories and how they handle mistakes. Along the way, we talk about the recent incident at the Seattle Airport, the CitiCorp building in Manhattan, Three Mile Island and other engineering and team missteps. We have, I hope, a successful show about failure. Notes 02:12 - Learning From Engineering Team Failure Seconds From Disaster (https://en.wikipedia.org/wiki/Seconds_From_Disaster) 04:49 - Self-Reporting of Near Accidents How a change in hospital policy saved thousands of lives (https://www.vox.com/2017/10/23/16387300/hospital-policy-saved-thousands-lives-central-line-infection) 06:54 - First Story/Second Story RailsConf 2018: Who Destroyed Three Mile Island? by Nickolas Means (https://www.youtube.com/watch?v=YBRiffheLXE) The Field Guide to Understanding Human Error 2nd edition Edition (https://www.amazon.com/Field-Guide-Understanding-Human-Error/dp/0754648257) 08:46 - How the Airline Worker Who Stole a Plane in Seattle Exposed a Security Risk (http://time.com/5368847/airline-security-risks/) 13:44 - The Design Flaw That Almost Wiped Out an NYC Skyscraper (http://www.slate.com/blogs/the_eye/2014/04/17/the_citicorp_tower_design_flaw_that_could_have_wiped_out_the_skyscraper.html) RubyConf 2016 - The Building Built on Stilts by Nickolas Means (https://www.youtube.com/watch?v=-ES1wlV-8lU) 99% Invisible Podcast: Structural Integrity (https://99percentinvisible.org/episode/structural-integrity-2/) 16:33 - Focusing on Blamelessness and Building a Learning Culture on a Team 21:04 - Overpaging Engineering Teams Charity Majors on overpaging (https://twitter.com/mipsytipsy/status/1028131196826349568) 25:21 - Story Communication Jeff Bezos Banned PowerPoint in Meetings. His Replacement Is Brilliant (https://www.inc.com/carmine-gallo/jeff-bezos-bans-powerpoint-in-meetings-his-replacement-is-brilliant.html) 29:44 - Helping Team Members Make Better Decisions The Boring Software Manifesto (http://www.noelrappin.com/railsrx/2016/5/26/the-boring-software-manifesto) Dan McKinley: Choose Boring Technology (http://mcfunley.com/choose-boring-technology) 34:29 - How to Behave When Things Go Wrong The Johnson & Johnson Tylenol Crisis (https://www.ou.edu/deptcomm/dodjcc/groups/02C2/Johnson%20&%20Johnson.htm) Related Episodes Developers from the Perspective of Product Owners (http://www.techdoneright.io/29) The Social Responsibility of Coding with Liz Abinante (http://www.techdoneright.io/25) Agile Teams and Escaping Velocity with Doc Norton and Claire Podulka (http://www.techdoneright.io/15) Special Guest: Nickolas Means.

Diverse Agile Teams with Marlena Compton, Betsy Haibel, and Jennifer Tu TableXI is now offering training for developers and products teams! For more info, email workshops@tablexi.com. Get your FREE career growth strategy information and techniques! (https://stickynote.game) Guests Marlena Compton (https://twitter.com/marlenac): Organizer of PearConf (https://pearconf.splashthat.com/). Betsy Haibel (https://twitter.com/betsythemuffin): CTO at Cohere (https://www.wecohere.com/). Jennifer Tu (https://twitter.com/jtu): Co-Founder at Cohere (https://www.wecohere.com/). Summary How do common Agile practices like pair programming and retrospectives work when you have diverse teams? How can you make sure that underrepresented team members have their voices heard, and how does doing so improve the way that your team delivers software? Besty Haibel, Jennifer Tu, and Marlena Compton discuss ways in which Agile practices can better serve your team in the real world. For more discussion, be sure to check out PearConf (https://pearconf.splashthat.com/). Notes 02:05 - Pairing and Agile Development on Diverse Teams Betsy on Twitter (https://twitter.com/betsythemuffin/status/990568867683500034) 04:31 - Implicit Agreement, Teaching Vs Exploring, and Power Differentials in Pairing Ruby DCamp (http://rubydcamp.org) Code Retreat (https://www.coderetreat.org) Allison McMillan (https://twitter.com/allie_p) 08:52 - Understanding and Improving Team Dynamics: Building a Library of Smells Pairing With Privilege (https://pearconf.splashthat.com) Ping Pong Pairing (http://wiki.c2.com/?PairProgrammingPingPongPattern) Troll Pairing Table XI Pair-A-Palooza Station (https://uploads.fireside.fm/images/e/e2f17a1d-4992-4c1c-b414-0780dcd58bc3/SAElUnop.jpg) 17:57 - Good Agile Pair Programming Techniques + Retrospective Roles Running your unconference discussions effectively: AdaCamp session role cards (https://adainitiative.org/2013/10/02/running-your-unconference-discussions-effectively-adacamp-session-role-cards/) 22:14 - Making People Comfortable When Speaking Up and Making Agile Healthier Dot-Voting (https://en.wikipedia.org/wiki/Dot-voting) 32:30 - Agile As An Institution Agile Manifesto (http://agilemanifesto.org) 38:34 - Backing Away From The Idea of Perfection 42:42 - PearConf (https://pearconf.splashthat.com/) Details 43:55 - Bonus Conversation: The Practices Not Being the Manifesto The Winter Getaway That Turned The Software World Upside down by Caroline Mimbs Nyce (https://www.theatlantic.com/technology/archive/2017/12/agile-manifesto-a-history/547715/) Related Episodes Nonviolent Conversation with Nadia Odunayo (http://www.techdoneright.io/22) How Set Design Can Inform Software Architecture With Betsy Haibel (http://www.techdoneright.io/21) Agile Teams and Escaping Velocity with Doc Norton and Claire Podulka (http://www.techdoneright.io/15) Special Guests: Betsy Haibel, Jennifer Tu, and Marlena Compton.

Doc Norton talks about the experimentation mindset. This episode is sponsored by Smartsheet. Show Notes: Slides from Doc’s presentation on the experimentation mindset XP = eXtreme Programming Other methodologies that fall into the "agile" category: Scrum, Lean Kent Beck, Ron Jeffries, and Ward Cunningham were all mentioned. They are all signers of the Agile Manifesto. Chris Argyris was mentioned in regards to single-loop and double-loop learning Book: Escape Velocity by Doc Norton - it has increased in price since the recording. It will now set you back at least 5 entire dollars. Supplemental links from Doc: CTO2 DocOnDev Collaboration Contracts Refactoring Code Smells Video: Experimentation Mindset Mob Programming Learning through experimentation PDF: How Organizations Learn From Harvard Business Review: Collective Genius Argyris: Teaching Smart People how to Learn (and PDF version) A/B Testing and the Experimentation Culture Enlightened Experimentation Smart Business Experiments Evidence Based Management link:http://www.edbatista.com/2008/05/double-loop.html[Ed Batista blog post on double-loop learning Lean Change Book: Scaling Up Excellence Experiential Learning Doc Norton is on Twitter. Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Music is by Joe Ferg, check out more music on JoeFerg.com!

Guest: Doc Norton @docondev Full show notes are at https://developeronfire.com/podcast/episode-337-doc-norton-builders-and-problem-solvers

In this ver. @csell5 talks with @docondev about software teams, company culture and it’s effect on delivery. Doc Norton is a software delivery professional working to make the world of software development a better place. His experience covers a wide range of development topics. Doc declares expertise in no single language or methodology and is immediately suspicious of anyone who declares such expertise. Doc writes regularly on topics related to software delivery, management, and leadership. You can find his musings at www.docondev.com, www.wearecto2.com/blog, and www.leanpub.com/escapevelocity A frequent and well rated international speaker, Doc is passionate about helping others become better developers, working with teams to improve delivery, and building great organizations. In his role at CTO2, Doc is provided opportunities to realize his passion every day. http://www.docondev.com/ http://twitter.com/docondev

Developers from the Perspective of Product Owners Follow us on Twitter! @techdoneright (https://twitter.com/tech_done_right) Also, please leave us a review on Apple Podcasts (https://itunes.apple.com/us/podcast/tech-done-right/id1195695341?mt=2)! The newsletter is back! For more information on upcoming episodes, sign up at http://techdoneright.io/newsletter (http://techdoneright.io/newsletter) Guests Cat de Merode (https://www.linkedin.com/in/cat-de-merode/): VP of Product at PeaPod (https://www.peapod.com/) Matt McNamara (https://www.linkedin.com/in/matthewbmcnamara/): Product Manager Summary Have you ever wondered what it's like to work with a software team? Perhaps you are a developer wondering what you seem like from the outside? Or maybe you are starting to work with a software team and you want to know what to expect? Cat de Merode and Matt McNamara join the show to talk about their experiences as product owners interacting with developer teams. We'll talk about what developers can do to build trust, how to work with product owners on estimates and to talk about technical topics. And they'll say what the most important things developers should know about working with their product owners. Notes 02:43 - Dealing with Developer Teams 04:00 - In-house vs External Developers 05:33 - Helping Developers Understand Product Owner Motivation and Goals and Getting on the Same Page 11:18 - How can developers build trust? 12:29 - Explaining Architectural Decisions to Product Owners 14:29 - Does team size make a difference? 16:30 - Good Company Culture Behavior 18:44 - Estimation and Complexity - More on velocity: Agile Teams and Escaping Velocity with Doc Norton and Claire Podulka (http://www.techdoneright.io/15) 28:40 - Curation of Features 34:15 - What should developers know about working with product owners? Related Episodes Agile Teams and Escaping Velocity with Doc Norton and Claire Podulka (http://www.techdoneright.io/15) From Idea To Company With Maci Peterson and Alicia Drucker (http://www.techdoneright.io/14) Managing For Career Development with Claire Lew and Dan Hodos (http://www.techdoneright.io/12) Special Guests: Cat de Merode and Matt McNamara.

Summary Doc Norton tells me why measuring agile velocity is a bad idea and what to do instead. Details Who he is, what he does. "Escape Velocity", why he wrote a book on agile metrics. What velocity is, rate of delivering value to customer, "it is useless", estimates are "bunk". "The business" pushes velocity based estimates. Lack of trust throughout organization. Can we really reduce a complex problem down to a simple number. Anti patterns: more velocity, cross team velocity comparisons, estimating with time, measuring individual velocity. Side effects of metrics. Variable velocity. What should we measure, cycle time and lead time, fixing bottle necks, code quality, team joy. Where does dev ops come in. How to find Doc's book. Upcoming conferences.

At the Agile Professional Learning Network - Chicago Chapter’s first Conference, I caught up with Doc Norton. He spoke about the Host Leadership model and its role-based examples, instead of character based traits of Servant Leadership. Listen as Doc explains several of the roles that anyone can take on in Host Leadership. Doc also has a book on Lean Pub right now, , where he explores more useful metrics than Velocity.

Agile Teams and Escaping Velocity with Doc Norton and Claire Podulka Follow us on Twitter! @techdoneright (https://twitter.com/tech_done_right), leave us a review on iTunes, and please sign up for our newsletter (http://www.techdoneright.io/newsletter)! Guests Doc Norton (https://twitter.com/DocOnDev): Co-Founder and CEO of CTO2 (http://www.wearecto2.com). Claire Podulka (https://twitter.com/cpodulka): Project Manager at Table XI (http://www.tablexi.com/). Summary How can you tell whether an agile software team is successful? Many teams use a single measure: velocity. Doc Norton, author of Escape Velocity, and Claire Podulka join the show to discuss why velocity is not a useful measure: it doesn't explain the problems with an unsuccessful team, and successful teams probably don't need it. We discuss the problems with velocity, what to use instead, and get on soapboxes for our least favorite agile anti-patterns. Notes 02:48 - Metrics for Agile Teams: Velocity - Escape Velocity: Better Metrics for Scrum Teams by Doc Norton (https://leanpub.com/escapevelocity) - Trust Driven Development by Noel Rappin (https://leanpub.com/trustdrivendevelopment) 06:15 - Using Velocity 07:49 - Problems When Relying Solely on Velocity and Estimation 12:35 - Theory of Flow 15:17 - Body Weight Analogy 17:17 - Assessing Team Health 18:37 - Team Temperature (Joy) 21:51 - Lead Time and Cycle Time 30:04 - Managing Estimation and Team Metrics When Teams and Scope Change 33:17 - Using Metrics: Large Organizations vs Small Organizations 39:18 - Breaking Down Team Velocity at the Individual Level Special Guests: Claire Podulka and Doc Norton.

In his Agile2016 session "The Technical Debt Trap", Doc Norton takes all the way back to the metaphor that started it all. Doc says Ward Cunningham coined the term "technical debt" not as shorthand for lousy code but for clean code implemented with your current understanding of the requirements and covered with tests. In short, "technical debt" isn't code that you intend to clean up later: it's clean code created when the dev's knowledge is impartial that the dev can then easily refactor when they learn more about the problem. The danger with the current meaning of technical debt is that the term is benign enough that we don't give it enough attention. "In a great extent, we're using the metaphor to abdicate our own professional responsibility..." Things that teams can start doing now: create debt stories and discuss with the business what the real value of that debt is. John Esposito, Editor-in-Chief of DZone, SolutionsIQ partner, hosts at Agile2016 in Atlanta, GA. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thoughtleaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter  Like: http://bit.ly/SIQFacebook

Michael “Doc” Norton (@docondev) joined me (@RyanRipley) to discuss Organizational Change, Mindset Shifts, and Product Centric Organizations. [featured-image single_newwindow=”false”]Doc Norton Presenting at The Path to Agility Conference – Copyright COHAA[/featured-image] Doc is passionate about working with teams to improve delivery and building great organizations. Working with a wide range of companies such as Groupon, Nationwide Insurance, Belly, and many others, Doc has applied tenants of agile, lean, systems thinking, and servant leadership to develop highly effective cultures and drastically improve their ability to deliver valuable software and products. In this episode you'll discover: The building blocks of a knowledge based culture How mindset shift at the leadership level happen Why product-centric is the new hierarchy What to do tomorrow to help deliver more value to your organization Links from the show: CTO2 – Doc’s Consulting Company Agile Fluency Model Doc’s presentations available online [callout]This book will help you implement successful change and bypass change resistance by co-creating change. The book will do that through examples of how innovative practices can dramatically improve the success of change programs. These practices combine ideas from the Agile, Lean Startup, change management, organizational development and psychology communities. This book will change how you think about change Click here to purchase on Amazon.[/callout] [reminder]What do you do when you don’t know what to do? Please share your ideas below.[/reminder] Want to hear another podcast about the agile mindset? — Listen to my conversation with Zach Bonaker, Diane Zajac-Woodie, and Amitai Schlair on episode 39. We discuss growing an agile practice and how coaches help create the environments where agile ideas can flourish. One tiny favor.  — Please take 30 seconds now and leave a review on iTunes. This helps others learn about the show and grows our audience. It will help the show tremendously, including my ability to bring on more great guests for all of us to learn from. Thanks! This podcast is brought to you by Agile Dev East. Techwell’s Agile Dev East is *the* premier event that covers the latest advances in the agile community. Agile for Humans listeners can use the code AFH16 to receive $200 off their conference registration fee. Check out the entire program at adceast.techwell.com. You’ll notice that I’m speaking there this year. Attendees will have a chance to see my Business of Agile presentation, along with my half day session on advanced scrum topics called Scrum: Answering the Tough Questions. I hope to see many Agile for Humans listeners in Orlando, Florida – November 13th – 18th for this great event. The post AFH 046: Agile Organizational Change with Doc Norton [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Hello Tech People. Today I’m joined by Doc Norton. Doc Norton is the CEO of CTO2 and is an authority in the technical space. CTO2 utilizes systems thinking, organizational psychology, and complexity theory to help you transform your entire organization. From recruiting and talent development, to engineering and product development, to sales and marketing. In my time with Doc we discuss his background, Organizational Agility, what a proper engineering team looks like, hiring, Doc’s theory of “Jungle gyms and not ladders, organizational structure, one-on-one meetings and the “Shock and Awe technique”. We are honored to have such an interesting person on our show this week.

An outspoken critic of the way I.T. companies organize their projects, Doc Norton will be a speaker at Emerging Technologies for the Enterprise. His talk is called Agile Metrics: Velocity is NOT the Goal. His company, CTO2, helps companies implement Agile development practices. Today, Ken and Doc discuss some of Doc’s most recent opinion pieces ... Read More The post TechCast #95 – Doc Norton on Agile Metrics – “Velocity is Not the Goal” appeared first on Chariot Solutions.

Introducing Matt Beam! Matt will become the show's new co-host and technical editor.  Don't worry, you'll still get to hear me inject more than a few um's and stutters :)  But, you will also get Matt's level-headed observations and ideas! In this episode, we talk about things we are seeing in the Chicago Agile space as far as Agile implementations, attitudes, practices, and how we've adapted to them. We talk a little about Doc Norton's presentation at Agile Day Chicago 2015.  Doc has a great new take on the Shu - Ha - Ri  maturity model. Rick gives a little detail about an experiment he's looking into with crossing the CSM training class and young students.  This gives way to a great discussion on training/educating students.  

Guest: Doc Norton @docondev Full show notes are at https://developeronfire.com/podcast/episode-033-michael-doc-norton-customer-value-and-great-organizations

While at NDC, Carl and Richard talk to Michael 'Doc' Norton about his experiences figuring out the right metrics to measure in productivity of a development team. The discussion focuses in on the key issue - that velocity is a dangerous metric. As Doc explains, pushing developers to do more features per sprint creates serious problems. So what measures make sense? Great thinking around what makes people productive, what impairs productivity, and how to do the right things the right way.Support this podcast at — https://redcircle.com/net-rocks/donations

While at NDC, Carl and Richard talk to Michael 'Doc' Norton about his experiences figuring out the right metrics to measure in productivity of a development team. The discussion focuses in on the key issue - that velocity is a dangerous metric. As Doc explains, pushing developers to do more features per sprint creates serious problems. So what measures make sense? Great thinking around what makes people productive, what impairs productivity, and how to do the right things the right way.Support this podcast at — https://redcircle.com/net-rocks/donations

Carl and Richard talk to Michael Doc Norton about how developers can grow their career. The conversation dives deep into techniques and approaches to practice in development, comparing it to music and katas. The reference sharpen the saw comes from Stephen Covey, and focuses on the idea of practice independent of work.Support this podcast at — https://redcircle.com/net-rocks/donations