Podcast appearances and mentions of allen holub

Luis Garcia: Forecast Over Estimation, How To Transform Your Approach To Project Management, NoEstimates Unplugged Week This is one of a series of episodes where Product Owners explain how they used, and benefited from #NoEstimates in their work with teams.  To know more about #NoEstimates, sign-up to get the first 3 chapters of the book here. Introduction to #NoEstimates Luis Garcia, transitioning from estimation discomfort to a #NoEstimates approach as a product owner, discovered its benefits after attending a workshop by Woody Zuill. Faced with the challenges of hard commitments in government projects, he sought to shift focus from when to what and why in project discussions. A Transformative Project Example  Implementing #NoEstimates in a kanban team, Luis emphasized work breakdown and comfortable task sizing. This method facilitated stakeholder communication, improved expectation management, and enabled precise progress measurement through metrics like cycle time and using techniques like Monte Carlo forecasting. Overcoming Implementation Challenges  When Luis tried to introduce #NoEstimates, he originally faced skepticism, misconceptions about planning, and stakeholder resistance. In those cases, Luis advises focusing on forecasting based on available data, ensuring team stability, and managing expectations effectively. And focusing on progress transparency, instead of trying to change people's minds. Strategic Stakeholder Management  Successfully integrating #NoEstimates involved fostering team accountability and ownership over the refinement process, thereby enhancing stakeholder dialogue and planning efficiency. For example, Luis shares that #NoEstimates shifted the team's focus to identifying and preparing the most valuable tasks, leveraging data for all planning and prioritization decisions. This focus helped to keep stakeholders informed, and improved transparency. Measuring Success and Communicating Progress  Without traditional estimates, Luis's team adopted a probabilistic approach to measure and communicate progress, supported by insights from the book "Thinking in Bets" by Annie Duke. When it came to adopting a different way to measure and communicate progress, practicality was key; even simple tools like Excel were effective for data management in the #NoEstimates process, emphasizing simplicity and scalability. Advice for #NoEstimates Adopters  Luis recommends low-change experimentation with #NoEstimates to experience its benefits firsthand and stresses the importance of informative discussions over rigid planning. Resource Recommendation  For those considering #NoEstimates, Luis suggests starting with the "NoEstimates" book and following thought leaders like Vasco Duarte, Woody Zuill, and Allen Holub on social media. About Luis Garcia Luis is a Program Manager at Formula.Monks, specializes in developing impactful digital products. Luis has over 10 years of experience and several Agile certifications, he adeptly applies Agile frameworks to meet client needs. His background includes a Master's in Computer Engineering and an Executive MBA. He is also fluent in English, Spanish, and French, he values diverse work environments and continuous learning. You can link with Luis Garcia on LinkedIn.

Allen Holub is a computer scientist, author, educator, and consultant. He has written extensively on the C, C++, and Java programming languages, and on object-oriented programming in general. Allen is well known for his uncompromising view of agile adoption and in particular the assumption that Scrum is the only agile approach. In the past he has said “Jira is the work of the devil” and “Agile has become a priesthood”. Allen is engagingly forthright in his views. In this episode of The Engineering Room, Dave Farley discusses with Allen the prevailing culture, and often anti-patterns, that lead to problems in agile adoption, and between them, they explore some of the ideas that really matter in becoming genuinely agile, as a practical way to more effective software development.xxIf you want to learn Continuous Delivery and DevOps skills, check out Dave Farley's courses ➡️ https://bit.ly/DFTraining

Nowadays, Agile methodologies are applied and well-known all over the software development industry. But are they actually implemented as they should? According to Software Architect and author Allen Holub, while Agile is the way to go, it does not mix well with other practices just as widespread in the industry—chiefly, estimates and project-based development.Allen Holub discusses with us his idea of #NoEstimates and shares his views on what software development should look like.Listen to the full episode or read the transcript at https://semaphoreci.com/blog/allen-holub-no-estimates Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

Allen Holub is a software development and agile consultant who wants to help you build better software and build software better. He's also not shy when it comes to telling the world what he thinks about product development via Twitter. Here are some of Allen's spicy takes: Making true organisational change requires C-level buy-in It's easy to get hired by the engineering team to help them learn how to make sausages better but the better goal is to work out if you want to make sausages, and you need top-level buy in for this There are too many people walking on eggshells on Twitter You should be able to share your version of the truth in an open, direct way. If people don't like it, they can listen to someone else! Context is important, but it's not ivory tower thinking to try to change a system. Empowering people to be agile doesn't mean leaving them to it Removing organisational blockers and waterfall thinking is important, but you can't just leave them to it and not support them. They need support to become a learning organisation. Scrum is, at best, mostly harmless, but only in good teams You don't need backlogs, you don't need scrum masters, you don't need Sprints. You don't need any of it. Scrum was just a way to make agile acceptable to bureaucratic micromanagers. But all frameworks fly against agile thinking. Product managers do essential work that developers won't do if left to their own devices, but.. It's important that they're part of the development team, that they're not a silo, they aren't the boss or decision maker for the team & they aren't a replacement for the customer JIRA is actively contributing to poor development behaviours We don't need big long complicated specs, we don't need backlogs, estimates, story points or velocity charts. We'd be better off with index cards stuck to a wall (or Miro!) Listen to the episode for this and more!   Follow the progress of Allen's book: Allen is writing a book! Check out the progress of the book here. Go to Allen's User Story workshop If you want to go to Allen's upcoming class on User Stories, check out the details here. Contact Allen You can reach out to Allen on Twitter, or book a chat with him.

