POPULARITY
3 episodes with lean software
3 episodes with lean software
3 episodes with lean software
4 episodes with lean software
4 episodes with lean software
2 episodes with lean software
3 episodes with lean software
5 episodes with lean software
2 episodes with lean software
This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereStephen Fishman - Field CTO at Boomi & Co-Author of "Unbundling the Enterprise"Matt McLarty - CTO at Boomi & Co-Author of "Unbundling the Enterprise"Erik Wilde - Principal Consultant at INNOQRESOURCESStephenhttps://x.com/fistsOfReasonhttps://www.linkedin.com/in/stephenhfishmanhttps://github.com/StephenFishmanMatthttps://bsky.app/profile/mattmclartybc.bsky.socialhttps://x.com/MattMcLartyBChttps://www.linkedin.com/in/mattmclartybcErikhttps://www.linkedin.com/in/erikwildehttps://github.com/dretLinkshttps://itrevolution.com/articleshttps://www.hbs.edu/faculty/PagesDESCRIPTIONHow can businesses thrive by embracing optionality through digital transformation?Authors Matt McLarty and Stephen Fishman talk about their book “Unbundling the Enterprise” with Erik Wilde. They highlight the power of APIs and flexible systems in enabling companies to capitalize on unforeseen opportunities, or "happy accidents," and how low-cost experimentation can drive long-term success.The conversation emphasizes that optionality is crucial not only in tech but also in business strategy, urging organizations to view their digital capabilities as part of a broader platform that supports both developer empowerment and revenue growth. With insights on optimization, platform engineering, and the importance of aligning technology with business objectives, the authors offer a roadmap for companies to navigate the future with agility and resilience.RECOMMENDED BOOKSStephen Fishman & Matt McLarty • Unbundling the EnterpriseCarliss Y. Baldwin • Design Rules, Vol. 2Matthew Skelton & Manuel Pais • Team TopologiesForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookMik Kersten • Project to ProductAndrew Harmel-Law • Facilitating Software ArchitectureBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!
The Software Process and Measurement Cast Crew is on vacation. Until then, we are revisiting some fabulous panel discussions we have had during the last 19 years. We will be back on June 21st. Poor work intake equals out-of-control. Being out of control leads to stress and poor quality. Mastering Work Intake is the path to bringing order out of chaos. Buy a copy today! JRoss Publishing or Amazon. JRoss Publishing: Amazon: Original Show Notes: In March 2020, as our world was shrinking and words like 'lockdown' and 'zoom-bombing' were becoming a reality, we recorded and aired . Paul Laberge, Susan Parente, Jo Ann Sweeney, John Voris, and I talked about how we could create or preserve interactions leading to serendipity. Remote working was new for many people. This week we discuss what went well and what have we learned from nearly a year of working remotely. As the editor of the SPaMCAST it is my great pleasure to reconvene a group of people that have such great insight into people. The discussion is full of great ideas to improve remote and hybrid working environments, but most of all it is full of ideas to help respect people in tough times or not. Panelist Bios Jo Ann Sweeney FCIM FIIC MCIPR is an engagement and communication consultant. Typically, she acts as change management lead on complex programmes, facilitating development of effective engagement, training, and communication strategies and then assisting as the strategies are implemented. Clients value her deep understanding of audiences. Jo Ann is known for clarifying the complex and for persuading key stakeholders to get involved and actively support change. You are welcome to download a complimentary copy of Jo Ann's guide How to Explain Change in 8 Easy Steps at Contact Jo Ann at jo.ann@sweeneycomms.com John Voris is the current leader of AgilePhilly, the local user group in the Philadelphia area for Scrum, Kanban, and Lean Software. () His day job is working on financial applications for Crown Cork & Seal, an essential company with over 100 years of manufacturing food and beverage cans. Prior to Crown, John was an independent software consultant for 30+ years helping both small companies and Fortune 100 large companies with both applications and operating systems. Reach out on LinkedIn: With more than 30 years in the information technology industry, Paul Laberge – CGI Director Consulting-Expert, has a wide range of experience providing IT project management. He enjoys coaching leaders in deploying business technology solutions. His experience in organizational change management spans many different lifecycles including transitions to Agile frameworks (RUP, XP, Scrum, SAFe, Nexxus, LeSS) and incorporating Lean (Kanban) methodologies. Reach out on LinkedIn: Susan Parente is a Principal Consultant at S3 Technologies, LLC and a University Professor at multiple Universities. Mrs. Parente is an author, mentor and professor focused on risk management, traditional and Agile project management. Her experience is augmented by her Masters in Engineering Management with a focus in Marketing of Technology from George Washington University, DC, along with a number of professional certifications. Ms. Parente has 23+ years' experience leading software and business development projects in the private and public sectors, including a decade of experience implementing IT projects for the DoD. Contact Susan at parente.s3@gmail.com
The Software Process and Measurement Cast Crew is on vacation. Until then, we are revisiting some fabulous panel discussions we have had during the last 19 years. We will be back on June 21st. Poor work intake equals out-of-control. Being out of control leads to stress and poor quality. Mastering Work Intake is the path to bringing order out of chaos. Buy a copy today! JRoss Publishing or Amazon. JRoss Publishing: Amazon: Original Show Notes: SPaMCAST 597 features a special panel of leaders who discuss working from home now and after the initial reaction to being remote has worn off. One of the important points we discussed was the need to make space for intentional serendipity. The panel is composed of Paul Laberge, Susan Parente, John Voris, Jo Ann Sweeney, and your host. Panelist Bios Jo Ann Sweeney FCIM FIIC MCIPR is an engagement and communication consultant. Typically, she acts as change management lead on complex programmes, facilitating development of effective engagement, training, and communication strategies and then assisting as the strategies are implemented. Clients value her deep understanding of audiences. Jo Ann is known for clarifying the complex and for persuading key stakeholders to get involved and actively support change. You are welcome to download a complimentary copy of Jo Ann's guide How to Explain Change in 8 Easy Steps at Contact Jo Ann at jo.ann@sweeneycomms.com John Voris is the current leader of AgilePhilly, the local user group in the Philadelphia area for Scrum, Kanban, and Lean Software. () His day job is working on financial applications for Crown Cork & Seal, an essential company with over 100 years of manufacturing food and beverage cans. Prior to Crown, John was an independent software consultant for 30+ years helping both small companies and Fortune 100 large companies with both applications and operating systems. Reach out on LinkedIn: With more than 30 years in the information technology industry, Paul Laberge – CGI Director Consulting-Expert, has a wide range of experience providing IT project management. He enjoys coaching leaders in deploying business technology solutions. His experience in organizational change management spans many different lifecycles including transitions to Agile frameworks (RUP, XP, Scrum, SAFe, Nexxus, LeSS) and incorporating Lean (Kanban) methodologies. Reach out on LinkedIn: Susan Parente is a Principal Consultant at S3 Technologies, LLC and a University Professor at multiple Universities. Mrs. Parente is an author, mentor and professor focused on risk management, traditional and Agile project management. Her experience is augmented by her Masters in Engineering Management with a focus in Marketing of Technology from George Washington University, DC, along with a number of professional certifications. Ms. Parente has 23+ years' experience leading software and business development projects in the private and public sectors, including a decade of experience implementing IT projects for the DoD. Contact Susan at parente.s3@gmail.com
Applying 'Accelerate' Principles to Embedded Systems | Agile Embedded PodcastWelcome to the latest episode of the Agile Embedded Podcast with Jeff Gable and Luca Ingianni! In this episode, we address a listener's question about the book 'Accelerate' by Nicole Forsgren, Jez Humble, and Gene Kim. Jeff and Luca delve into how the principles from this book, which focuses on Lean Software and DevOps, can be applied to embedded systems development. They discuss the nuances of embedded systems, the relevance of DORA metrics, and share insights on how capabilities and processes from the book translate to the unique challenges of embedded systems. Tune in to understand how you can adapt and implement these best practices in your projects.00:00 Introduction to the Agile Embedded Podcast00:06 Overview of the Book 'Accelerate'00:50 Research Methodology and Key Findings02:56 DORA Metrics Explained05:30 Key Capabilities for Effective Organizations18:41 Applying 'Accelerate' Principles to Embedded Systems20:19 Challenges and Considerations in Embedded Systems34:10 The Importance of Logging and Feedback Loops37:43 Empowering Teams and Encouraging Experimentation41:58 Final Thoughts and Recommendations You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here
Join us in this thoughtful episode of the Mob Mentality Show as we explore the world of Lean Software Development with Dave Adsit. Titled "Crafting Lean Software: Dave Adsit on Small Batches and Short Lead Times," this episode provides valuable insights for those looking to enhance their software development values and practices. Dave Adsit shares his experiences on how to effectively implement lean principles to achieve small batches, short lead times, and frequent releases. ### Key Discussion Points: #### **Lean Software Development** - **Craft vs. Engineering** - **Principles of Flow** - **Waterfall vs. "Agile" vs. Lean** - **Timeboxes vs. Scope-Boxes** - **Resource vs. Flow Efficiency** - **Prioritization, Prototyping, and Lean Investment Bets** - **Single Piece Flow, Feature Flags, Continuous Delivery** - **Maximal Learning through Experimentation and a 50% Product Bet Success Rate** #### **Collaboration** - **Integration with Lean** - **"All Hands on Deck" Mindset** - **Relation to WIP Limits** - **Pair and Mob Programming** - **Failures and Lessons** - **Rules, Why, and Learning Paths** - **Utilization and Person vs. Team vs. System Value** #### **Continuous Improvement** - **Core Value** - **Innovative vs. Inert Practices** - **Deep vs. Shallow Learning** - **Leading Learning Opportunities** - **Knowing Enough to Make Informed Decisions** - **What If Some Do Not Want to Learn?** - **Rock Star vs. Super-Star** Video and Show Notes: https://youtu.be/LgAMUGtdXGA
Could the secret to organizational success be as simple as going back to basics? Gene Kim and Steven Spear's new book, Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and Amplification presents practical, grounded research on organizational management and design. Gene is the chair of the Enterprise Technology Leadership Summit and Steven teaches at MIT Sloan.Gene and Steven walk Greg through the three mechanisms of successful organizational design: slowify, simplify, and amplify. They also discuss how the field of organizational design has evolved and what still needs to evolve with management education. *unSILOed Podcast is produced by University FM.*Episode Quotes:Three mechanisms of a successful organizational designWe now have everything we need to be able to describe the three mechanisms that must be in place in any high-performing system. You got to slowify, meaning we move the most difficult problems from production into planning and practice, where work can be redone. We can do experiments. We can learn where we can simplify where we actually divide up the problems. We partition them so that they are easier to solve. And there's three dimensions of that. And then there's amplification, this overlay of how do we create a system that can amplify even the weakest signals so that when someone needs help or when there's danger that we can quickly detect and correct or ideally prevent from happening again. What the term ‘slowification' means38:39 The reason why we had to create the word ‘slowification' is that we have a lot of adages for slow down to speed up or stop sawing to sharpen the saw, and the absence of the word prevents us from doing it or thinking it. (38:46) But the whole notion is creating time to be able to solve tough problems not in production but in planning and practice. To solve architectural problems, not during the normal sprint or what have you, but actually making time for the architectural spike or the period of technical debt reduction to enable people to do their work easily and well.The wrong way to measure successA lot of these metric-driven organizations, the pit they fall into is they don't account for the return on investment of discovery. They measure activity but not accomplishment.The great advantages of technology in management educationAnd now, because we can do education at a distance, we can do asynchronous education, we can have education which is interspersed with either structured experiences or just natural experiences that people have. We can now actually teach one by one as needed as ready situation where information is pulled from the instructor to time and place and situation where it's needed, rather than being forced by the instructor in a formulation that the instructor thinks is right but may have nothing to do with the readiness of the student.Show Links:Recommended Resources:Decoding the DNA of the Toyota Production System | Harvard Business ReviewChristina Maslach on unSILOed Gary Klein on unSILOedDr. Richard ShannonRon WestrumKim ClarkNyquist–Shannon sampling theoremGuest Profile:Gene Kim's WebsiteSteven Spear's profile at MIT SloanTheir Work:Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and AmplificationGene's Books:Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology OrganizationsThe DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business WinThe Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of DataSteve's Book:The High-Velocity Edge: How Market Leaders Leverage Operational Excellence to Beat the Competition
In this March roundup, IEEE Spectrum's editor-in-chief Harry Goldstein and senior editor Stephen Cass talk about some of the highlights of Spectrum's recent coverage, including a plea for programmers to stop producing bloated programs, a new transistor that could help make how we handle electrical power smarter, and the potential return of optical discs as a high-density date storage medium.
In the Microsoft Research Podcast series What's Your Story, Johannes Gehrke explores the who behind the technical and scientific advancements helping to reshape the world. A systems expert whose 10 years with Microsoft spans research and product, Gehrke talks to members of the company's research community about what motivates their work and how they got where they are today.Partner Research Manager and leading developer experience expert Nicole Forsgren oversees Microsoft Research efforts to enhance software engineering effectiveness through the study of developer productivity, community, and well-being. In this episode, she discusses AI's potential impact on software engineering, what she loves about tech, and how thoughtful decision making—combined with listening to her gut—has led to opportunities as a developer, accounting professor, and founder and CEO of a startup that was eventually acquired by Google.Learn more:Nicole Forsgren at Microsoft ResearchNicole Forsgren websiteQuantifying the impact of developer experience | Microsoft Azure Blog, January 2024Yes, good DevEx increases productivity. Here is the data. | GitHub blog, January 2024Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations | Book, 2018
Jez Humble joins Dave Farley in the podcast episode where they discuss writing the award-winning book 'Continuous Delivery' - Jez' goal was to stop people wasting time by doing the wrong things, and showing people a better way of working so they don't have to spend their evenings and weekends to release new software! Dave and Jez share views on a divided SW industry, the real identity of a software developer, what mistakes they made, the importance of building teams with trust, the origins of TDD and Blue-Green deployment, current software engineering trends AND MORE.xxEqual Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ https://bit.ly/3ASy8n0Join the Continuous Delivery community and access extra perks & content! JOIN HERE ➡️ https://bit.ly/ContinuousDeliveryPatreonDORA - https://www.devops-research.com/resea... Project Aristotle
Niklaus Wirth makes his plea for lean software, PocketBase puts your entire backend in 1 file, Vanna is a Python RAG framework for accurate text-to-SQL generation, Henrik Karlsson wants you to think more about what to focus on & Calvin Wankhede shares how he built a fully offline smart home (and you should too).
Niklaus Wirth makes his plea for lean software, PocketBase puts your entire backend in 1 file, Vanna is a Python RAG framework for accurate text-to-SQL generation, Henrik Karlsson wants you to think more about what to focus on & Calvin Wankhede shares how he built a fully offline smart home (and you should too).
Niklaus Wirth makes his plea for lean software, PocketBase puts your entire backend in 1 file, Vanna is a Python RAG framework for accurate text-to-SQL generation, Henrik Karlsson wants you to think more about what to focus on & Calvin Wankhede shares how he built a fully offline smart home (and you should too).
今回は「LeanとDevOpsの科学［Accelerate］-テクノロジーの戦略的活用が組織変革を加速する」という本で紹介されている、DevOps開発と組織やビジネスのパフォーマンスとの関係に関する研究結果についてについて話しました。 LeanとDevOpsの科学［Accelerate］-テクノロジーの戦略的活用が組織変革を加速する Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations 27 capabilities https://cloud.google.com/architecture/devops?hl=ja https://engineering.visional.inc/blog/412/devops-days-tokyo-2022-after/ Your co-hosts: Tomoaki Imai, Knot, inc CTO https://twitter.com/tomoaki_imai Ryoichi Kato, Software Engineer https://twitter.com/ryo1kato
Will Larson is Chief Technology Officer at Carta. Prior to joining Carta, he was the CTO at Calm and held engineering leadership roles at Stripe, Uber, and Digg. He is the author of two foundational engineering career books, An Elegant Puzzle and Staff Engineer, and The Engineering Executive's Primer, which will be released in February. In our conversation, we discuss:• Systems thinking: what it is and how to apply it• Advice for product managers on fostering productive relationships with engineering managers• Why companies should treat engineers like adults• How to best measure developer productivity• Writing and its impact on his career• How to balance writing with a demanding job• How to develop your company values—Brought to you by DX—A platform for measuring and improving developer productivity | OneSchema—Import CSV data 10x faster | Vanta—Automate compliance. Simplify security.—Find the transcript for this episode and all past episodes at: https://www.lennyspodcast.com/episodes/. Today's transcript will be live by 8 a.m. PT.—Where to find Will Larson:• X: https://twitter.com/Lethain• LinkedIn: https://www.linkedin.com/in/will-larson-a44b543/• Website: https://lethain.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Will's background(04:12) Changes in the field of engineering(06:27) We need to stop treating engineers like children(08:32) Systems thinking(13:23) Implementing systems thinking in hiring(16:32) Engineering strategy(20:21) Examples of engineering strategies(25:08) How to get good at strategy(26:48) The importance of writing about things that excite you(32:40) The biggest risk to content creation is quitting too soon(35:24) How to make time for writing(37:41) Tips for aspiring writers(41:18) Building productive relationships between product managers and engineers(43:45) Giving the same performance rating to EMs and PMs(48:24) Measuring engineering productivity(55:53) Defining company values(01:02:10) Failure corner: the Digg rewrite(01:11:05) Will's upcoming book, The Engineering Executive's Primer(01:12:04) Lightning round—Referenced:• The end of the “free money” era: https://www.theguardian.com/technology/2023/apr/11/techscape-zirp-tech-boom• Work on what matters: https://lethain.com/work-on-what-matters/• Sheryl Sandberg to Harvard Biz Grads: “Find a Rocket Ship”: https://www.forbes.com/sites/kashmirhill/2012/05/24/sheryl-sandberg-to-harvard-biz-grads-find-a-rocket-ship/?sh=708c9a93b37a• What Is Systems Thinking?: https://www.snhu.edu/about-us/newsroom/business/what-is-systems-thinking• Introduction to systems thinking: https://lethain.com/systems-thinking/• Thinking in Systems: https://www.amazon.com/Thinking-Systems-Donella-H-Meadows/dp/1603580557• Silent Spring: https://www.amazon.com/Silent-Spring-Rachel-Carson/dp/0618249060• Writing an engineering strategy: https://lethain.com/eng-strategies/• Carta: https://carta.com/• Eric Vogl on LinkedIn: https://www.linkedin.com/in/ericvogl/• Good Strategy/Bad Strategy: The difference and why it matters: https://www.amazon.com/Good-Strategy-Bad-difference-matters/dp/1781256179• The Crux: How Leaders Become Strategists: https://www.amazon.com/Crux-How-Leaders-Become-Strategists/dp/1541701240/• How Big Things Get Done: The Surprising Factors That Determine the Fate of Every Project, from Home Renovations to Space Exploration and Everything in Between: https://www.amazon.com/How-Big-Things-Get-Done/dp/0593239512/• Technology Strategy Patterns: Architecture as Strategy: https://www.amazon.com/Technology-Strategy-Patterns-Architecture/dp/1492040878/• The Value Flywheel Effect: Power the Future and Accelerate Your Organization to the Modern Cloud: https://www.amazon.com/Value-Flywheel-Effect-Accelerate-Organization/dp/1950508579• The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win: https://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/1942788290• The Engineering Executive's Primer: Impactful Technical Leadership: https://www.amazon.com/Engineering-Executives-Primer-Impactful-Leadership/dp/1098149483• An Elegant Puzzle: Systems of Engineering Management: https://press.stripe.com/an-elegant-puzzle• Staff Engineer: Leadership beyond the management track: https://www.amazon.com/Staff-Engineer-Leadership-beyond-management-ebook/dp/B08RMSHYGG• Gergely Orosz's newsletter: https://blog.pragmaticengineer.com/author/gergely/• Leaving big tech to build the #1 technology newsletter | Gergely Orosz (The Pragmatic Engineer): https://www.lennyspodcast.com/videos/leaving-big-tech-to-build-the-1-technology-newsletter-gergely-orosz-the-pragmatic-engineer/• The art of product management | Shreyas Doshi (Stripe, Twitter, Google, Yahoo): https://www.lennyspodcast.com/videos/the-art-of-product-management-shreyas-doshi-stripe-twitter-google-yahoo/• Henry Ward on LinkedIn: https://www.linkedin.com/in/heward/• Vrushali Paunikar on LinkedIn: https://www.linkedin.com/in/vrushali-paunikar/• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google): https://www.lennyspodcast.com/how-to-measure-and-improve-developer-productivity-nicole-forsgren-microsoft-research-github-goo/• DORA: https://dora.dev/• Setting engineering org values: https://lethain.com/setting-engineering-org-values/• Digg: https://digg.com/• Kevin Rose on LinkedIn: https://www.linkedin.com/in/kevinrose/• Digg's v4 launch: an optimism born of necessity: https://lethain.com/digg-v4/• Dash Gopinath on LinkedIn: https://www.linkedin.com/in/dashgopinath/• Rich Schumacher on LinkedIn: https://www.linkedin.com/in/richschumacher/• The ALL NEW Don't Think of an Elephant!: Know Your Values and Frame the Debate: https://www.amazon.com/ALL-NEW-Dont-Think-Elephant-ebook/dp/B00NP9LHFA• Top Chef on Peacock: https://www.peacocktv.com/watch-online/tv/top-chef/5172289448907967112• Hard to work with: https://lethain.com/hard-to-work-with/—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe
This interview was recorded at GOTO Aarhus for GOTO Unscripted.gotopia.techRead the full transcription of this interview hereSam Aaron - Live Coding Musician & Creator of Sonic PiJames Lewis - Principal Consultant & Technical Director at ThoughtworksRESOURCESsonic-pi.net@sonic_pigithub.com/sonic-pi-net/sonic-piableton.com/en/linkhydra.ojack.xyzSampatreon.com/samaaron@samaarongithub.com/samaaronlinkedin.com/in/samaaronJames@boicylinkedin.com/in/james-lewis-microservicesDESCRIPTIONProgramming isn't just lines of code but a gateway to creating music and art and legends such as Ada Lovelace were proof of that. With the aim to reshape the perception of coding which has traditionally been complex and intimidating, Sam Aaron created Sonic Pi, an open-source, free-to-use platform that empowers users to create music through code. What began as a humble endeavor has grown exponentially with more than millions of downloads globally and a large number of schools integrating the tool as part of their computing curriculum to teach children how to program.Tune in to this GOTO Unscripted where Sam spoke to James Lewis about how Sonic Pi is on a mission to democratize coding and break down barriers that have hindered people from engaging with both coding and music.RECOMMENDED BOOKSHans Gruendel • Making Music with Sonic PiHans Gruendel • Learn to Program with Sonic PISimon Monk • Raspberry Pi CookbookMatthew Skelton & Manuel Pais • Team TopologiesForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily
DORA Metriken: Die Performance-Messung deines Software Development Teams bzw. die Ermittlung des Reifegrades von DevOps in deiner OrganisationSoftwareentwicklung ist ein kreativer Beruf. Jedes Projekt ist einzigartig und die geschriebenen Lines of Code sagen wenig über die dafür benötigte Zeit aus. Das Research-Programm DevOps Research and Assessment (DORA) versucht dennoch die Performance eines Software-Entwicklungs-Teams zu messen. Nicht via Lines of Code, sondern auf Basis von Aktivitäten, die Value liefern: Deployment Frequency, Lead Time for Changes, Mean Time to Recovery, Change Failure Rate und Reliability.Die Metriken selbst sind weit bekannt. Wie diese Metriken beeinflusst werden können, wer eigentlich dahinter steckt, und was die Organisation eigentlich für eine Kultur vorleben muss, damit es überhaupt zu einem positiven Ergebnis kommt, wissen viele nicht. Und genau darüber sprechen wir in dieser Episode.Bonus: AOL CDs und Metal-Musik aus Litauen**** Diese Episode wird von trivago gesponsert:trivago aus Düsseldorf sucht Verstärkung für ihr Site Reliability Engineering Team. Arbeite eng mit den Entwicklungsteams an der globalen Hotelsuchmaschine. Profitiere von einem autonomen Arbeitsumfeld und bewirb dich unter https://careers.trivago.com/sre ****Das schnelle Feedback zur Episode:
This episode is brought to you by DX—a platform for measuring and improving developer productivity.—Dr. Nicole Forsgren is a developer productivity and DevOps expert who works with engineering organizations to make work better. Best known as co-author of the Shingo Publication Award-winning book Accelerate and the DevOps Handbook, 2nd edition and author of the State of DevOps Reports, she has helped some of the biggest companies in the world transform their culture, processes, tech, and architecture. Nicole is currently a Partner at Microsoft Research, leading developer productivity research and strategy, and a technical founder/CEO with a successful exit to Google. In a previous life, she was a software engineer, sysadmin, hardware performance engineer, and professor. She has published several peer-reviewed journal papers, has been awarded public and private research grants (funders include NASA and the NSF), and has been featured in the Wall Street Journal, Forbes, Computerworld, and InformationWeek. In today's podcast, we discuss:• Two frameworks for measuring developer productivity: DORA and SPACE• Benchmarks for what good and great look like• Common mistakes to avoid when measuring developer productivity• Resources and tools for improving your metrics• Signs your developer experience needs attention• How to improve your developer experience• Nicole's Four-Box framework for thinking about data and relationships—Find the full transcript at: https://www.lennyspodcast.com/how-to-measure-and-improve-developer-productivity-nicole-forsgren-microsoft-research-github-goo/#transcript—Where to find Nicole Forsgren:• Twitter: https://twitter.com/nicolefv• LinkedIn: https://www.linkedin.com/in/nicolefv/• Website: https://nicolefv.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Nicole's background(07:55) Unpacking the terms “developer productivity,” “developer experience,” and “DevOps”(10:06) How to move faster and improve practices across the board(13:43) The DORA framework(18:54) Benchmarks for success(22:33) Why company size doesn't matter (24:54) How to improve DevOps capabilities by working backward(29:23) The SPACE framework and choosing metrics(32:51) How SPACE and DORA work together(35:39) Measuring satisfaction(37:52) Resources and tools for optimizing metrics(41:29) Nicole's current book project(45:43) Common pitfalls companies run into when rolling out developer productivity/optimizations(47:42) How the DevOps space has progressed(50:07) The impact of AI on the developer experience and productivity(54:04) First steps to take if you're trying to improve the developer experience(55:15) Why Google is an example of a company implementing DevOps solutions well(56:11) The importance of clear communication(57:32) Nicole's Four-Box framework(1:05:15) Advice on making decisions (1:08:56) Lightning round—Referenced:• Chef: https://www.chef.io/• DORA: https://dora.dev/• GitHub: https://github.com/• Microsoft Research: https://www.microsoft.com/en-us/research/• What is DORA?: https://devops.com/what-is-dora-and-why-you-should-care/• Dustin Smith on LinkedIn: https://www.linkedin.com/in/dustin-smith-b0525458/• Nathen Harvey on LinkedIn: https://www.linkedin.com/in/nathen/• What is CI/CD?: https://about.gitlab.com/topics/ci-cd/• Trunk-based development: https://cloud.google.com/architecture/devops/devops-tech-trunk-based-development• DORA DevOps Quick Check: https://dora.dev/quickcheck/• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• The SPACE of Developer Productivity: https://queue.acm.org/detail.cfm?id=3454124• DevOps Metrics: Nicole Forsgren and Mik Kersten: https://queue.acm.org/detail.cfm?id=3182626• How to Measure Anything: Finding the Value of Intangibles in Business: https://www.amazon.com/How-Measure-Anything-Intangibles-Business/dp/1118539273/• GitHub Copilot: https://github.com/features/copilot• Tabnine: https://www.tabnine.com/the-leading-ai-assistant-for-software-development• Nicole's Decision-Making Spreadsheet: https://docs.google.com/spreadsheets/d/1wItAODkhZ-zKnnFbyDERCd8Hq2NQ03WPvCfigBQ5vpc/edit?usp=sharing• How to do linear regression and correlation analysis: https://www.lennysnewsletter.com/p/linear-regression-and-correlation-analysis• Good Strategy/Bad Strategy: The difference and why it matters: https://www.amazon.com/Good-Strategy-Bad-difference-matters/dp/1781256179/• Designing Your Life: How to Build a Well-Lived, Joyful Life: https://www.amazon.com/Designing-Your-Life-Well-Lived-Joyful/dp/1101875321• Ender's Game: https://www.amazon.com/Enders-Game-Ender-Quintet-1/dp/1250773024/ref=tmm_pap_swatch_0• Suits on Netflix: https://www.netflix.com/title/70195800• Ted Lasso on AppleTV+: https://tv.apple.com/us/show/ted-lasso• Never Have I Ever on Netflix: https://www.netflix.com/title/80179190• Eight Sleep: https://www.eightsleep.com/• COSRX face masks: https://www.amazon.com/COSRX-Advanced-Secretion-Hydrating-Moisturizing/dp/B08JSL9W6K/—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe
This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereMauricio Salatino - Author of "Platform Engineering on Kubernetes" Thomas Vitale - Software Architect & Author of "Cloud Native Spring in Action"RESOURCESMauricio@salaboylinkedin.com/in/salaboysalaboy.comThomas@vitalethomasgithub.com/ThomasVitalelinkedin.com/in/vitalethomasthomasvitale.comDESCRIPTIONPlatform Engineering on Kubernetes accelerates development of cloud-based systems with vibrant open source tools of the Kubernetes ecosystem. You'll use powerful open source projects like Helm, Tekton, Knative, and Crossplane to automate your projects from testing through delivery. Learn how to package services, build and deploy services to a Kubernetes cluster, and combine different tools to solve the complex challenges of CD in a cloud native environment.* Book description: © manning.comThe interview is based on the book "Platform Engineering on Kubernetes".RECOMMENDED BOOKSMauricio Salatino • Platform Engineering on KubernetesMauricio Salatino, Mariano De Maio & Esteban Aliverti • Mastering JBoss Drools 6Thomas Vitale • Cloud Native Spring in ActionDavid Farley • Modern Software EngineeringDave Farley & Jez Humble • Continuous DeliveryGene Kim, Jez Humble, Nicole Forsgren, Patrick Debois & John Willis • The DevOps HandbookForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsJohn Arundel & Justin Domingus • Cloud Native DevOps with KubernetesTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily
This week, Dan Neumann is joined by Mike Guiler to discuss the benefits of Agility, including employee satisfaction, predictable delivery, and speed to market among others. Key Takeaways: Agility leads to employee satisfaction since every Team member is connected to the purpose of the work. Sustainable pace is enabled by Agile Methods Agile done well eliminates the “death march” Deliver slices of value Deliver the most valuable items first Agile delivery is not “all-or-nothing,” enabling us to decide what we can release without Predictable delivery is mostly assured with Agile, and even when the mark is missed it can be adjusted back in a brief period. Reduction of Waste The Increment is inspected frequently We learn from what we deliver You can stop and pivot when going down a path that is not what the customer needs Make change easier Validate assumptions early Reduce Risk Don't build the whole thing before we deliver it Reduce risk by gradually exposing your features to users versus an “all-or-nothing” release Incremental deliveries reduce risk by validating assumptions. You get real customer feedback. Speed to Market Deliver the right things, reduce waste, and get a slice delivered! Do not expect that your developers will “code faster” Faster Return on Investment Generate revenue with small slices Decide when to stop investing further in a product When you decide to transform your business outcomes, you need to consider the benefits you are striving for when you make decisions within your organization. Keep the end goal in mind at all times. We want to be efficient instead of effective. Collaboration works wonders; a Team is more resilient and efficient when collaborating. Some people are not ready to work in a Team; they need space and time to gradually start feeling more comfortable with teaming. Scrum is often perceived as having a lot of meetings when in reality, the meetings required are the minimum necessary to keep the Team aligned toward achieving the common purpose. Mentioned in this Episode: Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren Ph.D., Jez Humble, and Gene Kim Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!
This interview was recorded for GOTO Unscripted at GOTO Copenhagen.gotopia.techRead the full transcription of this interview hereJessica Cregg - Information Technology Operations engineer at CybSafeJulian Wood - Developer Advocate at AWSDESCRIPTIONWhat are the technologies that one should leverage to build modern, scalable, and flexible applications?Julian Wood, developer advocate at AWS Serverless, talks with Jessica Cregg, previously a developer advocate at LaunchDarkly, now an information technology operations engineer at CybSafe about the mindset and tools required to build scalable software without over-engineering a solution.RECOMMENDED BOOKSAdzic & Korac • Running ServerlessScott Patterson • Learn AWS Serverless ComputingPeter Sbarski • Serverless Architectures on AWSGregor Hohpe • The Software Architect ElevatorHenney & Monson-Haefel • 97 Things Every Software Architect Should KnowMatthew Skelton & Manuel Pais • Team TopologiesForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily
Is development becoming obsolete? We invited Miku and Pauliina to talk about software engineering — how the roles have been shaping, what the current trends and challenges are, and how we can shape the future of our profession. Tune in and join our semi-practical, semi-philosophical conversation.GuestsPauliina started her career as a communications consultant, but slowly life took her back to her childhood hobby - coding. She moved all the way to Australia to study at a coding bootcamp and has now been working as a software developer for over 5 years. She still thinks it was the best decision of her life. What she loves most about coding is how tangible it feels to build software one piece at a time and how rewarding it is to solve problems with technology. In her free time,, you will find her on a yoga mat or wandering in a forest.With nearly 20 years of experience, Mikael is a passionate, future-oriented technology leader with a cultivated interest in cutting-edge technologies and the methodologies of creating exceptional digital products. While he currently has limited time to actually code at work, he still does it as a hobby. Mikael is a fan of functional programming and loves exploring new tech, surfing, and cooking.Mikael's core expertise and interests are the design of technology organizations, technology strategy, business, and digital strategy, innovation, software and enterprise architectures, modern process methodologies, modern leadership, self-organization, systems thinking, data, and AI.HostAnna Fröblom is a great programmer, problem-solver, hobby photographer, lego enthusiast, and simply a nice person.Guest HostRoss Langley is a human-centered designer from Reaktor Helsinki. He loves helping teams excel in challenging environments. Ross shines when he does concept modeling, validates ideas, or makes celebrity impressions. References:Malan, Pais, Skelton: Team Topologies: Organizing Business and Technology Teams for Fast FlowCagan: Inspired: How to Create Tech Products Customers Love (Silicon Valley Product Group)Forsgren, Humble, Kim: Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology OrganizationsGoogle Cloud 2022: Announcing the 2022 Accelerate State of DevOps Report: A deep dive into securityAbout ReaktorFork Pull Merge Push is a podcast created for developers by developers. It's brought to you by Reaktor, a creative technology partner for forward-thinking companies and societies, based in Helsinki, New York, Amsterdam, Stockholm, Lisbon, and Tokyo.We at Reaktor are looking for exceptional talent and new friends. Check our open positions and apply now!
Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. When Peter joined this project, the teams had been working on it for years and had little to show for it. Thanks to the CTO at the company, the new team which Peter coached, was able to focus on small, valuable increments to deliver the back-office system the company needed. Listen to this segment, to hear how we can help teams go from BIG BANG thinking to incremental delivery, a crucial need for Agile teams. In this segment, we refer to the Toyota Kata and the PDCA cycle. Featured Book of the Week: Accelerate by Forsgren et al. In Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Forsgren et al., Peter found evidence-based support for many of the approaches, and practices used by Agile teams and Agile organizations. In this segment, we talk about the DORA metrics, and how to focus software development on business results. Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome! About Peter Janssens Peter built a long career in agile coaching and training, and worked in leadership positions leading a PO team, and recently became CTO in a SAAS product company. Peter loves all conversations on effectiveness of team decisions, but he quickly realized that being responsible is different from being a coach. As a leader there is the challenge of sticking to the same foundations when dealing with delivery pressure. You can link with Peter Janssens on LinkedIn.
In episode 104 of the Teaching Python podcast, Kelly and Sean discuss their wins of the week and announce they are co-chairing the PyCon US Education Summit in April 2023. The episode features a segment on book recommendations, where Kelly and Sean share some of their recent reads that they found particularly useful for Python programmers. One of the recommended books is "The Missing ReadMe" which is a guide for new engineers to understand and navigate open-source projects. Another book recommended is "Fundamentals of Artificial Intelligence" which is a comprehensive introduction to the field of artificial intelligence and its underlying algorithms and techniques. They also recommend "Accelerate: The Science of Lean Software and DevOps" which is a practical guide with industry data about the benefits of DevOps. "Fluent Python" is another book they recommend which is a guide to writing better and more idiomatic Python code. Finally, they recommend the new edition of "Python Crash Course" by Eric Matthes which is a fast-paced, thorough introduction to Python programming for beginners. It's a great episode for anyone who is interested in learning more about the Python programming language, and the PyCon Education Summit, as well as reading some great books on the topic. The episode is available on the Teaching Python podcast website, and the links to the books can also be found there.
John Cutler writes the popular and beloved product newsletter The Beautiful Mess. For many years, he was a Product Evangelist at Amplitude, which led him to meeting and working with a large number of product teams around the world. Through this role, he gained unique insight into how the best product teams operate. In today's episode, John reflects on leaving his role at Amplitude, and explains the attributes that the top 1% of product teams share. We also go deep into some of his favorite frameworks and discuss the best way to apply these frameworks to your work. We also unpack skills like product sense and product mindset, and what he's planning in his new role at Toast.—Find the full transcript here: https://www.lennyspodcast.com/what-differentiates-the-highest-performing-product-teams-john-cutler-amplitude-the-beautiful-mess/#transcript—Thank you to our wonderful sponsors for supporting this podcast:• Merge—A single API to add hundreds of integrations into your app: http://merge.dev/lenny• Eppo—Run reliable, impactful experiments: https://www.geteppo.com/• Vanta—Automate compliance. Simplify security: https://vanta.com/lenny—Where to find John Cutler:• Twitter: https://twitter.com/johncutlefish• LinkedIn: https://www.linkedin.com/in/johnpcutler/• Newsletter: https://cutlefish.substack.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—Referenced:• Amplitude: https://amplitude.com/• The North Star Playbook: https://info.amplitude.com/north-star-playbook• Craig Daniel on LinkedIn: https://www.linkedin.com/in/craigmdaniel/• Working Backwards: Insights, Stories, and Secrets from Inside Amazon: https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595• AppFolio: https://www.appfolio.com/• High Leverage Product Evangelism: https://cutlefish.substack.com/p/high-leverage-product-evangelism• Satya Nadella on LinkedIn: https://www.linkedin.com/in/satyanadella/• The Culture Map: Breaking Through the Invisible Boundaries of Global Business: https://www.amazon.com/Culture-Map-Breaking-Invisible-Boundaries/dp/1610392507• Innovation Labs: https://innovationlabs.com/• BEES: https://mybeesapp.com/• Marty Cagan on Lenny's Podcast: https://www.lennysnewsletter.com/p/the-nature-of-product-marty-cagan#details• Sooner Safer Happier: Antipatterns and Patterns for Business Agility: https://www.amazon.com/Sooner-Safer-Happier-Patterns-Antipatterns/dp/1942788916• Teresa Torres on LinkedIn: https://www.linkedin.com/in/teresatorres/• Andrew Huberman on Instagram: https://www.instagram.com/hubermanlab/?hl=en• TBM 49/52: Pyramid of Leadership Self/Other Awareness: https://cutlefish.substack.com/p/tbm-4952-pyramid-of-leadership-selfother• ChatGPT: https://chat.openai.com/chat• How to Measure Anything: Finding the Value of Intangibles in Business: https://www.amazon.com/How-Measure-Anything-Intangibles-Business-ebook/dp/B00INUYS2U• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations: https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339• User Story Mapping: Discover the Whole Story, Build the Right Product: https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/B08TZGKKF2• Build with Maggie Crowley podcast: https://podcasts.apple.com/us/podcast/build-with-maggie-crowley/id1445050691• One Knight in Product podcast: https://www.oneknightinproduct.com/index.html#page-top• Sunny Bunnies on Netflix: https://www.netflix.com/title/81286920• Booba on Netflix: https://www.netflix.com/title/81011059• Toast: https://pos.toasttab.com/• Drift: https://www.drift.com/John's list of high-performing people worth following:• Dr. Cat Hicks (@grimalkina) https://www.linkedin.com/in/drcathicks/ • Stephanie Leue https://www.linkedin.com/in/stephanie-leue/• Amy Edmondson (@AmyCEdmondson) https://www.linkedin.com/in/amedmondson/• Dominica DeGrandis (@dominicad) https://www.linkedin.com/in/dominicadeg/• Courtney Kissler https://www.linkedin.com/in/courtney-kissler-0930681/• Christina Wodtke (@cwodtke) https://www.linkedin.com/in/christinawodtke/• Matthew Skelton https://www.linkedin.com/in/matthewskelton/• Heidi Helfand (@heidihelfand): https://www.linkedin.com/in/heidihelfand/—In this episode, we cover:(00:00) What is a product evangelist? John's unique role at Amplitude(05:50) John's reflections and feelings on leaving Amplitude(17:28) What John's doing next(18:52) John's newsletter: The Beautiful Mess(27:49) What do the top 1% of product teams have in common?(40:08) Different ways companies are successful, and why anyone can improve(45:55) Investing in people vs. investing in processes(48:49) The importance of culture and values(49:59) Global company cultures: the individualist vs. the collectivist (55:55) Why it's hard to make changes in large companies(58:49) How to view frameworks(1:01:02) The spectrum of performance in big and small companies(1:05:27) Examples of high-performing people who work outside of Silicon Valley(1:09:02) The skill of product management(1:11:35) The value of learning a bit about everything(1:13:46) Why do people often underestimate the loops available at their company(1:16:20) Chronic vs. acute issues at companies(1:18:07) Unpacking the skills behind product sense and product mindset(1:20:44) A place for people without the traditional meritocracy mindset(1:22:38) John's writing process and what he plans on writing about next(1:27:52) How to use ChatGPT for learning and levity(1:31:56) Lightning Round—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe
محاور الحلقة (00:00) - مقدمة (01:18) - التدريس المنزلي - Homeschooling (22:37) - التعليم في المغرب (40:11 - تربية الأطفال (01:13:33) - الإسلام و الهجرة (01:21:48) - البساطة في الحياة (01:25:29) - البرمجة (01:51:31) - ثقافة شركة تقنية (02:08:40) - مشروع زربيتي (02:16:09) - شبكات التواصل (02:18:15) - المنتخب المغربي في كأس العالم 2022 (02:29:30) - كتب تستحق القراءة (02:32:32) - توصيات الضيوف (02:36:35) - نصيحة لصغار السن (02:39:04) - رأي في كاس أتاي بودكاست (02:41:36) - المغزى من الحياة (02:45:54) - كلمات ختامية النسخة المصورة: https://youtu.be/9-BN2ojV7TI الموقع الرسمي: https://www.slimane.io/podcast/abdelhaq-el-aibi Patreon: https://www.patreon.com/lectorem Paypal: https://paypal.com/paypalme/lectorem Website: https://www.slimane.io/podcast Instagram: https://www.instagram.com/lectoremtv Facebook: https://www.facebook.com/lectoremtv Twitter: https://twitter.com/lectoremtv Short clips: https://www.youtube.com/channel/UCzlcGOWb8GF5tP8rEbLhECQ أرسل سؤالك إلى lectorem.questions@gmail.com للإعلان و التواصل المهني lectorem.business@gmail.com عبد الحق العيبي هو مهندس برمجيات متمرس بالمكتب الشريف للفوسفاط و أب لثلاثة أطفال. Abdelhaq El Aibi is a CTO on-demand, a solutions architect at OCP, and a father of three kids. الكتب المقترحة - Adieu, la dyslexie! - The 7 Habits of Highly Effective People. - Start With Why. - Accelerate: The Science of Lean Software and DevOps. - The Lean Startup. - The Software Architect Elevator. #45 Abdelhaq El Aibi — Homeschooling, Parenting, Programming, Islam, Minimalism, Code culture, World Cup
This interview was recorded for the GOTO Book Club.gotopia.tech/bookclubRead the full transcription of the interview hereTitus Winters - Principal Software Engineer at Google and Co-Curator of "Software Engineering at Google"Matt Kulukundis - Senior Staff Software Engineer at GoogleDESCRIPTIONWhat's the difference between programming and software engineering?Join Titus Winters, co-curator of “Software Engineering at Google”, and Matt Kulukundis while they approach the lessons learned by software engineering teams at Google in establishing the right practices for writing sustainable code in a safe environment. Discover what Google is still trying to improve on and what software decisions are difficult to undo.The interview is based on Titus' co-curated book "Software Engineering at Google"RECOMMENDED BOOKSTitus Winters, Tom Manshreck & Hyrum Wright • Software Engineering at GoogleForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOpsGeorge Fairbanks • Just Enough Software ArchitectureFred Brooks Jr. • The Mythical Man-MonthKim Scott • Just WorkDouglas R. Hofstadter • Gödel, Escher, BachDouglas R. Hofstadter • I Am a Strange LoopAlasdair MacIntyre • After VirtueN. K. Jemisin • The Fifth SeasonBecky Chambers • Wayfarers SeriesKen Liu • The Dandelion DynastyDavid Farley • Modern Software EngineeringMartin Kleppmann • Designing Data-Intensive ApplicationsZhamak Dehghani • Data MeshDev InterruptedWhat the smartest minds in engineering are thinking about, working on and investing in.Listen on: Apple Podcasts Spotify Manufacturing MattersInsights and interviews discussing trends, innovations, and advanced automation technologyListen on: Apple Podcasts SpotifyTwitterLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily
Pavel's operational excellence platform can be found and tried out for free at : http://vsoptima.com Pavel's InfoQ article on Dynamic Value Stream Mapping: https://www.infoq.com/articles/dynamic-value-stream-mapping/?itm_source=infoq&itm_campaign=user_page&itm_medium=link Pavel's article in Software Development Times: https://sdtimes.com/author/pavel-azaletskiy/ Pavel's Twitter is: https://twitter.com/AzaletskiyPavel Here is a sandbox using the value stream platform: Screen shots from the sandbox: TOUT Agile Grande
Pavel's operational excellence platform can be found and tried out for free at : http://vsoptima.com Pavel's InfoQ article on Dynamic Value Stream Mapping: https://www.infoq.com/articles/dynamic-value-stream-mapping/?itm_source=infoq&itm_campaign=user_page&itm_medium=link Pavel's article in Software Development Times: https://sdtimes.com/author/pavel-azaletskiy/ Pavel's Twitter is: https://twitter.com/AzaletskiyPavel Here is a sandbox using the value stream platform: https://app.vsoptima.com/diagram/6c055f51-5be5-4076-9097-e1ef3a875f6e Screen shots from the sandbox: Mentioned on the show: Value streams can show the you *cost* of not doing the upgrade to an M1 Mac for iOS development: Interested in Agile at your big company but struggling to resolve headaches? Is trying to do the usual Scrum or Kanban templates causing a lot of problems when more than one team is involved?Are you having trouble getting your management to align around what you see as obvious solutions?Do you want to learn about Systems Thinking and Whole Product Focus but find what you're reading is uninspiring and boring?The business novel, Agile Grande, will teach you these skills through dramatic story telling. Scrum Master Kartar takes a job to improve a logistics company's adaptability. But efforts to scale Agile practices are being blocked by Mr. Cherneski, a vice president who's organized the company into siloed pigeon holes in order to secretly make millions with a dark web shipping service. Kartar's life is in danger. He goes underground. A spy agency hunts Kartar.... The following concepts are covered in this dramatic story: scaling Scrum with LeSS, systems thinking, organizational design, systems modeling, and how to develop a transformation plan that your organization can actually do. Get a pre-release copy of Agile Grande for free at LeanPub.com.
Pavel's operational excellence platform can be found and tried out for free at : http://vsoptima.com Pavel's InfoQ article on Dynamic Value Stream Mapping: https://www.infoq.com/articles/dynamic-value-stream-mapping/?itm_source=infoq&itm_campaign=user_page&itm_medium=link Pavel's article in Software Development Times: https://sdtimes.com/author/pavel-azaletskiy/ Pavel's Twitter is: https://twitter.com/AzaletskiyPavel Here is a sandbox using the value stream platform: Screen shots from the sandbox: Mentioned on the show: Value streams can show the you *cost* of not doing the upgrade to an M1 Mac for iOS development: TOUT Agile Grande
Pavel's value stream platform can be found and tried out for free at : http://vsoptima.com Pavel's InfoQ article on Dynamic Value Stream Mapping: https://www.infoq.com/articles/dynamic-value-stream-mapping/?itm_source=infoq&itm_campaign=user_page&itm_medium=link Pavel's article in Software Development Times: https://sdtimes.com/author/pavel-azaletskiy/ Pavel's Twitter is: https://twitter.com/AzaletskiyPavel Mentioned on the show: Value streams can show the you *cost* of not doing the upgrade to an M1 Mac for iOS development:
Quais os caminhos possíveis para profissionais sênior em tecnologia?
7 Wastes of Lean & Software (PMP, Agile Training)
Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course War & Peace & IT Pocket Guide Recommend Reading The New Economics by Dr. Deming The High-Velocity Edge by Dr. Steven Spear The Fifth Discipline by Peter Senge The Toyota Way by Jeffery Liker The Toyota Kata by Mike Rother The Principles of Product Development Flow by Donald Reinersten Making Work Visible by Dominica de Grandis Modern Software Engineering by Dave Farley The DevOps Handbook by Gene Kim, Jez Humble, Patrick de Bois, John Willis The Phoenix Project by Gene Kim, Kevin Behr, and George Stafford Team Topologies by Matthew Skelton, Manuel Pais Recommended Listening Small Batches #50: Introducing Dr. Deming with John Willis Small Batches #39: The High-Velocity Edge (Part One) Small Batches #65: Systems Thinking Small Batches #53: The Toyota Way Small Batches #60: The Principles of Product Development Flow Small Batches #59: Making Work Visible Small Batches #63: Modern Software Engineering Small Batches #1: The Three Ways of DevOps Small Batches #16: The Story of Parts Unlimited Small Batches #18: Team Topologies Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website
In this episode the panel talks to Danny Hawkins - CTO at Quiqup - and his team's journey at Quiqup with Elixir. Danny explains how some of the first things Quiqup built were using Elixir and how they then left Elixir behind in favor of TypeScript, only to come back to Elixir.The panel considers how these choices rarely are purely driven by technological qualities but instead have to factor in cultural- and knowledge-aspects of a team, and how a top-down dictated technology decision - even if there are good reasons for it - can be harmful to a team's morale.Get in touch with Danny via email! Click here.Sponsors Top End Devs Coaching | Top End Devs Links Quiup A Perfect Pickup Choice of Technology at Quiqup EventStoreDB - the event database for today's fast moving, event-driven systems GitHub - commanded/commanded: Use Commanded to build Elixir CQRS/ES applications Elixir for Programmers GitHub - quiqupltd/libelection: Library to perform leader election in a cluster of containerized Elixir nodes Connect Livebook to Elixir in Kubernetes Twitter: @dannyhawkins Picks Danny- Onward - The ultimate VR Mil-Sim tactical shooter Danny- Treadmill for Standing Desk (Danny has a Sparnod) Danny- Accelerate: The Science of Lean Software and DevOps Sascha- KanDDDinsky - The art of business software
The Twenty Minute VC: Venture Capital | Startup Funding | The Pitch
Daniel Yanisse is the co-founder and CEO of Checkr, a leading HR technology company, currently valued at $5 billion. During the journey, Daniel has raised over $679M for Checkr from some of the best including Accel, Bond, Coatue, GV, Elad Gil and IVP to name a few. Prior to Checkr, Daniel was a software engineer and helped develop prototypes of the Mars Rover for NASA. Daniel has been recognized in Forbes “30 Under 30” and recently Checkr was recognized by Forbes as one of America's best start-up employers. In Today's Episode with Daniel Yanisse You Will Learn: 1.) The Origins of Checkr: The $5BN Company How did Daniel come to co-found Checkr? What was the a-ha moment? How did Daniel's experience with his prior company impact how he thought about building Checkr? What does Daniel know now that he wishes all first-time founders knew when they started? 2.) Hiring 101: What are the single biggest hiring mistakes Daniel made in the early days of Checkr? How does Daniel structure his interview process for new candidates today? How has it changed? How does Daniel test for ego and humility in the interview process? How does Daniel approach giving feedback today? How has it changed over time? What does Daniel believe is the right way to let someone go? How long does one give a team member who is not performing? 3.) Fundraising 101: How does Daniel advise founders going out to raise today in the challenging market conditions? What terms should founders optimize for? What terms should they not optimize for? What are the single biggest mistakes Daniel sees founders make when raising? What does Daniel wish he had done differently with Checkr's raises? What was the hardest raise for Checkr? Why was it so hard? What was the outcome? 4.) Going into Enterprise: Why does Daniel believe they went into enterprise too soon? What was the result of this? How does Daniel advise founders on when is the right time to go into enterprise? What changes in both your company and your product when moving to enterprise? Items Mentioned in Today's Episode with Daniel Yanisse: Daniel's Favourite Book: Accelerate: The Science of Lean Software and Devops: Building and Scaling High Performing Technology Organizations
This week, I'm joined by Urban Hafner for a wide-ranging discussion on management roles, autism, programming organization structure, sci-fi and fantasy books, programming books, the reasons behind high developer turnover, and bass guitar.The Pragmatic ProgrammerAccelerate: The Science of Lean Software and Dev OpsCynefinExpanding Beyond PodcastUrban Hafner.comUrban Hafner on Twitter
In this episode, we'll start by separating out Agile from DevOps, and then bringing in CI/CD pipelines. We'll also discuss DevSecOps and some of the best practices in engineering that a developer can adopt. We'll also give an overview of what a CI/CD pipeline looks like, what a pipeline stage is, what a pipeline's purpose is, and how it is related to DevOps. As a bonus, I talk about tools for Static Code Analysis (SCA) and Static Application Security Testing (SAST)! We'll also touch on Test Driven Development (TDD). ----- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Storytime with Dad Podcast
In this episode software craftsman Luke Elliott and I discuss what makes great software engineering, excellent software engineers and effective teams… We argue that understanding and delivering value is really all good software engineering is about. And that engineers understanding the customer is possibly the biggest difference between organisations who deliver value and those whose don't; and that this is best achieved by combining people who deeply understand the customers like product owners with engineers who deeply care (about value and consequently the customer). We discuss what makes high performing teams, and touch on the challenge of hiring great engineers. We make a detour chatting about the importance of TDD and Pair Programming and whether they are a cult, and why some love and some hate these practices, but why, ultimately XP practices like these ultimately the ability to deliver value at pace, reliably and sustainably. We briefly rant about TLAs and why one should always clarify acronyms (or rather not have them in the first place) and what it means, if a team doesn't feel sufficiently safe to ask questions (and what one can do to build the needed psychological safety). We close by discussing that the art of architecture is knowing what to do now and what to defer, why David Knuth is right in saying that ‘premature performance optimisation is the root of all evil' and what this means for startup who are in bootstrapping mode and must avoid overly early gold-plating and over-engineering while not impeding future scaling. … Luke is a software craftsman with deep experience in lean and agile software development. He believes that great software is crafted by great teams, and that building great teams is challenging and rewarding work. He has lead successful teams across public and private sector, bluechips and startups, in diverse industries including finance, healthcare and energy. He is a keen proponent of lean and agile approaches, XP and believes in CI/CD, fast feedback loops, outcome over output, and product thinking. He avoids big design up front, command-and-control management, and blame cultures. He is currently Director of Engineering at OakNorth Bank. Luke is currently hiring software engineers of all stripes and if you are interested in working like Luke describes, contact him at luke.elliott@oaknorth.co.uk. He can be contacted via revlucio@gmail.com or Linkedin: https://www.linkedin.com/in/lukeelliott/ – More information at https://www.theburnup.com This podcast produced by Burn Up Media Ltd under under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. Further Information at: https://creativecommons.org/licenses/by-nc-nd/4.0/
If you write software, you are probably collaborating with other developers. If you are collaborating, then you probably need to isolate your code and then merge it together when you're done. So what are some of the best-practices for managing this? My favorite is trunk-based development, but that name probably doesn't mean what you think it means! In this episode, we dive into branching strategies and trunk-based development. We also touch on test automation, CI/CD pipelines, agility, and DevOps practices. We'll also talk about anti-patterns or "worst practices" that some companies adopt because they are risk averse. Ironically, many of today's software delivery practices increase risk rather than decrease it! Hear my take and compare it to your own, then Tweet me (@tweetsofgrant) and tell me where our views differ! ----- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Google's Guidebook on Trunk-Based Development Other Visualizations of Trunk-Based Development
Show Notes Dit is een speciale aflevering. De eerste CodeKlets "live" opname met publiek erbij. We houden een panel discussie over de "Staat van Programmeren". Het panel bestaat uit, als je onze podcast trouw hebt geluisterd, 3 bekende gezichten: Redmar Kerkhoff, Dennis Doomen & Johnny Dongelmans. Het panel leggen we een aantal stellingen en vragen voor, om een beetje een beeld te krijgen hoe het staat met de "Staat van Programmeren" in 2022. Dit panel is mede mogelijk gemaakt door Aviva Solutions. We mochten daar te gast zijn op het Aviva Impulse event. Met hosts Kishen Simbhoedatpanday - LinkedIn Twitter Saber Karmous - LinkedIn Twitter Johnny Dongelmans - LinkedIn Redmar Kerkhoff Twitter - @rjkerkhoff LinkedIn Dennis Doomen Twitter - @ddoomen Continuous Improver Fluent Assertions Coding Guidelines for C# Onderwerpen 00:00:11 Intro 00:01:28 Nieuwe ontwikkelaars kunnen het beste beginnen met … 00:05:02 Programmeren van een moderne applicatie in 2022 is te complex 00:10:44 Welke principes pas je toe in je toolstack om de situatie simpel te houden? 00:16:32 De enige manier om oplossingen te bouwen is middels “the cloud” 00:21:24 Over welke technologie zijn jullie op dit moment heel enthousiast? 00:26:52 We zijn over de piek heen van de hype cycle als het aankomt op nieuwe programmeertalen/platforms 00:30:14 Wat zou je willen weten over de taal/platform van degene die naast je zit? 00:35:42 Vragen vanuit het publiek 00:36:18 Vraag van Wim The 00:40:28 Vraag van Frank Bakker 00:45:23 Vraag van Peter Hesseling 00:48:07 Outro Tips Redmar Accelerate: The Science of Lean Software and Devops Team Topologies CodeKlets links CodeKlets CodeKlets Nieuwsbrief CodeKlets Slack CodeKlets Twitter CodeKlets op Vriend van de Show
In part two of this two-part episode on The DevOpsHandbook, Second Edition, Gene Kim speaks with coauthors Dr. Nicole Forsgren and Jez Humble about the past and current state of DevOps. Forsgren and Humble share with Kim their DevOps aha moments and what has been the most interesting thing they've learned since the book was released in 2016. Jez discusses the architectural properties of the programming language PHP and what it has in common with ASP.NET. He also talks about the anguish he felt when Mike Nygard's book, Release It!, was published while he was working on his book, Continuous Delivery. Forsgren talks about how it feels to see the findings from the State of DevOps research so widely used and cited within the technology community. She explains the importance of finding the link between technology performance and organizational performance as well as what she's learned about the importance of culture and how it can make or break an organization. Humble, Forsgren, and Kim each share their favorite case studies in The DevOps Handbook. ABOUT THE GUEST(S) Dr. Nicole Forsgren and Jez Humble are two of five coauthors of The DevOps Handbook along with Gene Kim, Patrick Debois and John Willis. Forsgren, PhD, is a Partner at Microsoft Research. She is coauthor of the Shingo Publication Award-winning book Accelerate: The Science of Lean Software and The DevOps Handbook, 2nd Ed., and is best known as lead investigator on the largest DevOps studies to date. She has been a successful entrepreneur (with an exit to Google), professor, performance engineer, and sysadmin. Her work has been published in several peer-reviewed journals. Humble is co-author of Lean Enterprise, the Jolt Award-winning Continuous Delivery, and The DevOps Handbook. He has spent his career tinkering with code, infrastructure, and product development in companies of varying sizes across three continents, most recently working for the US Federal Government at 18F. As well as serving as DORA's CTO, Jez teaches at UC Berkeley. YOU'LL LEARN ABOUT Projects Jez and Gene worked on together before The DevOps Handbook came out. What life is like for Jez as a site reliability engineer at Google and what he's learned. The story behind his DevOps aha moment in 2004, working on a large software project involving 70 developers. The architectural properties of his favorite programming language PHP, what it has in common with ASP.NET, and the importance of being able to get fast feedback while building something. The anguish that Jez felt when Mike Nygard's book, Release It!, came out, wondering if there was still a need for the book he was working on, which was Continuous Delivery. “Testing on the Toilet” and other structures for creating distributed learning across an organization and why this is important to create a genuine learning dynamic. What Dr. Forsgren is working on now as Partner of Microsoft Research. Some of Dr. Forsgren's goals as we work together on the State of DevOps research and how it feel to have those findings so widely used and cited within the technology community. The importance of finding the link between technology performance and organizational performance and why it probably was so elusive for at least 40 years in the research community. What Dr. Forsgren has learned about the importance of culture, how it can make or break an organization, and the importance of great leadership. RESOURCES Personal DevOps Aha Moments, the Rise of Infrastructure, and the DevOps Enterprise Scenius: Interviews with The DevOps Handbook Coauthors (Part 1 of 2: Patrick Debois and John Willis) The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, Second Edition, by Gene Kim, Patrick Debois, John Willis, Jez Humble, and Dr. Nicole Forsgren Nudge: Improving Decisions About Health, Wealth, and Happiness by Richard H. Thaler and Cass R. Sunstein Nudge vs Shove: A Conversation With Richard Thaler The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps by Kevin Behr, Gene Kim and George Spafford FlowCon Elisabeth Hendrickson on the Idealcast: Part 1, Part 2 Cloud Run Beyond Goldilocks Reliability by Narayan Desai, Google Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation by Jez Humble and David Farley Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers) by Michael T. Nygard DevOps Days On the Care and Feeding of Feedback Cycles by Elisabeth Hendrickson at FlowCon San Francisco 2013 Bret Victor Inventing on Principle by Bret Victor Media for Thinking the Unthinkable Douglas Engelbart and The Mother of All Demos 18F Pain Is Over, If You Want It at DevOps Enterprise Summit - San Francisco 2015 Goto Fail, Heartbleed, and Unit Testing Culture by Mike Bland Do Developers Discover New Tools On The Toilet? by Emerson Murphy-Hill, Edward Smith, Caitlin Sadowski, Ciera Jaspan, Collin Winter, Matthew Jorde, Andrea Knight, Andrew Trenk and Steve Gross PDF Study: DevOps Can Create Competitive Advantage DevOps Means Business by Nicole Forsgren Velasquez, Jez Humble, Nigel Kersten and Gene Kim Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD, Jez Humble, and Gene Kim DevOps Research and Assessment (DORA) on Google Cloud GitLab Inc. takes The DevOps Platform public Paul Strassmann The Idealcast with Dr. Ron Westrum: Part 1, Part 2 Building the Circle of Faith: How Corporate Culture Builds Trust at Trajectory Conference 2021 The Truth About Burnout: How Organizations Cause Personal Stress and What to Do About It by Christina Maslach and Michael P. Leiter Maslach Burnout Inventory Understanding Job Burnout at DevOps Enterprise Summit - Las Vegas 2018 Understanding Job Burnout at DevOps Enterprise Summit - London 2019 Workplace Engagement Panel at DevOps Enterprise Summit - Las Vegas 2019 Expert Panel - Workplace Engagement & Countering Employee Burnout at DevOps Enterprise Summit - London 2019 The Idealcast with Trent Green Kelly Shortridge's tweets about Gitlab S-1 TIMESTAMPS [05:22] Intro [05:34] Meet Jez Humble [10:19] What Jez is working on these days [15:56] What inform his book, “Continuous Delivery” [24:02] Assembling the team for the project [26:30] At what point was PHP an important property [31:56] The most surprising thing since the DevOps Handbook came out [35:07] His favorite pattern that went into the DevOps Handbook [43:40] What DevOps worked on in 2021 [44:46] Meet Dr. Nicole Forsgren [50:32] What Dr. Forsgren is working on these days [52:18] What it's like working at Microsoft Research [55:58] The response to the state of DevOps findings [59:18] The most surprising finding since the findings release [1:05:59] Her favorite pattern that influence performance [1:08:49] How Dr. Forsgren met Dr. Ron Westrum [1:11:06] The most important thing she's learned in this journey [1:14:46] Her favorite case study in the DevOps Handbook [1:19:12] Dr. Christina Maslach and work burnout [1:20:46] More context about the case studies [1:25:32] The Navy case study [1:29:04] Outro
This interview was recorded at GOTO Copenhagen 2021 for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/the-future-of-devopsPJ Hagerty - Head of DevRel at MattermostHanna Park - Workplace Community Manager at MattermostDESCRIPTIONThe pandemic and remote work have changed the direction of the DevOps movement. Find out what lies ahead with Hanna Park, community manager at Mattermost, and PJ Hagerty, head of developer relations at Mattermost, in their discussion at GOTO Copenhagen 2021.RECOMMENDED BOOKSForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOps • https://amzn.to/3tCz1xOJohn Arundel & Justin Domingus • Cloud Native DevOps with Kubernetes • https://amzn.to/3hKZvI5Wynne, Hellesoy & Tooke • The Cucumber Book • https://amzn.to/3tEUINJRobert C. Myers • Essential Test-Driven Development • https://amzn.to/2Xc8ZWaRoy Osherove • The Art of Unit Testing • https://bit.ly/3obiKNBEric Ries • The Lean Startup • https://amzn.to/396fOvaRonnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• https://amzn.to/3c4HmmLhttps://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
Dragan Stepanović is our guest, and he brings his heuristic: “Continuous code reviews enable higher team's throughput”. We dive into Dragan's research on how async code reviews affect the quality and throughput of teams that create and maintain software. He also shares how his research challenged some of his assumptions, and we finalise discussing his experiences bringing his research to management. Dragan recommends the following resources: The Principles of Product Development Flow from Donald G. Reinertsen The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win from Gene Kim, Kevin Behr and George Spafford The Goal from Eliyahu M. Goldratt Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation from Jez Humble and Dave Farley Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations from Nicole Forsgren, Jez Humble and Gene Kim Dragan (@d_stepanovic) is based in Berlin and currently works as a principal engineer at HelloFresh. Typically on the search for better ways of working, exploring ends of the spectrums, and helping teams and organisations try out counter-intuitive ideas that initially don't make a lot of sense but end up as completely opposite of that. It's been a long time since he fell in love with eXtreme Programming, Domain-Driven Design, and software as a craft (founder of Software Crafting Serbia community). In the last couple of years, he enjoys endless discussions connecting the Theory of Constraints, Systems Thinking, Lean and socio-technical topics.
Avsnitt 25 av UTVECKLA är här! Vi har haft förmånen att bli gästade av Martin Fredriksson som jobbar med Innovation Lead på Consid. Dagens ämne är Assemblerprogrammering och Multicloud. Vad innebär egentligen dessa två? Och vad är fördelarna kontra nackdelarna med dem? Frågor som dessa besvaras i dagens samtal med Martin. Trevlig lyssning! Höjdpunkter från avsnittet: [06:50] - Vem är Martin Fredriksson? [08:30] - Martin har precis fått igång en Commodore 64 som han ska använda för att bygga upp ett spel med hjälp av Assemblerprogrammering. Här berättar han mer om detta projekt. [15:00] - Vilka är fördelarna kontra nackdelarna med assemblerprogrammering? [26:25] - Vad är multicloud för något? Och varför använder man sig av detta? [40:45] - Hur kostnadseffektivt är det egentligen med multicloud? [42:20] - Hur kommer man igång med sin multicloud-lösning? [47:15] - Så här ser framtiden ut inom assemblerprogrammering [49:45] - Hur påverkar forskningen våra molntjänster? [52:40] - Martin ger tips på två böcker inom programmering! Länkar till böcker: Accelerate - the Science of Lean Software and Devops: Building and Scaling High Performing Technology Organizations Measure what matters: The Simple Idea that Drives 10x Growth
Neste episódio, Bruno Pereira explica sobre 3 indicadores retirados do livro Accelerate: The Science of Lean Software and DevOps que são muito úteis na operação de produtos digitais. Essas métricas auxiliam a melhorar a eficiência do processo de desenvolvimento assim como a usabilidade ao cliente final. Melhora a experiência para o time de desenvolvimento e também ao usuário. Em nosso produto OnePlatform é possível mensurar métricas de produto e desenvolvimento do seu produto digital. Para saber mais acesse nosso site: https://elven.works E para ficar por dentro das novidades sobre computação em nuvem, IOT, devOps e Observabilidade, se inscreva em nosso blog: https://blog.elven.works
Um papo onde debatemos sobre o atual estado da arte do Devops, quais são as ferramentas e melhores práticas quentes do momento e também fazemos aquela velha pergunta: devops é cargo ou cultura? Participantes: Paulo Silveira, o host que também é dev e ops na AluraRenan Capaverde, diretor de engenharia no NubankAlan Ghelardi, leade software engineer no time de continuous integration do NubankDaniel Artine, analista de desenvolvimento na Stone AgeRoberta Arcoverde, que acha que todo ano deveria ter um episódio sobre as novidade de DevopsMaurício "Balboa" Linhares, que acha que devops perdeu o significado Links: Formação DevopsDevOps Research and AssessmentAccelerate: The Science of Lean Software and DevOpsThe State of Devops 2019 Produção e conteúdo: Alura Cursos de Tecnologia - https://www.alura.com.br === Caelum Escola de Tecnologia - https://www.caelum.com.br/ Edição e sonorização: Radiofobia Podcast e Multimídia
Um papo onde debatemos sobre o atual estado da arte do Devops, quais são as ferramentas e melhores práticas quentes do momento e também fazemos aquela velha pergunta: devops é cargo ou cultura? Participantes: Paulo Silveira, o host que também é dev e ops na AluraRenan Capaverde, diretor de engenharia no NubankAlan Ghelardi, leade software engineer no time de continuous integration do NubankDaniel Artine, analista de desenvolvimento na Stone AgeRoberta Arcoverde, que acha que todo ano deveria ter um episódio sobre as novidade de DevopsMaurício "Balboa" Linhares, que acha que devops perdeu o significado Links: Formação DevopsDevOps Research and AssessmentAccelerate: The Science of Lean Software and DevOpsThe State of Devops 2019 Produção e conteúdo: Alura Cursos de Tecnologia - https://www.alura.com.br === Caelum Escola de Tecnologia - https://www.caelum.com.br/ Edição e sonorização: Radiofobia Podcast e Multimídia
If you find yourself listening to this, and you can relate to having some waste problems in your company, it's going to be one of seven things. We have called them the seven wastes of software development. To find out more about those, please go back and listen to Episode 82. Today, however, you'll find out how to solve for each of the seven wastes; more specifically, you'll learn about creating a lean software toolkit.
Charles Flatt is joining the podcast today! He has been a software developer since 1994 and has helped over a dozen organizations succeed on over fifty projects, both small and large. Charles has an unusual breadth of business and personal experience from foodservice and retail to music, business management, hardware installation, and of course, software development. In this episode, Charles talks about his learning as a developer and some of his successes, big lessons, and key takeaways from the course of his career. He shares actionable advice for developers, teams, and organizations on how to improve; his favorite resources and books for further learning; the metrics that matter the most; and what he sees as being the key components of what makes a DevOps organization successful. Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [1:00] About The Azure DevOps Podcast, Clear Measure, and Jeffrey’s offer to speak at virtual user groups. [1:24] Clear Measure is hiring! Be sure to check out the link in the show notes. [1:34] About today’s guest, Charles Flatt! [1:57] Jeffrey welcomes Charles to the podcast. [2:34] Charles shares his career journey before software development and how he began his career in software. [6:49] Charles speaks about where he has worked and what he has been working on in the last decade. [11:48] Charles shares some of the big lessons and key takeaways from the course of working on over fifty projects in software development. [18:21] Charles and Jeffrey discuss their favorite books on DevOps and give their recommendations on what you should be reading as a developer today. [20:50] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [21:22] What Charles sees as needing to change within an organization in order to become more successful. [23:01] Charles gives some actionable advice on how to begin improving as a developer, as a team, and as an organization. [28:06] Charles and Jeffrey discuss the metrics that matter the most. [29:18] Jeffrey and Charles discuss the importance of continuous integration and what it really means to do continuous integration. [32:32] Charles recommends some go-to resources to check out after today’s podcast! [34:33] Jeffrey thanks Charles for joining the podcast! Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Charles Flatt’s LinkedIn Azure DevOps Podcast Ep. 33: “Rockford Lhotka on Software Architecture” Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD The Phoenix Project (A Novel About IT, DevOps, and Helping Your Business Win), by Gene Kim The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Continuous Integration: Improving Software Quality and Reducing Risk, by Paul M. Duvall, Steve Matyas, and Andrew Glover Good Habits, Bad Habits: The Science of Making Positive Changes That Stick, by Wendy Wood Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs, by John Doerr Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.
Τι επιλογές έχει ένας προγραμματιστής για την εξέλιξη του σε μία σύγχρονη εταιρεία. Από junior μέχρι VP. Δήλωσε συμμετοχή στο Laravel, React ή Docker #workshop: http://bit.ly/sn-workshops-y Ή πες μας τι workshop θες: bit.ly/WhatWorkshopSN Δες το video -> https://youtu.be/EieMyOU4Dfo Accelerate: The Science of Lean Software and Devops: Building and Scaling High Performing -> https://amzn.to/35fzv29
In March 2020, as our world was shrinking and words like 'lockdown' and 'zoom-bombing' were becoming a reality, we recorded and aired SPaMCAST 597. Paul Laberge, Susan Parente, Jo Ann Sweeney, John Voris, and I talked about how we could create or preserve interactions leading to serendipity. Remote working was new for many people. This week we discuss what went well and what have we learned from nearly a year of working remotely. As the editor of the SPaMCAST it is my great pleasure to reconvene a group of people that have such great insight into people. The discussion is full of great ideas to improve remote and hybrid working environments, but most of all it is full of ideas to help respect people in tough times or not. Panelist Bios Jo Ann Sweeney FCIM FIIC MCIPR is an engagement and communication consultant. Typically, she acts as change management lead on complex programs, facilitating the development of effective engagement, training, and communication strategies, and then assisting as the strategies are implemented. Clients value her deep understanding of audiences. Jo Ann is known for clarifying the complex and for persuading key stakeholders to get involved and actively support change. You are welcome to download a complimentary copy of Jo Ann’s guide How to Explain Change in 8 Easy Steps at https://freeguide.explaining-change.com/ Contact Jo Ann at jo.ann@sweeneycomms.com John Voris is the current leader of AgilePhilly, the local user group in the Philadelphia area for Scrum, Kanban, and Lean Software. (www.AgilePhilly.com) His day job is working on financial applications for Crown Cork & Seal, an essential company with over 100 years of manufacturing food and beverage cans. Prior to Crown, John was an independent software consultant for 30+ years helping both small companies and Fortune 100 large companies with both applications and operating systems. Reach out on LinkedIn: linkedin.com/in/john-voris-7b20525 With more than 30 years in the information technology industry, Paul Laberge – CGI Director Consulting-Expert, has a wide range of experience providing IT project management. He enjoys coaching leaders in deploying business technology solutions. His experience in organizational change management spans many different lifecycles including transitions to Agile frameworks (RUP, XP, Scrum, SAFe, Nexxus, LeSS) and incorporating Lean (Kanban) methodologies. Reach out on LinkedIn: linkedin.com/in/paullaberge Susan Parente is a Principal Consultant at S3 Technologies, LLC and a University Professor at multiple Universities. Mrs. Parente is an author, mentor and professor focused on risk management, traditional and Agile project management. Her experience is augmented by her Masters in Engineering Management with a focus in Marketing of Technology from George Washington University, DC, along with a number of professional certifications. Ms. Parente has 23+ years’ experience leading software and business development projects in the private and public sectors, including a decade of experience implementing IT projects for the DoD. Contact Susan at parente.s3@gmail.com Re-Read Saturday News This week the re-read of Great Big Agile, An OS for Agile Leaders by Jeff Dalton dives into Chapter 3. Chapter 3 describes the Providing Performance Circle. Providing is all about the logistics and the culture of the organization. If I were drawing a Venn Diagram, providing and leading (Chapter 2) have a significant overlap. Remember, buy a copy and read along. This week’s installment can be found at www.tomcagley.com/blog Previous installments: Week 1: Re-read Logistics and Front Matters - https://bit.ly/3mgz9P6 Week 2: The API Is Broken - https://bit.ly/2JGpe7l Week 3: Performance Circle: Leading - https://bit.ly/2K3poWy Next SPaMCAST The next Software Process and Measurement Cast will feature our interview with Ted Harrington, author of HACKABLE: How to Do Application Security Right. Security is not something that you can easily remedy after the fact - it needs to be part of the conversation before you write one line of code. Ted provides insights for developers, C-level executives, and product owners. If you have not bought a copy buy two copies (https://amzn.to/386w7Hr), one for you and one for your boss. Then listen to the interview together.
https://www.leanblog.org/391My guests for Episode #391 are Mary Poppendieck and Tom Poppendieck, the authors of books including Lean Software Development: An Agile Toolkit, Implementing Lean Software Development, and The Lean Mindset: Ask the Right Questions.In the episode, we'll hear their thoughts on Lean as "a way of thinking that values people" and how teamwork, problem solving, and customer focus are integral to Lean -- in software or otherwise. How can we build capabilities for problem solving ("producing people") and how can we "learn how to learn"?Questions, Links, and MoreHow did you first discover Lean? How did you come to see the potential applications to software development?You published Lean Software Development in 2003 -- how do you define that term “Lean” and what does it mean to you?How has your view of Lean evolved over those 17 years?What have you learned about Lean / TPS from visiting Japan?Your 2013 book is called "The Lean Mindset" -- as the subtitle says, asking the right questions is important... why so? How do we know what the right questions are?2009 -- Leading Lean Software Development -- another provocative subtitle... "results are not the point" -- what do you mean?LeanEssays.comTheir website: http://poppendieck.com/Mary on Twitter
In der ersten Folge unseres CTO-Specials haben wir Jesper Richter-Reichhelm zu Gast. Er ist CTO der Heritas GmbH und spricht mit uns über die Erfahrungen aus seiner Zeit als Softwareentwickler bei Jamba, Head of Engineering bei Wooga und CTO bei Outfittery. Jesper erzählt uns davon, wie er – begonnen als Entwickler – bei der Skalierung des Teams von Wooga von 10 auf 300 Personen geholfen hat. Als späterer Head of Engineering organisierte er die Arbeit von rund 90 EntwicklerInnen und lernte viel darüber, was es beim Firmenwachstum zu beachten gibt. Welche Strategien sind bei Einstellungsprozessen erfolgversprechend und wie etabliert man eine Firmenkultur, die auf Feedback und Eigenständigkeit fußt? Haben alle EntwicklerInnen das Zeug zum CTO? Diese und weitere Fragen rund um die Rolle eines Chief Technology Officers klären wir in dieser Folge. Bleibt bis zum Schluss dran, um wertvolle Tipps von Jesper zu erhalten, die er nicht nur (angehenden) CTOs, sondern allen MitarbeiterInnen eines Technologie-Unternehmens mitgeben möchte. Zum Einstieg in das Thema Management im Softwarebereich empfiehlt er das Buch “Accelerate: The Science of Lean Software and Devops”. Im CTO-Special holt sich Dennis Unterstützung durch Dominik, einem der Gründer der Lotum GmbH. Gemeinsam sprechen sie mit CTOs über Erwartungen, Anforderungen und Erfahrungen, welche die Rolle mit sich bringt.Schreibt uns! Was haltet ihr von dem neuen Format? Habt ihr Feedback, das ihr gern mit uns teilen wollt? Schickt uns eure Themenwünsche und euer Feedback. podcast@programmier.bar Folgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. Twitter Instagram Facebook Meetup YouTube Musik: Hanimo
Today's guest is Jonathan Cutrell - Director of Engineering at PBS & host of the Developer Tea podcast.In this episode we discuss:How and why he started Developer TeaThe why behind things we do as developersWhat drives the actions we takeThe psychology of remote workingHierarchies of developer rolesand much much more!
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website. A team Oskar worked with, was complaining about the meetings and wanted to stop some of those. Over time, the team members started not showing up, or showing up and not participating actively in the meeting. As the team was delivering, no one else saw this was a problem, but Oskar knew that this was not a team, it was just a group of individuals. In this episode, we talk about how to motivate a team and the importance of having a Vision that brings the team members together. In this segment, we refer to the FREE Create A Compelling Product Vision e-course. Featured Book of the Week: Accelerate by Nicole Forsgren In Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren, Oskar found a book that helped him explain the Agile mindset to technical people. He also understood the role of DevOps in an Agile organization. The biggest takeaway? Listen in to learn what was Oskar’s biggest takeaway. In this segment, we also talk about the #NoEstimates book, and how that influenced Oskar’s career. About Oskar Collin Oskar is a former software developer who became a passionate agile coach and Scrum master. He did so mainly because he was better at helping teams working together than building software. He loves experiments and questioning the status quo. He is passionate about helping teams build digital products and deliver value continuously. You can link with Oskar Collin on LinkedIn and connect with Oskar Collin on Twitter.
Developer Operations is a data driven endeavor, but how do you avoid drowning in noise? In this episode of Adventures in DevOps, the panelists discuss the metrics that matter, how we approach separating information from noise, and when a simple number fails to tell the whole story. Panelists Jeff Groman Henry Jewkes Scott Nixon Sponsors CacheFly Links CodePipeline Dashboard DevOps 043: Testing in Production with Talia Nassi SlIs, SLOs, SLAs, oh my! The Unicorn Project The Phoenix Project Accelerate: The Sciene of Lean Software and DevOps Picks Scott Nixon: Alone Follow on Social Media: Facebook: Adventures in DevOps Twitter: @DevOpsPodcast
Developer Operations is a data driven endeavor, but how do you avoid drowning in noise? In this episode of Adventures in DevOps, the panelists discuss the metrics that matter, how we approach separating information from noise, and when a simple number fails to tell the whole story. Panelists Jeff Groman Henry Jewkes Scott Nixon Sponsors CacheFly Links CodePipeline Dashboard DevOps 043: Testing in Production with Talia Nassi SlIs, SLOs, SLAs, oh my! The Unicorn Project The Phoenix Project Accelerate: The Sciene of Lean Software and DevOps Picks Scott Nixon: Alone Follow on Social Media: Facebook: Adventures in DevOps Twitter: @DevOpsPodcast
Sponsored by Linode Panelists Allen "Gunner" Gunn | Justin Dorfman | Pia Mancini | Richard Littauer Guest Tobie Langel Show Notes Welcome to Sustain! On today’s episode, we have special guest, Tobie Langel, the Founder of UnlockOpen, from Geneva, Switzerland. Tobie tells us all about UnlockOpen and what he does there. He tells us how he focuses on convincing companies that they need to contribute back to Open Source. Other topics we will talk about are DevOps culture, prototype JavaScript framework not being updated since 2015, which Tobie extensively explains what happened, as well as speaking about lessons to be learned and things we need to be aware of. There is so much great advice and stories shared on this episode. Download it now! [00:01:19] Tobie tells us about UnlockOpen and what he does. [00:02:30] Richard wants to know how do you get in the door as a consultant to try to talk to people about how they should use Open Source and how do you pitch that to people that don’t know what Open Source is? [00:08:04] Tobie discusses how he focuses on convincing companies that they need to contribute back to Open Source. Pia wonders if Tobie thinks we’re making progress towards cultural changes within the audience? [00:12:10] Allen asks Tobie if he’s advancing the notion of DevOps as a gateway drug for all of this open culture. Tobie mentions a book he’s reading called, Accelerate, that_ _talks about the benefits of DevOps culture to companies from a business perspective. [00:14:13] Justin wants to know where Tobie got his kind of background and he also wonders about project abandonment, and prototype JavaScript framework hasn’t been updated since 2015. So, what happened there and what lessons could be learned? [00:24:06] Tobie speaks about learning from history, about lessons to be learned, and things we have to be aware of. [00:26:06] Tobie mentions how he’s a huge fan of DHH and Basecamp and he gives some great advice that he’s learned on focusing on things that matter long term. Justin and Richard also have some positive advice and stories to share as well. [00:35:25] Richard makes an awesome statement here about being resilient. [00:36:20] Tobie tells us where we can find him to learn more about him. Spotlight [00:38:03] Justin’s spotlight is our first bonus podcast episode (#41) with Dave Gandy, and we discussed Font Awesome 6, the donut diet, commitments, and more. Check it out! ☺ [00:42:23] Allen’s spotlight is Open Tech Fund. [00:38:56] Richard’s spotlight is Aral Balkan, a cyborg rights activist. [00:39:17] Toby’s spotlight is a book by Nadia Eghbal called, Working in Public: The Making and Maintenance of Open Source Software. Quotes “It boils down to bottom line and top line. To some degree it’s more than that, obviously, culture, brand, making people feel happy to work in a company. All of those are critical for a company.” [00:10:45] “And we are at the point where we need to cross the chasm. So maybe move that from being something that is essentially something adopted by a few really performant companies at the helm of this effort and move that across to become more mainstream. [00:16:47] “And so the funny thing is I essentially learned JavaScript by reading the source code because there was no documentation and I started contributing to the library by writing documentation for it.” [00:17:44] “It took a lot of time for Sam to realize that he was burning out and just couldn’t spend the time that was needed to give more authority to other people on the project.” [00:21:58] “There was a lot of energy, and people are ready to do a lot of things for the rocket ship because you also benefit personally quite a bit when you’re investing your time in a rocket ship.” [00:25:19] “This goes right to the heart of what we’re trying to talk about here. And so I think one of the things that I’m really picking up from what you’re saying is that it’s better to dedicate yourself towards an ideology of working well in the open, of working with other people, of trying to consistently not just stay ahead of the curve, but work in a way that what you do will matter later.” [00:34:20] “At the same time you could carry that comparison even further kind of ad absurdum, like everything’s the same, because we all need to eat and we all get tired and we all get sleepy and we all get hungry, we’re all kind of anxious and we have to work with other people and what wears kind of annoying and it’s pretty tough.” Links Tobie Langel Twitter (https://twitter.com/tobie?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) UnlockOpen (https://unlockopen.com/) Sustain Podcast-Episode 41: The Donut Diet, Commitments. and More Awesomeness with Dave Gandy (https://fireside.fm/s/fxw-Bcan+HH3L5owT) Open Technology Fund (https://www.opentech.fund/) Aral Balkan (https://ar.al/) [Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal](https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862/ref=sr12?dchild=1&keywords=working+in+public%3A+the+making&qid=1592942530&sr=8-2) [Accelerate: The Science of Lean Software and DevOps:Building and Scaling High Performing Technology Organizations by Nicole Forsgren, PhD](https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr12?dchild=1&keywords=accelerate&qid=1592942345&sr=8-2) Credits Produced by Justin Dorfman (https://www.justindorfman.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Ad Sales by Eric Berry Special Guest: Tobie Langel.
Robby speaks with Ryan Cromwell, Technical Director at Sparkbox. They discuss the importance of simplifying deployments, technical debt in the client-services industry, and the traits to seek when hiring software engineers for client-services based work.Helpful LinksFollow Ryan on TwitterSparkbox[Book] Accelerate: The Science of Lean Software and DevOpsMichael Feathers on Maintainable[Book] Working Effectively with Legacy Code
OPIS W tym odcinku rozmawiamy w troche innej formie - o technologiach chmurowych z punktu widzenia konkretnego success story. A moim gościem jest Wojciech Gawroński NOTATKI Kim jest Wojtek Gawroński - 1 min Chmura pozwala działać zwinniej - 3 min Czy korzystanie z usług jest tańsze czy droższe - 11 min Co AWS oferuje dla tego typu projektów - 19 min Co chmura zmienia względem tradycyjnego podejścia - 25 min Jakie umiejętności są wg Ciebie potrzebne aby umiejętnie korzystać z chmury - 36 min Jak zmieniają się role, stanowiska wymagania i umiejętności - 50 min Gdzie można znaleść Wojtka w sieci - 65 min LINKI Pattern Match: https://pattern-match.com Blog: https://pattern-match.com/blog From Monolith to Serverless: https://services.pattern-match.com/from-monolith-to-serverless Blog AWS Gentleman: https://awsgentleman.com Twitch (cotygodniowe spotkania online na temat AWS): https://www.twitch.tv/afronski LinkedIn: https://www.linkedin.com/in/afronski Instagram: https://www.instagram.com/afronsky Cytat Leslie Lamporta o systemach rozproszonych. Fallacies of Distributed Computing. The 12 factor App. AWS Modern Application Development. AWS Data Flywheel i nasz artykuł o tym. The Art of Capacity Planning The Phoenix Project Accelerate: The Science of Lean Software and DevOps
Der Product-Life-Cycle digitaler Produkte (Quellen) 1. Geburt (Luca Hehl) # Ciroth, A., & Franze, J. LCA of an Ecolabeled Notebook. Consideration of Social and Environmental Impacts Along the Entire Life Cycle.(GreenDeltaTC, 2011). # Helms, H., et al. Weiterentwicklung und vertiefte Analyse der Umweltbilanz von Elektrofahrzeugen. https://www.umweltbundesamt.de/publikationen/weiterentwicklung-vertiefte- analyse-der (2016). # Bauer, C., et al. The Environmental Performance of Current and Future Passenger Vehicles: Life Cycle Assessment based on a Novel Scenario Analysis Framework. Applied Energy 157, 871–883 (2015). 2. Leben (Julian Neuweger) Klumpp, D. Energiefresser Internet: Die Ökobilanz eines Mausklicks. https://www.swr.de/odysso/oekobilanz-des-internets/-/id=1046894/did=21791748/nid=1046894/1jsu4be/index.html (2018) Andrae, A., & Edler, T., On Global Electricity Usage of Communication Technology: Trends to 2030. Challenges 6, 117–157 (2015) und Statista (2017). https://de.statista.com/statistik/daten/studie/151356/umfrage/stromverbrauch-ausgewaehlter-laender-weltweit/ Shehabi, A., et al. The Energy and Greenhouse-gas Implications of Internetvideo Streaming in the United States. Environmental Research Letters 9 (2014). Cisco. VNI Global Fixed and Mobile Internet Traffic Forecasts. Hintemann, R., & Hinterholzer, S. Smarte Rahmenbedingungen für Energie-und Ressourceneinsparungen (Kurzstudie im Auftrag des Bund für Umwelt und Naturschutz Deutschland e.V. (BUND)). https://bund.net/kurzstudie_smarthome (2018). 3. Tod (Mike Rademacher) Wikipedia. Software Bloat. https://en.wikipedia.org/wiki/Software_bloat (2019). Wirth, N. A Plea for Lean Software. Computer 28, 64–68 (1995). UNEP. Waste Crimes, Waste Risks: Gaps and Challenges In the Waste Sector: UNEP Report (2015).
Marc Fletcher graduated with a PhD in Physics (Quantum Computing) from the University of Cambridge and has been the CTO at Echobox since 2014. Whilst not jumping out of planes or competing for GB as a professional skydiver, he’s particularly passionate about maximising productivity in high performance cross-functional technology teams.Resources:Data first remote working perspective - https://medium.com/echobox/in-search-of-higher-engineering-productivity-a-data-first-remote-working-perspective-ab4a47f4417aNicole Forsgren - Author of Accelerate: The Science of Lean Software and DevOps, and is best known for her work measuring the technology process and as the lead investigator on the largest DevOps studies to date.Echobox are hiring - https://careers.echobox.comGithub Organization - https://github.com/ebxAWS resources for remote working - https://aws.amazon.com/blogs/aws/working-from-home-heres-how-aws-can-help/
The SPaMCAST 597 features a special panel of leaders discussing working from home now and after the initial reaction to being remote has worn off. One of the important points that we discussed was the need to make space for intentional serendipity. The panel is composed of Paul Laberge, Susan Parente, John Voris, Jo Ann Sweeney, and your host. Panelist Bios Jo Ann Sweeney FCIM FIIC MCIPR is an engagement and communication consultant. Typically, she acts as change management lead on complex programmes, facilitating development of effective engagement, training, and communication strategies and then assisting as the strategies are implemented. Clients value her deep understanding of audiences. Jo Ann is known for clarifying the complex and for persuading key stakeholders to get involved and actively support change. You are welcome to download a complimentary copy of Jo Ann’s guide How to Explain Change in 8 Easy Steps at https://freeguide.explaining-change.com/ Contact Jo Ann at jo.ann@sweeneycomms.com John Voris is the current leader of AgilePhilly, the local user group in the Philadelphia area for Scrum, Kanban, and Lean Software. (www.AgilePhilly.com) His day job is working on financial applications for Crown Cork & Seal, an essential company with over 100 years of manufacturing food and beverage cans. Prior to Crown, John was an independent software consultant for 30+ years helping both small companies and Fortune 100 large companies with both applications and operating systems. Reach out on LinkedIn: linkedin.com/in/john-voris-7b20525 With more than 30 years in the information technology industry, Paul Laberge – CGI Director Consulting-Expert, has a wide range of experience providing IT project management. He enjoys coaching leaders in deploying business technology solutions. His experience in organizational change management spans many different lifecycles including transitions to Agile frameworks (RUP, XP, Scrum, SAFe, Nexxus, LeSS) and incorporating Lean (Kanban) methodologies. Reach out on LinkedIn: linkedin.com/in/paullaberge Susan Parente is a Principal Consultant at S3 Technologies, LLC and a University Professor at multiple Universities. Mrs. Parente is an author, mentor and professor focused on risk management, traditional and Agile project management. Her experience is augmented by her Masters in Engineering Management with a focus in Marketing of Technology from George Washington University, DC, along with a number of professional certifications. Ms. Parente has 23+ years’ experience leading software and business development projects in the private and public sectors, including a decade of experience implementing IT projects for the DoD. Contact Susan at parente.s3@gmail.com Re-Read Saturday News This week we tackle Chapter 9 of Crucial Conversations: Tools for Talking When Stakes Are High, Second Edition by Patterson, Grenny, McMillan, Switzler. The subtitle of this chapter is a fair summary of the ideas in the chapter: how to turn crucial conversations into action and results. Let’s face it if you don’t do anything with what you learn in a crucial conversation you are wasting a lot of value. Week 1 - Logistics, Forewards, and Preface - http://bit.ly/2wls1Mq Week 2 - Chapter 1: What’s a crucial conversation? And who cares? - http://bit.ly/3a7Kivp Week 3 – Chapter 2: The Power of Dialogue – http://bit.ly/3aO4cMa Week 4 - Chapter 3: Start With Heart - http://bit.ly/2UbJizK Week 5 - Learn To Look - https://bit.ly/3djnnPX Week 6 - Make It Safe - https://bit.ly/39p4Xu4 Week 7 - Master my Stories - https://bit.ly/2V1DJUZ Week 8 - State My Path - https://bit.ly/2XtqTSr Week 9 - Explore Others’ Paths - https://bit.ly/2ViOGD5 Week 10 - Move to Action - https://bit.ly/2y1ddUb We are starting the poll for the next book in the re-read series. Crucial Conversations has two more chapters and an afterword left which means we have approximately three weeks to choose what we will read next. I am going to try something a little different this time by focusing on books I’ve read in late 2019 early 2020 and that I carry around with me when I am working. One exception is the inclusion of the runner up from our last poll. If you do not have a copy or have tossed it at someone during a crucial conversation, it is time to buy a copy. Please use the link https://amzn.to/34RuZ6V (using the link helps support the blog and podcast). Next SPaMCAST SPaMCAST 598 will feature our essay titled Recognizing A Toxic Meeting Culture. Just because you are meeting remotely doesn’t mean meeting culture has been reset. We will also return to the QA Corner with Jeremy Berriault.
One of the recurring themes we talk about a lot on the a16z Podcast is how software changes organizations, and vice versa... More broadly: it’s really about how companies of all kinds innovate with the org structures and tools that they have. But we've come a long way from the question of "does IT matter" to answering the question of what org structures, processes, architectures, and roles DO matter when it comes to companies -- of all sizes -- innovating through software and more. So in this episode (a re-run of a popular episode from a couple years ago), two of the authors of the book Accelerate: The Science of Lean Software and DevOps, by Nicole Forsgren, Jez Humble, and Jean Kim join Sonal Chokshi to share best practices and large-scale findings about high performing companies (including those who may not even think they’re tech companies). Nicole was co-founder and CEO of Dora, which was acquired by Google in December 2018; she will soon be joining GitHub as VP of Research & Strategy. Jez was CTO at DORA; is currently in Developer Relations at Google Cloud; and is the co-author of the books The DevOps Handbook, Lean Enterprise, and Continuous Delivery.
Show Notes and Links Flo and Julian talk with Michael Engel who went from teaching operating systems fundamentals in Germany to researching sustainability at the NTNU in Norway. Discuss the episode in Matrix room #ukvly:matrix.org or on Freenode IRC #ukvly. Send feedback to podcast@ukvly.org or via Twitter. Resources Dirty ships Plea for a Holistic Analysis of the Relationship between Information Technology and Carbon-Dioxide Emissions emscripten Fabrice Bellard’s x86 emulator written in JavaScript Purism, makers of the Librem laptops and the [Librem 5 phone](https://puri.sm/products/librem-5/ Openmoko Michael Engel’s blog Project Oberon: The Design of an Operating System and Compiler by Niklaus Wirth Plea for Lean Software by Niklaus Wirth School of Niklaus Wirth Computer Latency 1977-2007 Oberon FPGA-system DIGITAL FX!32:Combining Emulation and Binary Translation
In this episode of Adventures in DevOps the pane interviews Adam Nowak. Adam is a part of the DevOps team at Netguru. He joins the panel today to share his DevOps transformation story. Adam starts by explaining the title he chose for today’s episode. He also shares his definition of DevOps. Adam explains the age-old story of a misunderstood DevOps team that was overworked and underappreciated. The organization grew but the DevOps team didn’t scale with it, leaving them with piles of tickets and everyone else wondering what was taking so long. The panel commiserates with Adam and shares some of their own similar stories. Reaching out to others to help solve the problem, Adam found that many DevOps teams had and are experiencing the same problem. He found help from others in the DevOps space and recommended books. His team started by making their work more visible. To do this they streamlined their communication and published documentation. Next, they made more focused goals. Instead of trying to do everything and never meeting their goals they chose a couple things to work on and focused on that. Another change they made was to diversify their meetings, projects, and initiatives; they brought in people from all the teams to collaborate, making the projects even better. The panel discusses the importance of empathy in the workplace and in life. Most people are trying their best and probably have a reason for doing the things that they are doing. Instead of treating others as if they are incompetent, talk them and discuss the reasons behind their actions and decisions. Panelists Nell Shamrell-Harrington Charles Max Wood Guest Adam Nowak Sponsors CacheFly Links How we killed DevOps by creating a dedicated DevOps team | Adam Nowak The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win Making Work Visible: Exposing Time Theft to Optimize Work & Flow The Goal: A Process of Ongoing Improvement The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Switch: How to Change Things When Change Is Hard https://www.facebook.com/Adventures-in-DevOps-345350773046268/ Picks Charles Max Wood: Holiday Inn White Christmas The MaxCoders Guide To Finding Your Dream Developer Job Nell Shamrell-Harrington: The Mandalorian Rust in Motion Adam Nowak: Why We Sleep: Unlocking the Power of Sleep and Dreams Jabra Elite 85h Wireless Noise-Canceling Headphones
In this episode of Adventures in DevOps the pane interviews Adam Nowak. Adam is a part of the DevOps team at Netguru. He joins the panel today to share his DevOps transformation story. Adam starts by explaining the title he chose for today’s episode. He also shares his definition of DevOps. Adam explains the age-old story of a misunderstood DevOps team that was overworked and underappreciated. The organization grew but the DevOps team didn’t scale with it, leaving them with piles of tickets and everyone else wondering what was taking so long. The panel commiserates with Adam and shares some of their own similar stories. Reaching out to others to help solve the problem, Adam found that many DevOps teams had and are experiencing the same problem. He found help from others in the DevOps space and recommended books. His team started by making their work more visible. To do this they streamlined their communication and published documentation. Next, they made more focused goals. Instead of trying to do everything and never meeting their goals they chose a couple things to work on and focused on that. Another change they made was to diversify their meetings, projects, and initiatives; they brought in people from all the teams to collaborate, making the projects even better. The panel discusses the importance of empathy in the workplace and in life. Most people are trying their best and probably have a reason for doing the things that they are doing. Instead of treating others as if they are incompetent, talk them and discuss the reasons behind their actions and decisions. Panelists Nell Shamrell-Harrington Charles Max Wood Guest Adam Nowak Sponsors CacheFly Links How we killed DevOps by creating a dedicated DevOps team | Adam Nowak The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win Making Work Visible: Exposing Time Theft to Optimize Work & Flow The Goal: A Process of Ongoing Improvement The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations Switch: How to Change Things When Change Is Hard https://www.facebook.com/Adventures-in-DevOps-345350773046268/ Picks Charles Max Wood: Holiday Inn White Christmas The MaxCoders Guide To Finding Your Dream Developer Job Nell Shamrell-Harrington: The Mandalorian Rust in Motion Adam Nowak: Why We Sleep: Unlocking the Power of Sleep and Dreams Jabra Elite 85h Wireless Noise-Canceling Headphones
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website. What happens when a team member who joined as a “gift” from management fails to keep the standard expects from each of the team members? If you add to this, the fact that some team members become vocal about the problem, but others don’t even want to touch the subject, you have all the ingredients you need for massive conflict. What can a Scrum Master do? Listen in to learn how Dmytro, the Scrum Master helped the team get out of this negative spiral. Featured Book for the Week: Accelerate, by Nicole Forsgren et al. Dmytro’s recommendation is the book by Gene Kim, Jez humble and Nicole Forsgren, Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations. In Accelerate, Dmytro found many inspirational stories and anecdotes that helps him improve the organization and the teams he works with. Dmytro also recommends Scrum, the art of doing twice the work in half the time by Sutherland. In this book he highlights the many real-life examples. Additionally, Dmytro refers to The DevOps Handbook by Gene Kim, a book he describes as filled with technical practices that teams can apply. About Dmytro Balaba Dmytro calls himself one of the most dedicated Scrum Masters/Agile Coach in the world :) On his right-hand he has a tatoo with golden ratio, Fibonacci sequence. After almost 15 years of work in IT management Dmytro found himself balanced and happy. He’s been a full-time Scrum Master for more than 3 years. You can link with Dmytro Balaba on LinkedIn and connect with Dmytro Balaba on Twitter.
In today’s episode, Dan Neumann is joined by Steven Granese, the Vice President of the Transform Practice at AgileThought! As the VP of Transform Practice, Steven leads a team of the top Agile Coaches, DevOps Consultants, and Product Consultants in the United States. Together, Dan and Steven will be exploring the ‘why’ behind Scrum and examing the question of why organizations and teams should be using Scrum, in the first place. Steven often sees that the clients he’s working with lose focus on the ‘why’ behind Scrum or don’t even know what it is, to begin with! With these clients, there will be a lot of focus on the mechanics of Scrum and the framework itself (i.e. the ‘how’) without a deep understanding of why they’re using Scrum, what problems they’re trying to solve with Scrum, and what their purpose is for working with sprints with iterations. In this episode, Steven addresses how organizations can shift their perspective from a ‘how’ mentality to a ‘why’ mentality as well as many of the misconceptions and incorrect uses of Scrum (so you can be sure to avoid them!) Key Takeaways Why it is important to focus on the ‘why’ behind Scrum rather than the ‘how’: The ‘why’ helps the team and organization understand what problem they’re trying to solve with Scrum in the first place Focusing on the ‘how’ (such as: “How do we execute Scrum?”) leads to organizations applying Scrum incorrectly Understanding the ‘why’ leads to a deeper understanding of why they’re using Scrum, the problems they’re trying to help solve with it, and what their purpose is in working with sprints and iterations The ‘why’ behind Scrum and where it makes the most sense to use: In conditions of high uncertainty In environments of high uncertainty Incorrect ways Steven sees Scrum being applied: As opposed to building a working increment of their product, getting feedback as they go, and adjusting their sprint-to-sprint plan based on the feedback (which is the heart and soul of the ‘why’ behind Scrum), they’re not allowing feedback into the process — therefore losing the ‘why’ in the process Breaking up work into milestones instead of sprints Treating the sprint demo like a sales pitch and not letting the customer experience the demo for themselves Techniques and tips for achieving the ‘why’ behind Scrum: Recognize that the market moves fast, there’s a lot of uncertainty in the world, and that the customer’s needs are changing very quickly Match the way you think about your work and deliver your work to that uncertainty (which allows you to move faster) Stop overplanning and just start working Put increments of the product into the customers’ hands and start getting their feedback Get back to the basics and simply focusing on two weeks at a time Measuring the right metrics (“You get what you measure”) Don’t just use Scrum to measure the team; use it to measure the flow of the entire system Focus on getting really quality feedback from your customers “Begin with the end in mind.” — Stephen Covey Through receiving high-quality, real feedback from a sprint demo, really listen to the feedback and adjust the plan and fix problems accordingly Understand where the market is headed (and differentiate between what the customer wants and what is actually needed) by building something and putting it in their hands to get feedback Fail fast to learn fast Build in thin slices and get feedback as you go — you will learn a ton about what users actually need and also save time by not building unneeded features Misconceptions about the Scrum framework: That Scrum is really about product delivery (“Scrum is just as much about discovering the solution as it is about delivering the solution” — Steven Granese) Scrum and other Agile frameworks are seen as a delivery mechanism (as opposed to a mechanism to discover what the customer actually needs) That you have to use Scrum (if you already know exactly what you need to build and there’s no uncertainty then there’s no need for the iterative nature of Scrum) Mentioned in this Episode: Steven Granese Stephen Covey “Wagile” (Waterfall Agile) Steven Granese’s Book Picks: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren, Jez Humble, and Gene Kim Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!
Robby speaks with Matt Weagle, Engineering Manager at Lyft. Matt discusses how his engineering teams have handled technical debt in small iterations vs. a major rewrite, why a whiteboard is the best tool for architectural challenges, and the most common mistakes he sees when engineers approach legacy code bases. Helpful Links: Follow Matt on Twitter Matt on LinkedIn Some Thoughts on Security After 10 Years of Gmail A Taxonomy of Yak Shaving [Book] The Manager's Path by Camille Fournier [Book] Release It!: Design and Deploy Production-Ready Software by Michael T. Nygard [Book] The Phoenix Project, A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim , Kevin Behr [Book] The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity by Alan Cooper [Book] Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations by Nicole Forsgren Subscribe to Maintainable on: Apple Podcasts Overcast Or search "Maintainable" wherever you stream your podcasts. Loving Maintainable? Leave a rating and review on Apple Podcasts to help grow our reach. Brought to you by the team at Planet Argon.
Today’s episode is all about recognizing middle-of-the-day deployments; how teams such as Netflix, Facebook, and even the Azure DevOps Product Team are doing them; and taking a look at how other teams can achieve that for themselves! Jeffrey Palermo’s guest today is Eric Fleming, a Software Architect at Clear Measure. Eric leads an intense team, developing and operating a mission-critical software system in the financial sector. He lives in Alpharetta, Georgia, and is a host of the Function Junction Youtube Channel, which is all about Azure functions. He’s also written articles for MSDN Magazine and CODE Magazine. In this episode, Eric takes Jeffrey through his journey of inheriting a monolithic software system and the major transformations he had to execute to get it where it is today; deploying in the middle of the day! He explains the key steps he took in breaking up the monolith, the development process, who was involved, what the structure and DevOps environments looked like, and all of the details you need to know if you’re finding yourself in a similar situation! Topics of Discussion: [:52] How to get your hands on Jeffrey’s book, .NET DevOps for Azure. [2:04] About today’s episode and featured guest. [3:00] Jeffrey welcomes Eric to the podcast! [3:06] Eric begins the story of how he inherited a software system and the journey it took getting it to deploy in the middle of the day. [9:58] Fast forward to today, what does this software system look like now? [11:50] What does Eric attribute to his ability to handle a high-throughput in only four app servers? [15:52] Eric’s process for deploying the 50-sum processes that need to be deployed. [17:32] A word from Azure DevOps sponsor: Clear Measure. [17:59] Eric speaks about their Git Repositories. [19:25] Eric explains what the structure and DevOps environments of one of his applications looks like (that is a Windows service with its own Git Repository). [21:45] Who is involved whenever part of the system is being deployed? [25:37] Has there been development process differences during their monthly deployments/monolith time? [26:22] Now that they are shipping every day/whenever they need to, what has become of their sprints? And how do they get some features done in just a day and ready to deploy within days? What does this look like and how do they implement this pattern? [31:50] Do sprints even exist in this new world? [33:31] The major transformations that Eric had to execute to get to where he is today with the software system, and some of the first steps he took to breaking up the monolith. [36:27] Would Eric have been able to start breaking the monolith apart if he didn’t have automated tests? [38:47] Resources Eric recommends to listeners in a similar situation to where he was! Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) — Reach out to Jeffrey @JeffreyPalermo on Twitter if you have a user group or conference and would like some free copies of .NET DevOps for Azure! .NET DevOps for Azure, by Jeffrey Palermo bit.ly/dotnetdevopsproject — Visit for an example of .Net DevOps for Azure Function Junction Youtube Channel MSDN Magazine CODE MagazineEric Flemming’s Twitter: @EFleming18 NServiceBus Particular SoftwareTeamCity Octopus Deploy Sumo Logic New Relic Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD, Jez Humble, and Gene Kim The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.
Yalın yazılım geliştirme yöntemleri kaliteli ve müşterinin ihtiyacına uygun yazılım geliştirmesini sağlarken diğer taraftan da ekibin teknik yeterliliklerini arttırmayı hedefler. Günümüzde çevik yöntemleri kullanan bir çok firmanın yalın olmadığını süreçlerindeki israflardan açıkça görebiliyoruz. Yalın yazılım geliştirme yöntemlerinin en çok dert edindiği konu olan süreçlerdeki israflara değindik. Konuşmacılar: Onur Aykaç, Uğur Atar, Mert Susur
本期节目将开辟一个新系列，我会邀请一些从事软件行业的朋友来聊聊软件开发、职业规划、行业见闻等话题。在这期节目中，我与 Ruby 开发者 Yiming 聊了聊各自对敏捷开发（Agile）的理解，实践敏捷开发时遇到的痛点和积累的经验，并交流了如何将敏捷开发的思想运用在生活中的其他方面。 Yiming 的博客：My Understandings of Agile Over Time Yiming 的博客：Similarities between TDD and Management The Effective Engineer One Decision Separates The Wealthy From The Non-Wealthy Accelerate: The Science of Lean Software and DevOps
Your host, Dan Neumann, is excited to bring you two guests for this week’s episode — repeat guest, Eric Landes, and Barry Matheney. Eric and Barry are both Agile thinkers, experts in the DevOps space, and colleagues of Dan at AgileThought. Eric Landes is a Scrum.org certified professional Scrum trainer and currently serves as a Senior DevOps Consultant, ALM Director, and Solutions Architect. Barry also is a Senior DevOps Consultant. Previously to his role at AgileThought, he served as Director Enterprise Applications at Kforce Inc. Today, they’re talking about DevOps and the importance of having it on Scrum teams. They cover whether it is good or bad that there are barriers between Agile, Scrum, and DevOps; what well-functioning Scrum teams look like when they have a DevOps skillset embedded into them; how to incorporate DevOps into organizations; what a DevOps skillset could bring to a team; and how DevOps can fit into even the most traditional of companies. Key Takeaways Is it good or bad that there are barriers between Agile or Scrum and DevOps? It is disadvantageous to separate DevOps from Agile or Scrum because it is important that your team has all the skills they need to deliver software You need the DevOps skillset on your team and it should be a goal to incorporate it What do well-functioning Scrum teams look like when they have DevOps skillsets embedded into them? Self-sufficient Not limited by dependence on other teams or organizations Eliminates walls and allows for continuous delivery How to incorporate DevOps into organizations: Use baby steps Use it to inform the beginning of the development cycle and product decisions down the line What the DevOps skillset brings to a team: Experimentation or hypothesis-driven development Rapid deployment and continuous delivery Tons of not-so-visible benefits (such as auditing, compliance, security, deployability, and testability) How DevOps can fit into traditional companies: Remove constraints (such as specific deployment dates) Automate the value the compliance brings Mentioned in this Episode: Eric Landes (LinkedIn) Barry Matheney (LinkedIn) The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Podcast Ep. 9: “Exploring Expert Facilitation Tips with Adam Ulery” SRE — Site Reliability Engineering Cowboy coding Eric Landes and Barry Matheney’s Book Picks The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done, by Stephen Denning Lean Enterprise: How High Performance Organizations Innovate at Scale, by Jez Humble, Joanne Molesky, and Barry O’Reilly Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD, Jez Humble, and Gene Kim Outliers: The Story of Success, by Malcolm Gladwell Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!
Do 203. dílu jsme pozvali Lukáše Křečana, Martina Damovského a Zdeňka Mertu a bavili se o testování na produkci. Techniky (postupy) - Canary release https://martinfowler.com/bliki/CanaryRelease.html - Blue Green deployment https://martinfowler.com/bliki/BlueGreenDeployment.html - A/B testing https://en.wikipedia.org/wiki/A/B_testing - Tap recording - Shadowing http://blog.christianposta.com/microservices/advanced-traffic-shadowing-patterns-for-microservices-with-istio-service-mesh/ - Feature toggles https://martinfowler.com/articles/feature-toggles.html - Synthetics (Specialni ucty) - Exploration Testing https://en.wikipedia.org/wiki/Exploratory_testing - Chaos testing https://principlesofchaos.org Nástroje - Diffy https://github.com/twitter/diffy - Istio https://istio.io Zdroje Knihy - The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations - Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations - Lean Enterprise: How High Performance Organizations Innovate at Scale - Building Microservices: Designing Fine-Grained Systems Články - https://medium.com/@copyconstruct/testing-in-production-the-safe-way-18ca102d0ef1 - https://blog.turbinelabs.io/deploy-not-equal-release-part-one-4724bc1e726b - https://blog.turbinelabs.io/deploy-not-equal-release-part-two-acbfe402a91c - https://martinfowler.com/articles/microservice-testing/ - http://blog.christianposta.com/microservices/advanced-traffic-shadowing-patterns-for-microservices-with-istio-service-mesh/ - https://githubengineering.com/move-fast/
Brant Burnett is continuously integrating and deploying microservices. This episode is sponsored by Smartsheet. Show Notes: Previous microservice episodes: Chase Aucoin on the Microservices Manifesto Richard Rodger on Microservices SOA (Service Oriented Architectures), first defined in a Gartner paper from 1996: "Service Oriented" Architectures, Part 1 CI tools mentioned: Jenkins TeamCity Travis CI AppVeyor DEB and RPM files were mentioned. DEB - Video: Anatomy of a Debian Package RPM - rpm.org Chocolatey is a similar offering for Windows s3 is a cloud storage service from AWS (Amazon) Spinnaker Blue/Green Deployment and Red/Black Deployment Canary Release Monitoring tools mentioned: Prometheus and Data Dog Linq2Couchbase is a Linq provider for Couchbase (NoSQL database). For more about Linq, check out this video featuring Ander Hejlsberg State of DevOps Report 2018 by Puppet (and Splunk) Book: Accelerate : The Science of Lean Software and DevOps by Nicole Forsgren, Jez Humble, Gene Kim LaunchDarkly Brant Burnett 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!
with Nicole Forsgren (@nicolefv), Jez Humble (@jezhumble) and Sonal Chokshi (@smc90) From the old claim that "IT doesn't matter" and question of whether tech truly drives organizational performance, we've been consumed with figuring out how to measure -- and predict -- the output and outcomes, the performance and productivity of software. It's not useful to talk about what happens in one isolated team or successful company; we need to be able to make it happen at any company -- of any size, industry vertical, or architecture/tech stack. But can we break the false dichotomy of performance vs. speed; is it possible to have it all? This episode of the a16z Podcast boldly goes where no man has gone before -- trying to answer those elusive questions -- by drawing on one of the largest, large-scale studies of software and organizational performance out there, as presented in the new book, Accelerate: The Science of Lean Software and DevOps -- Building and Scaling High Performing Technology Organizations by Nicole Forsgren, Jez Humble, and Gene Kim. Forsgren (co-founder and CEO at DevOps Research and Assessment - DORA; PhD in Management Information Systems; formerly at IBM) and Humble (co-founder and CTO at DORA; formerly at 18F; and co-author of The DevOps Handbook, Lean Enterprise, and Continuous Delivery) share the latest findings about what drives performance in companies of all kinds. But what is DevOps, really? And beyond the definitions and history, where does DevOps fit into the broader history and landscape of other tech movements (such as lean manufacturing, agile development, lean startups, microservices)? Finally, what kinds of companies are truly receptive to change, beyond so-called organizational "maturity" scores? And for pete's sake, can we figure out how to measure software productivity already?? All this and more in this episode!
Future Squared with Steve Glaveski - Helping You Navigate a Brave New World
Today, I am speaking with Nicole Forsgren. Nicole is an IT impacts expert who is best known for her work with tech professionals and as the lead investigator on the largest DevOps studies to date. She is a consultant, expert, and researcher in knowledge management, IT adoption and impacts, and DevOps. In a previous life, she was a professor, sysadmin, and hardware performance analyst. Nicole has been awarded public and private research grants (funders include NASA and the NSF), and her work has been featured in various media outlets, peer-reviewed journals, and conferences. She holds a PhD in management information systems and a master’s degree in accounting. Nicole is CEO and Chief Scientist at DevOps Research and Assessment (DORA). Her first book, Accelerate: The Science of Lean Software and DevOps explores the topic of Building and Scaling High Performing Technology Organizations. I had a great time chatting with Nicole and learning about, not only her Swedish ancestry, her favorite ice cream flavour and her love for working out - which might have something to do with the ice cream, but learning more about what makes a high performing team tick. You will learn lots in this conversation, including: Why traditional performance measurement metrics such as utilisation and lines of code are flawed and what to use instead What characteristics differentiate high performing teams from low performing team and how to start embedding these characteristics into your organisation; and How to effectively drive culture change This just scratches the surface of what we discussed so please sit back, walk, run or whatever it is you do when you listen to podcasts and enjoy my conversation with Nicole Forsgren. Topics Discussed: What DevOps is and why it matters Waterfall and stage gate versus agile and DevOps Why speed is fundamental to success The research behind the book What differentiates high performers from low performers How to effectively measure performance Flaws in common measurement approaches Maturity models v capability models Change advisory boards How to do QA in a fast-moving team Breaking down silos The power of cross functional, self organised teams How to drive culture change Continuous delivery How to build a truly engaged organisation How to avoid burnout Simple things companies can do to transition Show Notes: Get the Book: Pre-order on Amazon at: https://amzn.to/2wtaIW9 Web: Nicolefv.com Twitter: @nicolefv DORA: http://devops-research.com The Business Case Alternative ebook: http://bit.ly/bizcaseebook/ Nudge (book): https://amzn.to/2Nh9ofX Thinking Fast and Slow (book): https://amzn.to/2LruWVI The Undoing Project: https://amzn.to/2BO8IO9 Join the conversation on Facebook: https://www.facebook.com/groups/futuresquared/ where you can discuss episodes, request guests, propose questions for forthcoming guests and access exclusive content and special offers! Listen on iTunes @ goo.gl/sMnEa0 Listen on Stitcher @ www.stitcher.com/podcast/future Listen on Google Play @ bit.ly/FSGoog If you've got any questions on this podcast feel free to send an email to steve@collectivecamp.us or tweet me on Twitter @steveglaveski or @future_squared Follow me on Instagram: @thesteveglaveski Like us? It'd make our day if you took 1 minute to show some love on iTunes, Stitcher or Soundcloud by subscribing, sharing and giving us a 5 star rating. To sign up to our mailing list head to www.futuresquared.xyz For more information on Collective Campus, our innovation hub, school and consultancy based in Australia and Singapore check out www.collectivecampus.io
Most people will only be involved in a Lean software implementation once or maybe a few times. We help companies with improvement software deployment every single day. Because we have been around the block many times, we have seen what leads to success and which mistakes should be avoided at all costs. We are happy to share what we’ve learned.
In this episode of AgileNEXT, Al Shalloway, an Agile and Lean Coach, joins Daniel and Stephen to discuss: Scaling Agile SAFe Scrum and the role of Agile Brands Object Oriented design Community Bio: https://www.linkedin.com/in/alshalloway From Al: As founder of Net Objectives, I am committed to leading the industry in learning how organizations can transition to Enterprise Agility with Lean-Agile methods. I have co-authored the following books: Lean-Agile Software Development: Achieving Enterprise Agility, Essential Skills for the Agile Developer: A Guide to Better Programming and Design, The Lean-Agile Pocket Guide for Scrum Teams, and Design Patterns Explained: A New Perspective on Object-Oriented Design. I am currently one of a couple dozen SPC Trainers outside of SAI. Although I co-founded Lean-Kanban University, I am no longer affiliated with it. Specialties: Consulting, training and coaching in Lean Software, SAFe, Kanban, Agile, Scrum, Design Patterns, Object-Oriented Analysis and Design
One of the many things we love about this time of year is the opportunity to reflect back on what we’ve accomplished (or survived) over the past twelve months. It’s also a great moment to set the stage for success in the year to come. If you practice the Lean management approach or plan to do so in 2017, one way to ensure that you get the most out of your improvement and waste reduction efforts is to invest in Lean software. Doing so gives you a number of advantages that will amplify your results and ease the path to achieving your most important goals. Here are some of them.
The Get Paid Podcast: The Stark Reality of Entrepreneurship and Being Your Own Boss
Thinking about hiring a developer to build an app for your business? Make sure you know exactly what you DON'T need before you start shelling out piles of money. Ernesto Tagwerker is the owner of OmbuLabs, a software boutique that uses the Lean Startup methodology to create web apps for their clients. Just because you have an idea for an app doesn't mean that's where you should start. Listen to Ernesto share the biggest things people get wrong when they hire a development team and why you should apply some Lean Startup practices to your business even if it has nothing to do with software. In this episode you'll hear: -- Why OmbuLabs probably won't build your website. -- The difference between a web app, a website, a desktop app, and a mobile app. -- All about MVPs, and why they're a must-have in your project (whether or not you're building software). -- Why you need to “get out of the building” more. -- One of Ernesto's biggest challenges in closing clients. -- How he combats burnout in himself and his team. -- Why Ernesto went from bootstrapping his business to looking for funding, and back to bootstrapping over the course of 3 years. -- Why OmbuLabs charges by the hour and not on a per-project basis. -- The unique challenges in hiring software developers.
Agile Instructor - Coaching for Agile Methodologies such as Scrum and Kanban
I am thrilled to present a wonderful interview with Mary and Tom Poppendieck. They are true legends in the Agile and Lean Software Development movement. Checkout today's episode where we discuss challenges facing many organizations such as: product vs. project mindset, globally distributed teams, and equipping teams for success. We also discuss their latest book, The Lean Mindset. Please consider picking up the book to learn more about these topics in greater detail.Please check out their website: poppendieck.com to learn more about Mary & Tom and their insightful work. Many thanks to Mary and Tom for investing their time for this podcast and for their contribution to our industry.All Things Agile - Episode 005 - Mary and Tom Poppendieck InterviewTranscript:Welcome to the All Things Agile Podcast. Your destination for tips and interviews with the leaders in the world of Agile. Don’t forget to subscribe to this podcast on iTunes, and please check out our sponsor: TeamXcelerator.com. And now, here’s your host: Ronnie Andrews Jr.Ronnie: Hello everyone and welcome to the All Things Agile Podcast, Episode 5. I’m very excited to present to you a wonderful interview with lead software legends Mary and Tom Poppendieck. Before I begin, a quick reminder that this podcast is for informational purposes only and accepts no legal liability. So let’s get started!One of the goals for this podcast is to interview and feature influential leaders in the Agile space. Today’s guests are just that – Mary and Tom pioneered the Lean Software development movement, with their groundbreaking book Lean Software Development and Agile Toolkit. It’s a classic among Agile literature. In 2013 they also released ‘The Lean Mindset – Ask the Right Questions’. Mary and Tom travel the globe, speaking at conferences and consulting with many of the world’s top companies. It’s an honor and a pleasure to have them on the All Things Agile Podcast. Without further ado, let’s welcome Mary and Tom!Well, thank you for joining me today Mary and Tom, I really appreciate it. Why don’t we go ahead and get started with a few questions. During my own career, I have worked at several Fortune 500 companies. And I’ve often found that large organizations tend to be project-focused, rather than product focused. For example, I have seen environments where software development is treated as a black box, and it can sometimes have a throw-it-over-the-fence mentality. I would love to hear your thoughts on integrating software development as part as a holistic product chain.Mary: If you look back to the early 90’s, I was a manager in the early 90’s and there were very few of my colleagues that could even type. Typing wasn’t something that you learned, unless you were going to be a secretary. The idea of doing email and stuff was so difficult that when the internet first came, many managers sat down their secretaries to do their email typing. Eventually that went away. But if you look at industries that were formed before technology was widespread, like banks and insurance companies and those kinds of industries, you’ll find that this technology area was separated out from the mainstream for two reasons: one reason is because the managers of the line businesses simply were not comfortable with technology; and another was that computer technology was considered something that was expensive and should be centralized in order to reduce costs.Well, today, computer technology is not the same. It is the fundamental basis for competition for almost every company that uses it. Thanks to the kinds of products that they offer, or the things that help them be competitive – if you take a look at the new companies like Google and Facebook and Amazon and those companies, computer technology is a fundamental competitive advantage. And if that’s true, then it needs to be manage, at least what’s done, in the line organization, rather than in some side-organization that is in side to the line organization. So if you look at the companies I’ve just mentioned, they don’t have a central IT department. They have the line organizations responsible. That doesn’t mean that they don’t think about IT costs, but they think about them as product development costs.So now, the things that people develop that are helping the company become more competitive and distinguish it from other companies, are things that need to happen with people who sit in the line organization and truly understand customers and are close to them and secondly, software technology today is much more thought of not as a black box, but as a constant feedback mechanism. So you do something, you see the results on customers and on the line business, you adapt to the results and you continue on.With those two things said, first of all it provides the competitive or strategic advantage to be thinking in line organization about technology. And secondly, technology is by and large best developed as a short feedback loop kind of a business; it makes very little sense to continue on with this black box concept that used to be a sensible idea. Tom, you have something to say?Tom: Yes, definitely. I’d like to address this from a little more abstract level and put projects in their proper place. The motivating aspects as identified by Simon Sinek is ‘always a purpose’, a reason for doing things, a difference that an organization is attempting to make in the world. It’s the reason why people come to work, why they think about a problem, why they devote a lot of energy to solving a problem. Now, ‘Why?’ is primary – nothing great happens without a great ‘Why?’ ‘How?’ is where the project sits; it’s one of the techniques for containing risk, for containing how much resources you’re going to devote to achieving your ‘Why?’. Agile is another collection of techniques that are ‘How?’s – ways of working strategies, tools.Engineering disciplines are another set of ‘How?’s. Automated testing and many others. But they’re all ways of working, ways of thinking to achieve a purpose. And neither of those are your product. Your product is ‘What?’ that’s Simon’s third level. Why, How and What? Now, whether you are successful is not so much a matter of did you sail this in the constraints, that your project imposes? It is ‘did you do the very best that you could in terms of achieving your purpose within the constraints of your available tools and skills, and risk management strategies?’I read a fascinating article in Harvard’s Business Review yesterday. And it was saying that the most important, the most powerful way of managing risk is to measure and analyze time to recover the something going wrong in any individual component of what you’re doing. This translates easily at least in my initial impression, into how fast is your feedback loop?If you try and do a ‘What?’ that doesn’t really contribute to achieving the purpose and find out about it until very much after it has been done, and after many things have been built on top of it, you have wasted all of the good skills, all of the good techniques and you have triggered away your ‘Why?’ But if you find out about it very quickly, and you haven’t placed practices and approaches that you can recover very quickly, then you have the very best that you can; you’ve delivered the best ‘What?’ that you can using your constraints to achieve your purpose. And I think that’s the framework for thinking about projects – it’s just a tool; they’re not the ‘What?’, they are not the ‘Why?’ – they’re just a way of containing risk. Ronnie: Right, that makes sense. I agree. Sometimes, people place more emphasis, if you will, on the success of the project rather than the success of the product. And for the customers, I agree. Excellent answers. The next question I was wanting to ask, kind in a similar note, I also worked on projects where everything was kind of guided by arbitrary dates if you will. And sometimes, the end customer and the product features were really not in focus. Have you seen this behavior before and if so, what advice do you have for our listeners on how to tackle this issue?Mary: Well, it’s interesting where the arbitrary dates come from, because I think that a business organization wants them to help them move forward with customers. They have some frame in mind about how much it’s worth to them to do that, how much money they can spend and what kind of deadlines are important, and those deadlines and those budget constraints should be honored as far as what are our constraints for meeting our overall objective? But then those get translated into somebody’s version of minor objectives and minor deadlines and if we don’t do this by this time, we can’t get to there by that time. Then those become completely arbitrary and basically unattached to the overall purpose. And those kinds of deadlines that are fake, are pretty easy to detect and what is the reason for them? That’s what you got to ask. Why do we have these strange deadlines? Why don’t we have, instead, a very tight feedback loop and a visibility of the progress we’re making towards the overall objective of what we’re trying to do and understand what part of the progress needs to happen at different times.Now, if the way that you do a project is you first do all of the design and then you do all of the next step and it isn’t until the end that you actually do the work, write the code, write the test, integrate the software, then those days are truly artificial. But if you strategy is to say ‘I am going to have a complete system in two months – it’s going to be a minimal system, but it will be workable and we can get feedback on it – and that two months is going to give us another 8 months to finish the whole thing and the feedback necessary to do that’ – that’s a much more viable deadline. So you have to say are the high level constraints appropriately applied as low-level constraints to get stuff done or are they artificial? Because if they’re artificial, smart people can figure that out and they will ignore them. Tom?Tom: Not all deadlines are arbitrary. Some are legal, some are annual rhythms of shows. There are some very legitimate deadlines. And a competent team with a competent manager that understands what it takes to do work will be able to achieve a real deadline. However, if a deadline is used as motivation, as a goad, as a way of avoiding waste, then it can be very ineffective and very destructive. It can lead to bad behavior. The use of a deadline that is not legitimate, that is not related to the ‘Why?’, to the work being done, is probably a symptom of lack of competence to measure what really matters about the progress of the work.Mary: I want to throw in one last little thing here, and that is that projects should have things called: cost, schedule and scope. And the thing that really should be flexible is neither, in most business’ cases cost, nor schedule. The thing that should be flexible is scope, because cost and schedule deadlines are typically driven by business constraints. But the scope should be the thing that is negotiable almost always and the reason for that is that, especially in a software environment, the thing that we’re putting together is a complex system. The more junk, features, capabilities or whatever that we throw into that massive software, the more complex it is, the more difficult it is and by and large, over time, the more stuff you have in software, the more crud you get in there, the more complexity you get in there, the harder it is to change, to manage and so on.So in software, you want to think of ‘stuff’ as bad. You don’t want to measure a team on how much junk can I put in, in a window of time? You want to say: How much business purpose can I achieve within as little code as possible? So you are looking for reduced feature set, reduced capabilities that get the job done. And so the thing you really want to reduce is not the budget or the schedule; it’s the amount of stuff that you try to squeeze into a business-driven budget and schedule. So typically in all projects – and this is not the way most project managers look at it – but a software project almost always bend on scope, rather than bend on deadline or on cost.Tom: It is impact. Did you achieve the impact that your work aimed to achieve? Did it achieve its purpose? If the impact can’t be measured, you have no guidance about what to include and what to leave out. You have no measure about when you’re done. If you have as much impact as your tools and skills and techniques permit, as the team was capable of and the project was a success…Ronnie: I definitely like that impact thing – that kind of really sums it up really well, thank you. If you don’t mind, I’ll ask the next questions which is: in my experience, I’ve seen senior exectutives get very excited about Agile and they decide to roll it out across the organization. However, sometimes the teams can be lacking in technical skills or tools to ensure success. For example, great Agile teams place a high value on quality and that usually will translate in frequent and rigorous testing. And if a team has, for example, automated tests in place that will result in the product being in good shape. However, there may be teams which have never worked, for example, with test automation and it can then be a real challenge. What are your thoughts regarding skills and technical preparation in relation to methodology adoption?Mary: Methodology is the result – it’s not the driving factor in a good Agile implementation. What you’re trying to do is create an environment with rapid feedback, so that you can do a better job of satisfying customers. And you should not be measuring ‘did I do this or that Agile practice’? You should be measuring ‘do I have greater impact in delivering what my customers really want?’ And that’s where you get to the quality, the test automation and that sort of thing.So let’s talk about a different objective for that executive, so that the executive have stuff that they can measure and put hands around. And that is, instead of working about a methodology called Agile, why not worry about what I’m going to call ‘The Software Development Process of the Future’ which is continuous delivery. So instead of saying that we have these meetings and we have these things, you should be saying ‘How fast, from the time I decide to do something, until the time I get it in production – how long does that take?’ And when you start looking at how far along am I on the path to continuous delivery - that is my executive goal. Those companies that do that have far more effective Agile implementations because it’s that one thing that you’re focusing on that continues delivery, that drives all the good technical behavior by the way of good practice behavior.Let me give you an example in Alcoa – once upon a time when he became CEO, decided that he wanted to focus on one single thing and it was going to be safety. And every single issue around any kind of safety incident was what the entire company focused on. And that became a lever to cause all kinds of additional good behavior and the company really took off, because you can’t have safety without quality, alert workers, really good, well-run equipment, all of that sorts of things. And similarly in Lean, the concept of flow is sort of that driving principle. So you try and just focus on flow, everything falls in place. All the technical things, all the quality things and so on. Similarly in software. Let’s not focus on process; let’s focus on continuous delivery. How far are we towards being able to deploy immediately? And if we make that the one principle of how we perceive, then what we have is a driving principle that will drive all the rest of the good behavior and certainly, all of the technical behavior.Ronnie: Excellent answer. A final question, if you will. There are many great sources of information on implementing Agile, but most are geared towards smaller organizations often. And for larger companies, it can be a hurdle if you will to implement new methodologies in a global workforce. For example, I’ve recently worked with teams that are split across India, Brazil, China, Mexico and of course here in the US. What insight can you provide on how to tackle teams that are globally distributed?Mary: There certainly are many big companies – we wrote in our new book about Ericson as an example – very large companies that are very effective in implementing Lean and Agile concepts. But they don’t hold a lot of stake in having ‘teams’ that are geographically distributed. Yes, organizations are geographically distributed – but why do teams need to be? So what I see large, effective organizations do when they think about distribution is to say what are the things that need to be communicated? And how can we effectively, at a single site, have communication among colleagues and think about communication across teams on a different scale? So the effective ones don’t try too hard to make individuals have to communicate across large distances. And if they do, they have people travel.However, there can definitely be reasons why people should – and really valid purpose-drive, business-driven reasons why people need to communicate across geographic boundaries. And there certainly are plenty of examples on how this is done effectively. If you look at the open source movement, none of the open source projects have people co-located. These ones work very well with the communications issues across countries and if you look at them for models on how to do it. So if teams do need to be distributed, then you want to think ‘Why?’ Okay? You do not want to have class A people figure out what to do and class B people are in another continent that actually implement it, because that gets us back to the first question. The people that are doing the implementation are divorced from the purpose. But if the teams are geographically distributed, you have to think hard about how can they all share a common purpose that they understand and believe in and commit to, and if they do that the communication issues will be solved. And if you can’t imagine teams across countries dedicated to a common purpose, then you should say: Why are our teams structured this way? So every company that has solved this problem, has solved it in a different way, depending upon their market and their structure and all of that sorts of things. But they do have a few things in common. One is, they think for themselves. They don’t take rule books. They try to make sure they honor the intelligence of every person on the team and make sure that they can participate fully their thoughts in thinking about it, and they don’t have these wall handover mechanisms because that’s not the right way to deal with this. Tom: All the teams we have seen around the world, and we’ve seen many, have one shared characteristic. And it’s not tools or techniques or methodologies – it’s they think for themselves. There are many examples, case studies about groups that have thought about their problem and their context and their challenges and they think for themselves and come up with a unique combination of tools and techniques and disciplines that make them highly effective in achieving their purpose. A team which is distributed and is simply doing what it’s told to do is not going to be very effective. A team which is distributed for a good reason who all believe in a purpose that they are trying to achieve and have adequate tools, handles and the like, that make it possible to communicate effectively, will figure out how to do it. They will think for themselves, if they have sufficient feedback about how they are doing, how things are working for them; they will figure out how to do it. And there are many, many ways that different teams figure out how to do this. But it’s not a recipe. It’s not a product that you buy; it’s how people think about what they are doing together. If they can’t think together, they can’t be very effective at working together. They can’t learn together. The product will reflect that lack of learning.Ronnie: I definitely agree. I definitely agree with you that having those teams be able to really understand it and what they’re trying to achieve and have those goals and have that thought in control is very key – it’s as you mentioned, if you kind of have a class A, class B type situation, then it can often result in micromanaging and diminish morale and sometimes poor quality – I’ve seen in the past the results in code. Great points, great points! And a lot of them are actually referencing some of your more recent work – if you don’t mind, I’d love to mention that briefly. You guys have put together a great book last year ‘The Lean Mindset’. Would you like to maybe highlight that a little bit more?Mary: Sure! I was just reading in an article that it used to be ‘share all their value’ was the thing that businesses thought they were in business for. But today, in today’s economy and today’s high-tech environment, what you really want to do in order to have a successful business is you need to have great people that use their minds for accomplishing the common purpose. And that purpose has to be something that these people believe in and you need to have an intense focus on delighting customers. And those three things: customers that you’re trying to delight, employees that are deeply engaged at trying to make something happen for those customers and an overriding purpose are the three sort of company drivers of the future.Our book has 5 chapters. One is on purpose and then the next one is on engaged workers and energized workers; the third one is about delighted customers. And then we talk about efficiency and what efficiency means in this context. Efficiency means, in the Lean context, flow efficiency rather than resource efficiency. Which is a whole other topic that we can talk about sometime. And lastly, we talked about innovation because today’s economy, today’s technology moves too fast to be comfortable that what worked 3 years ago is going to work 3 years from now, so constant innovation is another thing that companies need to have. That’s sort of, in a nutshell, what the book is about, those 5 chapters. And to sum it all up we have lots of case studies in there, as Tom said, and each case study shows how thinking for yourself in your context is important; which means it’s important to have people who care to think for themselves and who are allowed to think for themselves and who are inspired to help make the company successful. Ronnie: Excellent! I definitely encourage our listeners to pick up a copy of your latest book. Once again, it’s ‘The Lean Mindset’ and it’s available at book stores everywhere. I picked up my copy on Amazon, and I really just want to thank you both Mary and Tom for joining me today for this podcast episode. It’s been tremendous help to myself and I’m sure, to all of our listeners. I really thank you so much for your time Mary and Tom, you’ve been great! Thank you listening to All Things Agile. We look forward to you subscribing to the podcast on iTunes and leaving a kind review. Thanks and God bless!
Agile Instructor - Coaching for Agile Methodologies such as Scrum and Kanban
Today's episode is centered around some exciting news. I am launching a new venture, Team Xcelerator Inc., which will focus on Agile team software. The AgileInstructor.com blog and the All Things Agile podcast will be moved under the Team Xcelerator umbrella. I am very excited about the possibilities. Please checkout the podcast and send me your thoughts and product feature input using coach@agileinstructor.com. Also, don't forget to please post a kind review in iTunes. We really appreciate your time and support :)All Things Agile - Episode 4 - A New HopeTranscript:Welcome to the All Things Agile Podcast. Your destination for tips and interviews with the leaders in the world of Agile. Don’t forget to subscribe to this podcast in iTunes and please check out our sponsor: TeamXcelerator.com. And now, here’s your host: Ronnie Andrews Jr.Hello everyone and welcome to the All Things Agile Podcast, Episode 4. Today’s title is ‘A New Hope’. This is paying homage to the classic Star Wars title, but before we begin, a quick reminder that this podcast is for informational purposes only and accepts no legal liability. So let’s get started.As an Agile coach, I’m frequently searching for tools to help myself and others utilize Agile methodology successfully. Candidly, I haven’t found many tools which truly reflect the needs that I have seen over the years. Rather than let this frustration remain, I decided to start a new company: Team Xcelerator Inc. to tackle common challenges for Agile teams. You have undoubtedly heard references to Team Xcelerator a few times already. I want to take a few moments to talk about it in more detail. Everything is still very early stages, but I’m hopeful that many Agile practitioners will come to love it. A goal of mine is to develop a product which reflects the global nature of today’s workforce. Almost all development teams are now spread across the world and this trend is only continuing to rise. The use of Agile itself is also on the rise. However, many organizations are still struggling with learning and how to adapt Agile, including the fact that teams or departments may implement Agile differently.Many of the products that I’ve seen on the market are really just project management tools. We still have a lot of work remaining, but it is a goal of mine to develop Team Xcelerator into a cloud-based web tool which will enable teams to specifically focus on Agile success. I also intend for Team Xcelerator to be affordable. I want to encourage teams to utilize the tool and achieve success. It will be targeting organizations of all different sizes, including young startups to industry veterans. I can’t release too many specifics at this time, but I did want to take a moment and let my audience have advance notice of this new platform. I’m also interested in your input to ensure that it better conforms to your needs. As the episode title alludes to, it is a new hope for me and for the world of Agile; an opportunity to create a platform for Agile professionals, by Agile professionals. And I hope that you’re excited about this recent product news as I am – and remember: you can check out my blog using the website agileinstructor.com and feel free to contact me using coach@agileinstructor.com and feel free to include product comments that you may have regarding Agile tools. I would love to be able to take in your input and ensure that we have product features that will truly meet the needs of our audience.Also, don’t forget to visit our previously discussed sponsor: TeamXcelerator.com which makes this podcast possible. And thank you once again for joining me for this quick podcast – join me for Episode 5, we’re having an exciting interview with Mary and Tom Poppendieck who are the innovators of Lean Software. You don’t want to miss it! Remember – it’s time to accelerate your team, today! Thank you for listening to All Things Agile. We look forward to you subscribing to the podcast on iTunes and leaving a kind review. Thanks and God bless!
Welcome to the Software Process and Measurement Cast 270. The SPaMCAST 270 features my interview with Allan Shalloway. We talked lean, Kanban and SAFe (Scaled Agile Framework). A great interview to end the old year and bring in the new year! Al Shalloway is the founder and CEO of Net Objectives. With over 40 years of experience, Al is an industry thought leader in Lean, SAFe, Kanban, product portfolio management, Scrum and agile design. He helps companies transition to Lean and Agile methods enterprise-wide as well teaches courses in these areas. Al is a SAFe Program Consultant as well as a co-founder of the Lean Systems Society. Al has developed training and coaching methods for Lean-Agile that have helped Net Objectives' clients achieve long-term, sustainable productivity gains. He is a popular speaker at prestigious conferences worldwide. He is the primary author of Design Patterns Explained: A New Perspective on Object-Oriented Design, Lean-Agile Pocket Guide for Scrum Teams, Lean-Agile Software Development: Achieving Enterprise Agility and Essential Skills for the Agile Developer. Al has worked in literally dozens of industries over his career. He is a co-founder and board member for the Lean Software and Systems Consortium. He has a Masters in Computer Science from M.I.T. as well as a Masters in Mathematics from Emory University. For the next few weeks the Software Process and Measurement Cast will include a promo for the "Influential Agile Leader" events led by Johanna Rothman and Gil Broza. Check out the full details at www.InfluentialAgileLeader.com The Software Process and Measurement Cast has a sponsor . . . ITMPI provides a great service to the IT profession. ITMPI's mission is to pull together the expertise and educational efforts of the world's leading IT thought leaders and to create a single online destination where IT practitioners and executives can meet all of their educational and professional development needs. The ITMPI offers a premium membership that gives members unlimited free access to 400 PDU accredited webinar recordings, and waives the PDU processing fees on all live and recorded webinars. The Software Process and Measurement Cast receives a fee if you sign up using the URL in the show notes. HERE All revenue from our sponsors goes for bandwidth, hosting and new cool equipment to create more and better content for you! Support the SPaMCAST and learn from the ITMPI! The Software Process and Measurement Cast is a proud member of the Tech Podcast Network. Check out the Software Process and Measurement and other great audio and video casts! TPN: www.techpodcast.com Do you have a Facebook account? If you do please visit and like the Software Process and Measurement Cast page on Facebook. http://ow.ly/mWAgU The Daily Process Thoughts is my project designed to deliver a quick daily idea, thought or simple smile to help you become a better change agent. Each day you will get piece of thought provoking text and a picture or hand drawn chart to illustrate the idea being presented. The goal is to deliver every day; rain or shine, in sickness or in health or for better or worse! Check it out at www.tcagley.wordpress.com. The Daily Process Thoughts is my project designed to deliver a quick daily idea, thought or simple smile to help you become a better change agent. Each day you will get piece of thought provoking text and a picture or hand drawn chart to illustrate the idea being presented. The goal is to deliver every day; rain or shine, in sickness or in health or for better or worse! Check it out at www.tcagley.wordpress.com. Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." NOW AVAILABLE IN CHINESE! Have you bought your copy? Contact information for the Software Process and Measurement Cast Email: spamcastinfo@gmail.comVoicemail: +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook: http://bit.ly/16fBWVContact information for the Software Process and Measurement Cast One more thing! Help support the SPaMCAST by reviewing and rating the Software Process and Measurement Cast on ITunes! It helps people find the cast. Next: The Software Process and Measurement Cast 271 features the essay from my re-read of the 7 Habits of Highly Effective People. This book has made a huge impact on my life and the essay is a great way to start 2014!
Welcome to the Software Process and Measurement Cast 174! The SPaMCAST 174 features my interview with Karl Scotland. We discussed his concept, Kanban Thinking Karl Scotland is a versatile software practitioner with over 15 years of experience covering development, project management, team leadership, coaching and training. For the last 10 years he has been successfully applying Agile methods, and most recently has been a pioneer and advocate of using Kanban Systems for software development. Currently an Agile Coach with Rally Software in the UK, Karl is a founding member of the Lean Software and Systems Consortium and the Limited WIP Society, and has previously championed Agile and Lean Thinking with the BBC, Yahoo! and EMC Consulting. Karl writes about his latest ideas on his blog at http://availagility.co.uk/. Want to get in touch with Karl? Linked In http://www.linkedin.com/in/karlscotlandBlog http://availagility.co.uk/Twitter https://twitter.com/#!/kjscotland A message from SPaMCAST's sponsor . . . THe SPaMCAST 174 is sponsored by LeanKit Kanban. LeanKit Kanban is a software tool for kanban that is as simple to use as physical kanban. If you put it up on a touchscreen in your team area, it practically IS physical kanban. But your boards are available from anywhere, and updated in real-time. A slew of colors, icons, and avatars take your visual signaling to the next level. And the system tracks the metrics for you, providing analytics on bottlenecks, lead time, work distribution, process efficiency, and variability - for a single board or a whole company. It's kanban for the Lean enterprise. I have been using LeanKit Kanban for a personal project my wife and I are working on. LeanKit allows us to share the Kanban board across the miles with ease! Visit LeanKit Kanban! (and say hello for the SPaMCAST!) Interested in becoming a radio star? If you are interested in reviewing tools or books? Drop me a note at spamcastinfo@gmail.com Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: "This book will prove that software projects should not be a tedious process, neither for you or your team." Have you bought your copy? Contact information for the Software Process and Measurement CastEmail: spamcastinfo@gmail.comVoicemail: +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook: http://bit.ly/16fBWV Next:The Software Process and Measurement Cast 175 feature an essay titled, Do You Have Trust, Passion and A Beginners Mind? An important set of concepts for ANY framework you might be adopting.
© 2020-2025 Ivy Podcast Discovery LLC
