Podcasts about agile why

Meera Klemola and Astrid Kohlmeier are legal design pioneers. They are both teachers, speakers and writers, specialising in the application of design principles to legal services delivery. Both have consulted on this topic to the world's largest law firms and in-house teams. For this episode we sat down with Meera and Astrid to discuss their book, "The Legal Design Book", which was published in 2021. We covered many topics including: * Why they wrote the book and why now is the right time to publish it * What "legal design" is and how it differs from some other methodologies, such as Lean Six Sigma and Agile * Why "legal design" is about more than visually pleasing documents * The key philosophies and mindsets that underly legal design * How to apply legal design in practice, including case studies * The relationship between legal design and legal operations LINKS The book: https://legaldesign-book.com/ Meera's website: https://www.groundm.com/ Meera on LinkedIn: https://www.linkedin.com/in/meera-klemola/ Astrid's website: https://astridkohlmeier.de/ Astrid on LinkedIn: https://www.linkedin.com/in/astridkohlmeier/

  The connection between Lean and Agile is widely misunderstood. In this podcast we will answer all your questions about these two different approaches. Join us as Samuel Gregory explains when an agile approach is needed and what's really behind the word.     SAMUEL GREGORY Samuel Gregory is the founder of Jupiter and the Giraffe, a website design consultancy as well as hosting the weekly That Tech Show Podcast. During his time Samuel has helped world-class tech companies like Netflix and Corning as well as Conde Nast build engaging and experiential websites, working as both an engineer, leveraging his experience coding since the early 2000s as well as a technical program manager and a project manager. Using his experience and appreciation for creativity gathered during his time at Framestore, Samuel has also consulted with UI designers and user experience designers on many digital products. With this experience, Samuel has seen many of the ups and downs that can happen on website projects from both the technical side and the business side. He uses this knowledge, along with his ability to communicate complex, technical ideas into more accessible language teaching what he believes is expected in modern website development. This streamlined approach helps to keep both clients and teammates working effectively together    CONNECT WITH SAMUEL LinkedIn: https://www.linkedin.com/in/samgregorydigital/ Website : https://www.thefullstackagency.xyz/ Book: https://www.thefullstackagency.xyz/books/lingo-agile-book Key Topics in this podcast: ● Samuel's career background ● How he came up with the name of his company ● What is Agile and its connection to Lean? ● Simplifying the term “Agile” ● Why some people dislike Agile ● The history of the connection of Agile and lean ● How Agile originated from Lean ● Interactivty of websites and Its benefits for companies ● What needs to change in education to help industry to focus on learning and not just delivering ● Samuel's advice for the young people who just started out their career KEY TAKEAWAYS ● Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. ● An agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly. ● Scrum is a framework that helps teams work together. Much like a rugby team (where it gets its name) training for the big game, scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve. ● Kanban is a popular framework used to implement agile and DevOps software development. It requires real-time communication of capacity and full transparency of work. ● Agile isn't required for for building websites but may be more appropriate for software product development.   Memorable Quotes From Samuel Gregory ‘'Whenever you encounter something, whenever you see something new, don't just observe it, and let it fly by. Go down that rabbit hole! I am encouraging you to follow your nose.”

We have a very special guest this episode - one of the co-authors of the manifesto - Arie van Bennekum! In this episode we get to know how Arie got invited to the weekend in Salt Lake City when the manifesto were written! We get to know all about that weekend and how that weekend changed Aries life in many ways! Why did they choose the word Agile? Why did they write a manifesto? How did they wrote the principles? What would Arie change if he had the opportunity?

In this episode we talk to Moira van den Akker, Global Demand Generation Manager at Trimble. What is Agile? Why should marketers care? How can they implement Agile methodology? 1) Daily (or weekly) stand-ups 2) Backlog and task prioritization 3) Visual task board 4) Short-term projects (sprints) 5) Feedback loops (Kaizen) Check out Moira's LinkedIn article on this topic: https://www.linkedin.com/pulse/your-marketing-team-going-agile-2019-moira-van-den-akker/ Click here to connect with this guest on LinkedIn.