Nachdem wir bereits über die agilen Schätzmethoden Magic Estimation und Planning Poker in vorherigen Podcastfolgen gesprochen haben, geht es in dieser Episode um NoEstimates. Dominique und Oliver sprechen darüber, warum sie auch "Nicht-Schätzen" in diese Reihe der Praktiken einordnen. Statt beispielsweise mit der Fibunacci-Reihe zu agieren werden bei NoEstimates in der Regel die Anzahl der Items gezählt und so Prognosen anhand von historischen Daten erstellt. Dominique und Oliver schauen auf die grundsätzlichen Schwierigkeiten, sofern ich als Product Owner mit Schätzungen arbeite. Sie diskutieren die eine oder andere Dysfunktion und die Gefahr, sich zu sehr auf Fristen und Product Delivery zu konzentrieren. Nachdem so die Motivation sich mit NoEstimates zu beschäftigen geklärt ist, geht es im Kern der Folge um die Voraussetzungen, die ich schaffen muss. Und natürlich werfen Oliver und Dominique auch einen kritischen Blick auf Schwierigkeiten, die bei dieser Methode aufkommen kann. Wie immer runden persönliche Tipps aus dem eigenen beruflichen Werdegang diese Episode ab. Dominique empfiehlt folgende YouTube-Videos für einen Einstieg in das Thema: NoEstimates von Vasco Duarte NoEstimates von Allen Holub

  Allen is an internationally recognized software architect and consultant/trainer focusing on organizational agility. He helps people build software better & build better software. He's available as a consultant to help your company with it's agility.   Links https://holub.com/ https://twitter.com/allenholub https://www.linkedin.com/in/allenholub/   Resources https://holub.com/heuristics/ #NoEstimates The Death of Agile Drive: The Surprising Truth About What Motivates Us "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!  

Necmettin Özkan hakkında : https://tr.linkedin.com/in/necmettinozkan Podcast konusu olan makale : https://www.researchgate.net/publication/353396540_Towards_the_End_of_Agile_Owing_to_Common_Misconceptions_in_the_Minds_of_Agile_Creators Diğer ilgili makaleler: The dark side of agile software development: http://darkagilemanifesto.org/dark-side-of-agile-janes-succi-splash-2012.pdf The Evolutionary Trajectory of the Agile Concept Viewed from a Management Fashion Perspective: https://pdfs.semanticscholar.org/c6d0/4e7966b386b4e227c2927df8c179bd25eda6.pdf İlgili Videolar: “Agile is Dead” by Dave Thomas (Agile manifesto yazarı): https://www.youtube.com/watch?v=a-BOSpxYJ9M&list=PL9jAj30XT3yXps9qbQN2O79dl1VgA1ieX&index=2 “The Death of Agile” by Allen Holub: https://www.youtube.com/watch?v=HZyRQ8Uhhmk&list=PL9jAj30XT3yXps9qbQN2O79dl1VgA1ieX&index=11 “Agile™'ın Sonu mu Geliyor?” by Necmettin Özkan: https://www.youtube.com/watch?v=MJ4nf2vgUDA&list=PL9jAj30XT3yXps9qbQN2O79dl1VgA1ieX&index=17 “Why Scrum sucks” by Florian Haas: https://www.youtube.com/watch?v=FTM_-H1cPNE&list=WL&index=58 Web Pages: The Craziest Things in Working with Methods and Frameworks (Essence): https://www.linkedin.com/groups/12544857/

#5amMesterScrum Show 706 Live - Bringing Home the Bacon in Baseball and Work plus Fortune Cookie Friday  - Today's topic: (1) Went to Iron Pigs minor league baseball and there was no bacon but they committed to tons of the stuff and Bringing home the bacon at work reflecting on post by Allen Holub about salary and (2) Fortune Cookie Friday: Empty Commitments Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum #5amMesterScrum #scrum #agile #business #scrummaster #agilecoach #coaching #philadelphia #philly #value #commitment #customer #revenue #fortunecookie 5am Mester Scrum Show 706 went live on Youtube Friday 9/10/2021 from Philadelphia, PA  Happy Scrumming, Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum)

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubAino Vonge Corry - Author of "Retrospectives Antipatterns" - @apaipiAllen Holub - Author of "Holub on Patterns" & "Taming Java Threads" - @allenholubBernd Rücker - Author of "Practical Process Automation" - @berndrueckerMary Poppendieck - Author of "The Lean Mindset" - @mpoppendieckMike Amundsen - Author of "Design and Build Great Web APIs" - @mamundRobert C. Martin (Uncle Bob) - Author of "Clean Code" & "The Clean Coder", Co-author of the Agile Manifesto - @unclebobmartinDESCRIPTIONSharing from our experiences is one of the most important ways in which we can help software developers and engineers that are just starting out. We asked some of the well-known and respected names in the industry what are some of the things they wish someone had told them when they were starting out. Dive into this GOTO Unscripted episode to discover the stories of Mary Poppendieck, Mike Amundsen, Allen Holub, Bernd Rücker, Aino Vonge Corry and Uncle Bob Martin. Read the full transcription of the interview here:https://gotopia.tech/bookclub/episodes/you-wish-you-had-known-when-you-started-as-a-developerRECOMMENDED BOOKSAino Vonge Corry • Retrospectives Antipatterns • https://amzn.to/3naFk84Bernd Rücker • Practical Process Automation • https://amzn.to/3cs3BSHMike Amundsen • Design and Build Great Web APIs • https://bookshop.org/a/9452/9781680506808Uncle Bob • Clean Code • https://amzn.to/3soPO6kUncle Bob • Clean Coder • https://amzn.to/3dhEPWXUncle Bob • Clean Architecture • https://amzn.to/3x0gjBQUncle Bob • Clean Agile • https://amzn.to/3fEqTrOAllen Holub • Holub on Patterns • https://amzn.to/3g8Is3uAllen Holub • Taming Java Threads • https://amzn.to/3mLNYdIMary & Tom Poppendieck • The Lean Mindset • https://amzn.to/3hqeczXMary & Tom Poppendieck • Implementing Lean Software Development • https://amzn.to/3hm6XufMary & Tom Poppendieck • Leading Lean Software Development • https://amzn.to/2STLX4vMary & Tom Poppendieck • Lean Software Development • https://amzn.to/3hkZifIhttps://twitter.com/GOTOconhttps://www.linkedin.com/company/goto-https://www.facebook.com/GOTOConferencesLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at https://gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

"#Agile" in many ways has been corrupted by rote processes, rules, and coercion. Is the same thing happening to #MobProgramming? Can #MobProgramming be taught with a handbook of rules, patterns, and formulas? Or is it only caught? Is the only rule "there are no rules"? How can one share their Mob Programming leanings and discoveries in a way that does not sound like formulas? What is the right mindset in learning anything from others? Come join Austin and Chris as they discuss these intriguing topics and more with Allen Holub and Rob Williams. Video and show notes: https://youtu.be/8EGPI5eNOIA 

Many management experts believe that competition kills collaboration and that's why a software team must not encourage their people to compete. Instead, they should collaborate and help each other. I don't see a contradiction here. Moreover, I don't think that a fully altruistic collaboration is at all possible and/or productive. I argue with Allen Holub in this video. The video is here: https://www.youtube.com/watch?v=qRuzYdmgjCg

Shift-M podcast: https://www.yegor256.com/shift-m.html Allen Holub personal website: https://holub.com/ Allen's Twitter: https://twitter.com/allenholub Video is here: https://youtu.be/8OKdilyNOIg