What makes a great dev shop agency? Someone who knows what it takes and is running a dev shop agency of his own is Ryan Vice. Ryan is the founder of Vice Software. His passion is dev and he’s fully immersed in the world of scoping projects, devving them and giving his clients what they want. On today’s CTO Studio, Ryan explains how Vice Software got started, why empathy is so critical as a CTO or other tech leader and his personal recommendations for running a dev shop agency.  In this episode, you’ll hear: Why don't they use Agile? Why does using offshore labor typically cost so much in the beginning? What is Sandler's Model and how does it work? Why do they cut out Scrum? What are his suggestions if you want to start a dev shop agency? And so much more! We begin today with Ryan explaining the way their company functions: everyone who works at the company programs, and it's a blended model. He got to a point in enterprise software where his rate was very competitive and he started managing offshore teams, which he didn't enjoy. But then he met his business partner and they realized they could create a lot of value. He soon realized why big companies were paying him to get that model to work, and he and his partner decided together they should try to sell that same model to small and mid-level companies. Now they have taken on a few projects for folks where they are going CTO down. They are finalizing a deal right now with a company that is creating a marketing research-type platform and he foresees stepping into a fractional CTO-type role there while his partner who lives in New Delhi manages the team and the operations. Ryan also handles ensuring their technology vision is correct and they are strategically set for the right technologies at the right time. I ask him to expand on the agency software model; I personally think it's incredibly valuable for CTOs who are considering hiring shops like Ryan's. Ryan’s company takes what lessons have worked for him in the enterprise world and makes that information available to start-ups and tech projects on a smaller scale. He explains what some of those lessons are. Everybody is looking at $10-$15 an hour labor offshore and while it's very tempting, not a lot of people do it because it's really hard to be successful using that as your labor source. What he found was every single large company that contracted him would almost immediately put him in charge of an offshore team. Basically, every time he was hired in the past he was put in charge of a remote team. And now he's converted that experience into him managing his own teams with his partner in New Delhi; they've implemented lessons learned and optimized their processes to make it more efficient so smaller companies can use his services.  The real difficulty in doing this is the start up costs. So on projects his clients don't need 40 hours of his time every week. He has one arrangement with a large company in Austin that gets 10 hours of his time every week, he has another company that he's signing and it will probably be for 5 hours of his time every week. The larger companies are paying 40 hours a week for long periods of time to have a guy like him (who has a high billing rate), go out and fail with numerous teams before finally finding the right match. Those start up costs are really high: having a high billing guy testing out multiple teams. He has found start ups and mid-size companies can't really afford to that on their own, so instead they hire Vice Software. Also on this episode of CTO Studio, we get into estimates and budgets. Ryan explains how he walks a CTO founder through the process of taking ideas bringing them into real life, all the while building and ensuring trust is created as he does this. They've gotten really good at estimating MVPs so that's something that is all about doing a waterfall-style approach to your estimation. So you have to make sure you create a spec that accounts for most things and you call out the different experiences for each user and walk through that to make sure it is solid. Then he and his partner have gotten good at quickly estimating on top of that, then they account for known unknowns. They have a padding bucket for estimating ideal hours, they have a padding bucket for requirements wiggle room and they have a padding bucket for QA. And they run everything super lean. They know their guys work hard and they don't need to motivate them with Agile so they use kanban. They prioritize the backlog then charge through the items. From there they do weekly demos to show progress and their visibility becomes much cheaper. If you cut out all the overhead of scrum for MVP you save a lot of money. They typically have about 7 to 7.5 hours per week for project management, which is pretty low. Ryan explain why this works so well with MVPs, his recommendations for CTOs dealing with artificial marketplace deadlines, the importance of empathy and how and why to engage your competitors. Join us to hear his insights on those topics during today's edition of CTO Studio.

How do you implement Agile? Why does Agile matter? How has Agile changed in the last decade? Where do you get a beer in Austin? Walter Bodwell (https://www.linkedin.com/in/wbodwell/) answers all of these questions and more in this episode. Plus, we hear the story of how Evity was sold for $100 Million. More Planigle (http://www.planigle.com) www.walterbodwell.com (http://www.walterbodwell.com) Agile Austin (http://www.agileaustin.org) Keep Austin Agile 2018 (http://conference.agileaustin.org) Image Credit (https://twitter.com/chrissmouse/status/910305604413087744) Special Guest: Walter Bodwell.

How do you implement Agile? Why does Agile matter? How has Agile changed in the last decade? Where do you get a beer in Austin? Walter Bodwell (https://www.linkedin.com/in/wbodwell/) answers all of these questions and more in this episode. Plus, we hear the story of how Evity was sold for $100 Million. More Planigle (http://www.planigle.com) www.walterbodwell.com (http://www.walterbodwell.com) Agile Austin (http://www.agileaustin.org) Keep Austin Agile 2018 (http://conference.agileaustin.org) Image Credit (https://twitter.com/chrissmouse/status/910305604413087744) Special Guest: Walter Bodwell.

Michael Nygard: @mtnygard | Wide Awake Developers (Mike’s Blog) | The Cognitect Blog | Release It! Design and Deploy Production-Ready Software This episode is sponsored by Pivotal. 01:42 - Mike’s Background and Career Path Thus Far 02:59 - Complex Systems The Complexity Explorer 06:22 - Continuous Partial Failure and Looking at Microservices Mike’s New Normal Blog Series 11:23 - “Agile”: Why? 14:03 - Antifragility Blog Post: From Resilient to Antifragile Nassim Taleb’s Antifragile Normal Accidents: Living with High-Risk Technologies by Charles Perrow 20:18 - Evolutionary Design Blog Post: The Art of War, Maneuverability, and Microservices Sun Tzu’s The Art of War Matt’s Antifragile Architecture Talk Evolutionary Architecture by Neal Ford, Rebecca Parsons, and Pat Kua 29:05 - Redundancy and DRY (Don’t Repeat Yourself) YAGNI (You Aren’t Gonna Need It) 37:11 - What services should I actually have? 41:00 - Contracts Between Services 48:29 - Advice for Someone Getting Started as an Architect: Ward Cunningham’s c2 Wiki The Pattern Oriented System Architecture Series