Chris and Austin have a stimulating discussion with Allen Holub (https://twitter.com/allenholub) hitting a range of topics including Mob Programming in-person vs. remote, Agile vs. Agility, organizational change, and Scrum, SAFE, & certs, oh my!  Video and shows notes: https://youtu.be/nLUFPHUS2Pk 

In this episode, Allen joined Shahin to talk about what truly Agile is in today’s world of Software Development. Topics We conversed about and around the following topics: Agile or Not Agile is nothing more than Better Software Better What is Real Agile Thinking? Reasons to Avoid Agile Fake Agile, Dark Agile (Foe Agile) Trust is the heart of agile SAFE v.s. Scrum; Kanban Board Assumes Linear Process Agile in The Time of Corona Scrum’s Response to Corona Remote Working Went Bad – More Silos The Complexity Of Working From Home Work Is A Human Activity Challenges of Successful Agile Transformation in Large Organization (And Typically Failures) Experiments Failure in Big Organizations; PMO and Agile Failure Pattern ING Transformation Story (New Zealand) + Home Depot Dunbar Number Agile Architecture Designing Flexible (Agile) Code and Dependency (of code) with the Client; The Holub Principle Architecture Process Code Culture Connected for True Agile Mob Moves Forward Even If Individual Has To Drop Out And Come Back In Social Software Development & Mentorship People & Resources: We referred to and/or mentioned the following people and/or resources: Books Fixing Your Scrum – (Amazon US – Amazon CA) Scrum: The Art of Doing Twice the Work in Half the Time – (Amazon US – Amazon CA) Holub on Patterns (Amazon US – Amazon CA) People: Ryan Ripley Jeff Sutherland Ken Schwaber The New New Product Simon Brown Gerry Weinberg For more details please visit http://podcast.leanonagile.com. Twitter: twitter.com/LeanOnAgileShow  LinkedIn: linkedin.com/company/lean-on-agile

How do organizations actually work with Agile? In this episode of Programming Leadership, Marcus and his guest, Allen Holub, discuss what organizations get wrong about Agile. Allen has been an Agile transformation consultant for nearly 40 years and has seen the best and worst it has to offer. Luckily, he says the worst can be avoided. The challenge lies in company culture and architecture. The Agile way of working can be a shock to an organization’s system. However, those willing to suffer a few growing pains can reap tremendous rewards further down the line!   Show Notes Why Agile is failing (3:55) Teams are not Agile, organizations are (7:12) When Agile works (15:14) The inspect and adapt loop (26:21) Obstacles preventing organizations from being Agile (30:27) Why people can’t imagine work working differently (37:16) Advice for people realizing that they’re not actually Agile (39:46) Allen’s consulting strategy (43:13)   Links: Toyota Kata, Mike Rother Follow Allen Holub on Twitter Holub.com Email Allen at allen@holub.com Schedule a video chat with Allen at holub.com/chat Agile and Lean Software Development Group on LinkedIn O’Reilly Infrastructure & Ops Conference: http://oreilly.com/infraops/blankenship

Phil’s guest on this episode of the IT Career Energizer podcast is Allen Holub.  An internationally recognised software architect and Agile-transformation consultant.  He’s worn every hat from CTO to grunt-programmer, and is an expert-level programmer in many languages.   He is also an international speaker and a widely published author, having written ten books and hundreds of articles.    In this episode, Phil and Allen discuss the unique challenges working as an independent throws up and how to cope with them. They also discuss the benefits that working this way bring.   They talk about why you need to seek advice from the right people. Then reveal two non-technical skills that will keep you organised and energize your career.   KEY TAKEAWAYS: (7.29) TOP CAREER TIP If you are working as a consultant, make sure you keep at least 6 months of cash to hand. Your income is going to fluctuate and you need to be able to cover your bills.   Social media marketing is important for consultants. Twitter works particularly well. It enables you to have proper conversations and gives lots of people the chance to get to know you a bit.   (9.36) WORST CAREER MOMENT Allen was once hired to work on a terrible piece of software. It was so bad that he was obliged to write to the CEO and say so. He knew he had done the right thing. But, three years later, he was still struggling to find work. Former members of that team kept getting him blackballed.   But, he does not regret doing it. Allen thinks it is important to be honest. When you are consistently honest people hear about it and know they can trust you.   (12.49) CAREER HIGHLIGHT Making a positive difference to how people work and helping them to achieve more, is very fulfilling. So, for Allen, each new success is a highlight.   Speaking at conferences has enabled him to reach thousands more people. In the podcast, Allen shares an effective way to push yourself out of your comfort zone. A method you can use to start public speaking and benefiting from doing so.     (15.49) THE FUTURE OF CAREERS IN I.T Allen says that for the I.T. industry the future is kind of interesting. However, he is concerned that we are starting to repeat past mistakes.   This is particularly the case when it comes to the Agile way of working. Many firms have tweaked it to the point where it is no longer Agile. Instead, they have more or less gone back to their previous inefficient ways of working. Allen explains why this has happened and touches on how issues like this can be rectified.     (19.10) THE REVEAL What first attracted you to a career in I.T.? – Wanting to make his own electronic instruments led to Allen becoming interested in I.T. What’s the best career advice you received? – Because Allen’s career has not been a traditional one, he has not received much career advice. What’s the worst career advice you received? – Allen is an introvert, so he finds it impossible to effectively apply the marketing advice created for him by extroverts. It just does not work for him. What would you do if you started your career now? – Allen says he probably would not pursue an IT career, again. He explains why, during the podcast. What are your current career objectives? – Allen’s current focus is on marketing himself. He is also planning to write another book. What’s your number one non-technical skill? Being able to write well. It helps you to stay organised and communicate effectively. How do you keep your own career energized? – Speaking at conferences helps Allen to energize his career. It keeps him interacting with others and learning. What do you do away from technology? – Allen is an artist, so he draws occasionally and still enjoys playing the piano.   (24.57) FINAL CAREER TIP Provided you can handle the uncertainty and cash flow issues, working as an independent is a great career choice. It insulates you from a lot of negativity and is an interesting and fulfilling way of working.   BEST MOMENTS (7.50) – Allen - “For consultants, cash flow is a constant problem. So, you need six months of cash sitting around.” (11.40) – Allen - “You’ve got to be honest. If you are not you can’t do a good job.” (14.33) – Allen - “There is no need to fear public speaking. After all, you are just talking to people who are basically like you.” (20.41) – Allen - “To be useful, advice has to be given by someone who knows you and understands your work.” (25.30) – Allen - “Working as an independent insulates you from a lot of the problems that are associated with our industry”     ABOUT THE HOST – PHIL BURGESS Phil Burgess is an independent IT consultant who has spent the last 20 years helping organisations to design, develop and implement software solutions.  Phil has always had an interest in helping others to develop and advance their careers.  And in 2017 Phil started the I.T. Career Energizer podcast to try to help as many people as possible to learn from the career advice and experiences of those that have been, and still are, on that same career journey.   CONTACT THE HOST – PHIL BURGESS Phil can be contacted through the following Social Media platforms:   Twitter: https://twitter.com/philtechcareer LinkedIn: https://uk.linkedin.com/in/philburgess Facebook: https://facebook.com/philtechcareer Instagram: https://instagram.com/philtechcareer Website: https://itcareerenergizer.com/contact   Phil is also reachable by email at phil@itcareerenergizer.com and via the podcast’s website, https://itcareerenergizer.com Join the I.T. Career Energizer Community on Facebook - https://www.facebook.com/groups/ITCareerEnergizer   ABOUT THE GUEST – Allen Holub Allen Holub is an internationally recognised software architect and Agile-transformation consultant.  He’s worn every hat from CTO to grunt-programmer, and is an expert-level programmer in many languages.   He is also an international speaker and a widely published author, having written ten books and hundreds of articles.     CONTACT THE GUEST – Allen Holub Allen Holub can be contacted through the following Social Media platforms:   Twitter: https://twitter.com/allenholub LinkedIn: https://twitter.com/allenholub Personal Website: https://holub.com/  

Allen Holub on Deliver It, Jason Tanner on Drunken PM, Mary and Tom Poppendieck on Unlearn, Saron Yitbarek on Greater Than Code, and Dave Karow and Trevor Stuart on Deliver It. 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 July 8, 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. ALLEN HOLUB ON DELIVER IT The Deliver It podcast featured Allen Holub with host Cory Bryan. Cory started out by reviewing an article by Ron Jeffries called “Story Points Revisited.” Allen’s take is that the negatives around story points are more than just the potential for misuse; he believes story points have no value at all. He says the most important thing is to narrow your stories, not estimate them. He says estimates exist because of fear. The software development process is opaque to certain managers and, as a result, they want estimates to alleviate their fear, but when you are delivering every day, you can eliminate the fear without resorting to estimates. Cory asked Allen what product owners need to know about Agile architecture. Allen said that one of the mistakes that he sees product owners make a lot is they try to do a miniature up-front design and expect that to be implemented. When this happens, he says there is too much information captured up-front of what is going to be built during the sprint and not enough information captured during the sprint as a side effect of releasing code to users and getting their feedback. This leads to inappropriate architectures because when you do anything up-front, you start doing everything up-front. Your sprint planning starts involving architecture decisions, UI decisions, and UX decisions that may be wrong and you will not know if you are wrong until you release. In Allen’s view, the most important thing a product owner does is answer questions that come up during the course of development. He uses a “two-minute rule”: if a question comes up during development, the product owner needs to be able to answer within two minutes. Allen talked about how the constraints of a bad architecture can prevent you from ever being Agile. He says, “Agile has nothing to do with standup meetings and backlog grooming and all of those. The important thing is to get stuff into your user’s hands quickly.” Allen says that the architecture has to be focused on the domain. Where systems that are wrong go wrong is that they don’t map to the domain but to the technology. A change at the story level, which is where the majority of changes come from, ends up touching all the modules or layers of your system when your architecture is mapped to your technology instead of your domain. Allen says that when he does a workshop on Agile architecture, people raise their hands about halfway through and say, “All we’re doing is domain analysis!” The fact is, if the domain and code are matched to each other, domain analysis is architecture. One of the questions Allen asks when he gets a bunch of product owners in a class is, “How many of you talk to multiple customers multiple times a day?” Maybe 5% raise their hands. So he says, “Who in the organization does talk to multiple customers multiple times a day?” This is often met with silence. He asks, “What about Sales? What about Tech Support?” He says that if you can’t respond to customer kinds of issues as well as a salesperson or a tech support person could, you don‘t know the domain well enough to be helpful to the engineering team. Cory asked Allen what he thought of the distinction between regular stories and “technical” stories. Allen says that there is no such thing as technical stories. A story describes the users of your system performing some kind of domain level work to achieve a useful outcome. Fixing some technical thing like changing the color of a button in no way makes your end users’ lives easier; it does not help them do their work. Allen says that the role of the architect in an Agile environment is very different from what we traditionally think of, just like the role of a manager in an Agile environment. In Agile environments, the job of people who are in a leadership position is to make sure that you can do your job, not to tell you what to do. They communicate a strategic requirement, provide support, and remove the obstacles. The same, he says, applies to Agile architects. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ep90-agile-architecture-with-allen-holub/id966084649?i=1000441313352 Website link: http://deliveritcast.com/ep90-agile-architecture-with-allen-holub JASON TANNER ON DRUNKEN PM The Drunken PM podcast featured Jason Tanner with host Dave Prior. Dave started out by asking Jason why he believes the daily scrum is broken. Jason said that the daily scrum is broken because, first, most developers hate the daily scrum because most daily scrums take the traditional weekly project status review meeting and do it five times a week with the Scrum Master filling the role of the project manager. Second, he says, is that it is being done backwards. The center of attention should not be the Scrum Master, but the team and the sprint backlog. He says that the purpose of the daily scrum is misunderstood. The three questions don’t result in a plan but result in just an exchange of information. For what real daily planning looks like, he uses an analogy of driving down the road and seeing a bunch of plumbers’ trucks from the same company parked outside of a McDonald’s. Inside, they’re planning things like, “We’re going to the Johnson’s house at noon. Can you come over and meet me because it’s going to be a two-man job.” Jason says he hates the three questions. He says the subject of the sentence is not helping us in collective ownership of the sprint backlog. “I have my user story. I have my Jira ticket. I have five team members and we each have a ticket.” Shifting the subject of the sentence to “we”, he says, changes the behavior dramatically. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/jason-tanner-is-on-a-mission-to-fix-your-daily-scrum/id1121124593?i=1000441958371 Website link: https://soundcloud.com/drunkenpmradio/jason-tanner-is-on-a-mission-to-fix-your-daily-scrum MARY AND TOM POPPENDIECK ON UNLEARN The Unlearn podcast featured Mary and Tom Poppendieck with host Barry O’Reilly. Barry asked Mary and Tom what we may need to unlearn since the Agile movement began. Mary says that Agile started as a reaction to what was going on at the time. The vast majority of people doing software engineering today weren’t around back then. One of the things Agile has to do is grow up to be not a reaction to bad things that happened in the past, but to be something that talks about, “What does it take to do good software engineering?” She contrasted the software engineers she speaks to today that expect to be handed a spec with the engineers she worked with early in her career who treated engineering as problem-solving. Tom talked about how many who are working to make organizations more agile attempt to solve problems with process. This assumes that the organization’s problems are process problems but they are actually architectural problems. This includes problems with the architecture of the applications they are evolving, problems with the structure of the organization, and problems with the structure of the relationships between the supporting groups and those who are benefitting from said groups. Mary talked about how Amazon AWS was one of the early organizations to understand that you need to give teams of smart, creative people problems to solve. As a result of having this insight, they organized the company in such a way as to optimize for this, such as by eliminating a central database which was heresy back in 2005. She called out AWS Lambda in particular because this product did not optimize for short-term shareholder value and would never have been approved at most companies because it reduced what Amazon was charging customers by five times. She attributes this ability to self-disrupt as being essential to Amazon AWS’s success. Tom talked about the fact that when you attempt to scale things up, you reach a point where complexity dominates any future gains and wipes them out. He says you instead need to de-scale: figure out how to do things in little chunks that are independent and don’t require coordination. He says that this is how cities have been organized for thousands of years. Mary said that she has been doing software since 1967 and has never seen anything last two decades and still be current. Agile is two decades old and cannot be current unless it is constantly adapting to what is current today. She brought up continuous delivery as a fundamental change in agile thinking. It changed the way we thought about how we structure organizations and teams and what kinds of responsibilities we should give to them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/solving-problems-safely-with-mary-and-tom-poppendieck/id1460270044?i=1000442018979 SARON YITBAREK ON GREATER THAN CODE The Greater Than Code podcast featured Saron Yitbarek with hosts Arty Starr, Rein Henrichs, and Chanté Thurmond. They talked about the annual Codeland conference Saron is running and how it offers free on-site childcare this year. Saron says free on-site childcare at conferences today is where codes of conduct were a few years ago. She says that if her conference wasn’t making it easier for parents to attend, it wouldn’t be living up to their promise for inclusion. Chanté asked Saron what she learned in her transition from being a code newbie herself to the present day where she is running two podcasts, a software job, and a conference. Saron said she learned that it is important to be consistent in all your efforts, whether it is community work, your personal projects, or a project at work. Nothing gets built overnight and, for a while, nobody will care what you’re doing. If you want to do something great, it takes persistence and it takes you believing in yourself especially when you’re not getting external validation. Arty asked about what expertise in “newbie-ism” might look like. Saron says that it is about being comfortable in a state of frustration. She pointed to a study on the difference between those who finish a computer science degree and those who quit. The study said that those who finished the degree were comfortable being in a state of confusion: they knew that things were not going to make sense for a while and they were ok with that. A second thing, she says, that helps you become an expert newbie is realizing that almost all problems in coding are solvable. By contrast, in writing, there is no perfect essay. In journalism, there is a search for truth, but is truth attainable? In life sciences, we study nature all around us that we may never fully understand. She also says to keep your frustration external, avoid internalizing your failures, and she says to distance who you are from your work and the things you produce. Saron’s comment on being comfortable in a state of confusion triggered a Virginia Satir quote from Rein: “Do you know what makes it possible for me to trust the unknown? Because I've got eyes, ears, skin. I can talk, I can move, I can feel, and I can think. And that's not going to change when I go into a new context; I've got that. And then I give myself permission to say all my real yeses and noes, because I've got all those other possibilities, and then I can move anywhere. Why not?” Rein asked what Saron learned about teaching. Saron says that teaching is storytelling in disguise. She says that if we frame teaching opportunities as storytelling opportunities we can be better teachers. This reminded me of Josh Anderson’s comment on the Meta-Cast podcast that I referenced way back in episode 3, “Taking The Blue Pill Back To Sesame Street.” Rein brought up a theory of learning called conversation theory. In conversation theory, teaching happens as a conversation between two cognitive entities. You have to come to agreement and build a bridge with that other cognitive entity. It deconstructs the teacher-learner binary. The teacher themselves has to be a learner too. Chanté asked about the ethos at Code Newbie for being a learner and a teacher. Saron says they look to the community to pitch in. When someone asks a question, they encourage the community to answer. She contrasted Code Newbie with Stack Overflow. Code Newbie attempts to teach the learner from where they are and avoid the condescension that is common on Stack Overflow. She said that to create an environment where people are not afraid to ask questions, we have to be unafraid of being vulnerable ourselves. Go first, share your vulnerability, and share what you’re struggling with. The moment you start doing that, other people will be much more likely to raise their hands as well. Chanté asked Saron what resources she recommends for code newbies to learn to code. Saron said that the hard part isn’t finding resources but sticking with them when things get tough or boring. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/135-intentional-learning-with-saron-yitbarek/id1163023878?i=1000442022293 Website link: https://www.greaterthancode.com/intentional-learning DAVE KAROW AND TREVOR STUART ON DELIVER IT The Deliver It podcast featuring Dave Karow and Trevor Stuart with host Cory Bryan. They talked about running experiments to learn about your customer. Cory asked how people can run such experiments at scale. David pointed out that having a way to run the experiment is one thing, but you also need to be able to rapidly make sense of the results in a repeatable, authoritative way. Trevor says it is all about assumptions, hypotheses, and documentation. Before you even start your experiment, you need to understand why you are running it in the first place. In other words, you need to establish what is going to change as a result of the experiment. Trevor says that much of the market is already doing experiments and they don’t know it. They just call it “using feature flags” and rolling things out incrementally. They just need to move one step further to slice and dice their user populations, roll things out for longer time periods to those users, and bring the resulting data into a form that facilitates decision-making. David talked about dog-fooding by starting your rollout of new features with your employee population, giving examples from Microsoft, where it takes a few weeks to go from the employee population to the full customer population, and Facebook, where it takes about four hours for the same kind of rollout. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ep91-product-experiments-with-trevor-and-dave-from-split/id966084649?i=1000442844631 Website link: http://deliveritcast.com/ep91-product-experiments-with-trevor-and-dave-from-split 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:

  Product Owners need to understand that a significant component of how well the team is able to deliver, depends on their product architecture. In fact, it’s often a limiting factor in how agile you really can be.  Because it’s so important, Allen Holub joins this episode to talk about what PO’s need to know about architecture, why it’s so important, and how they can help determine it’s direction. All while keeping the main value and focus on the customer's benefit.   Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: PO Coaching and Consulting - seek taiju Alan Holub -  https://holub.com, @allenholub Software Architect 2013 - Agile Architecture Part 1 - Allen Holub - Agile Architecture Part 2 - Allen Holub Michael Küsters - Agile Architecture Ron Jeffries - Story Points Revisited MindSumo - 3 New Product Successes (And Why They Won)  

Guest: Allen Holub @allenholub Full show notes are at https://developeronfire.com/podcast/episode-339-allen-holub-ask-if-it-s-useful

Esther Derby (@estherderby), Tim Ottinger (@tottinge), Allen Holub (@allenholub), and Zach Bonaker (@zachbonaker) joined Ryan Ripley (@RyanRipley) to discuss the past, present, and future of Scrum. [featured-image single_newwindow=”false”]A High Performing Scrum Team[/featured-image] Esther is an expert in organizational dynamics and a leading thinker in bringing agility to organizations, management, and teams. She co-authored “Agile Retrospectives: Making Good Teams Great” and “Behind Closed Doors: Secrets of Great Management“. Esther is sought after trainer and speaker. Tim is committed to understanding and improving the art of software from the angle of “thinking for a living.” He is a programmer, author, trainer and globally recognized coach with over 35 years of real software development experience. His style is practical and hands-on, steeped in both Agile and classic traditions. Tim rapidly communicates concepts and practices, and is recognized for his compassionate and patient approach to working with individuals and has a sincere interest in helping people reach their goals. Allen is a trainer, writer, speaker, and coach who takes a non-tribal view of software development. He is a highly regarded instructor for the University of California, Berkeley, Extension. Allen eschews the dogma that surrounds many of the current agile topics and practices. Zach is a self-described “benevolent trouble-maker” and seeks to foster servant leadership that cultivates growth, learning, and discovery. He is a systems thinker who shares his thoughts on his blog – Agile Out Loud. Zach is great at pushing agile thinking forward and has authored many popular posts on next generation agile theories and practices. In this episode you'll discover: Impediments to adopting Scrum Management’s role on agile and scrum teams Why scrum may not be the right framework for you Links from the show: The Scrum Guide [callout]Great management is difficult to see as it occurs. It’s possible to see the results of great management, but it’s not easy to see how managers achieve those results. Great management happens in one-on-one meetings and with other managers—all in private. It’s hard to learn management by example when you can’t see it. You can learn to be a better manager—even a great manager—with this guide. You’ll follow along as Sam, a manager just brought on board, learns the ropes and deals with his new team over the course of his first eight weeks on the job. From scheduling and managing resources to helping team members grow and prosper, you’ll be there as Sam makes it happen. Click here to purchase on Amazon.[/callout] [reminder]Which topic resonated with you? Please leave your thoughts in the comment section below.[/reminder] Want to hear another podcast about the life of an agile coach? — 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! Techwell's Agile Dev East is *the* premier event covering the latest advances in the agile community. Agile for Humans listeners can use the code AGILEDEV to receive up to $200 off any registration package over $800. Check out the entire program at adceast.techwell.com. You'll notice that I'm speaking there again this year. Attendees will have a chance to participate in my Aligning Toward Business Agility–360° of Freedom Leadership Summit presentation, along with my half day sessions on advanced scrum topics called Scrum: Answering the Tough Questions, as well as Rethinking Your Retrospectives. I hope to see many Agile for Humans listeners in Orlando – November 5-10, for this great event. The post AFH 074: The Past, Present, and Future of Scrum appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Allen Holub (@allenholub) joined me (@RyanRipley) to discuss his Kickstarter project: Agility with Allen: The Whole Caboodle. [featured-image single_newwindow=”false”]Agility with Allen Holub[/featured-image] Allen is a trainer, writer, speaker, and coach who takes a non-tribal view of software development. He is a highly regarded instructor for the University of California, Berkeley, Extension. Allen eschews the dogma that surrounds many of the current agile topics and practices. In this episode you'll discover: Insights in to creating a Kickstarter project How LEAN is at the center of most of the things agilists do Where to go to learn more about Allen’s Kickstarter project Links from the show: Allen’s website:  holub.com Kickstarter: Agility with Allen: The Whole Caboodle Capital C Documentary Allen’s #NoEstimates Keynote [callout]Written in a fast-paced thriller style, The Goal, a gripping novel, is transforming management thinking throughout the world. It is a book to recommend to your friends in industry – even to your bosses – but not to your competitors. Alex Rogo is a harried plant manager working ever more desperately to try improve performance. His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant – or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a professor from student days – Jonah – to help him break out of conventional ways of thinking to see what needs to be done. Click here to purchase on Amazon.[/callout] [reminder]What are your thoughts about this episode? Please leave them in the comments section below.[/reminder] Want to hear another podcast episode with Allen Holub? — Listen to my conversation with Allen on episode 21. We discuss #NoEstimates, #NoManagement and what it truly means for an organization to adopt agility 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 Audible. I have used Audible for years, and I love audio books. I have three to recommend: Agile and Lean Program Management by Johanna Rothman Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland The Lean Startup by Eric Ries All you need to do to get your free 30-day Audible trial is go to Audibletrial.com/agile. Choose one of the above books, or choose between more than 180,000 audio programs. It's that easy. Go to Audibletrial.com/agile and get started today. Enjoy! The post AFH 060: Kickstarting Agility with Allen Holub [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

Hosts Ryan Ripley, Allen Holub Discussion Allen Holub (@allenholub) joined me (@RyanRipley) for a discussion about #NoEstimates, #NoManagement and what it truly means for an organization to adopt agility. Allen is a trainer, writer, speaker, and coach who takes a non-tribal view of software development and eschews the dogma that surrounds many of the current agile topics and practices. Allen recently gave a keynote at DevWeek 2015 on #NoEstimates where he opened with: “We just need to stop doing all estimation now.” Along with #NoEstimates, Allen I discussed what it truly means for an organization to adopt agility, why such a transformation is so difficult, and how Kanban wrapped around a waterfall can make life easier for both companies and coaches. We wrapped up with a discussion on #NoManagement and Holocracy. And then…we called it a night. Agile for Humans is brought to you by audible.com – get one FREE audiobook download and 30 day free trial at www.audibletrial.com/agile Resources, Plugs, and More Ryan – https://ryanripley.com Vasco Duarte's NoEstimates Book The Tipping Point by Malcolm Gladwell Drive by Daniel Pink Allen – http://holub.com Allen is teaching a 3 day class on agility at SDD Deep Dive in London on Nov 10-12 Allen’s class offerings: “Agility” focuses on agile culture and what you need to do as an organization to make agile processes work “Designing for Volatility” – an in-depth dive into how to design scalable fault-tolerant systems that can be built in an incremental way and can stand up to the stress of constant change “Design by Coding” an extension of TDD/BDD techniques to the architectural level. Self-Insight: Roadblocks and Detours on the Path to Knowing Thyself by David Dunning The original Kruger/Dunning paper Then of course, there’s John Cleese on Kruger/Dunning The post AFH 021: Agility with Allen Holub [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.