Podcasts about when agile

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

When Agile was still a young framework, we found that people struggled with the idea that they did not need a ton of heavyweight paperwork up front to be successful. In today's episode of The Daily Standup join V. Lee Henson as we explore the new enemy. Bad Agile or dogmatic agility has taken over. In a time where organizations are hyperfocused on quantity, they are all quikly abandoning quality and not allowing for a sustainable build and release framework. In this episode we identify the problem and talk about short term solutions. 

In this episode, Kendall, rachel, and Kristina talk about: * A rare actual degree in the field of Information Systems/IT! * The value of informational interviews * How product management works at a huge aerospace company * Going from a giant corporation to a much smaller company * Culture-first as an approach to running a business * How great it is when the people who build the product have good context from customers * Being the glue when there are a lot of managers in the mix * When Agile doesn't really scale anymore * What changes when you go from managing ICs to managing managers * The dynamics of tenured vs newer leadership with external experience * Signs of seniority and experience in engineering leaders * Shiny, shiny context! * Reasons people in leadership tend to like solitary activities * Kendall's uplifting sense of irony You can find Kristina on the internet on LinkedIn and on Twitter as @kemmeroo Special thanks to Mel Stanley for our theme music

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

When Agile coaches Nidhi Sharma and Michael Callahan are looking at changing someone’s mindset and changing the way that they behave and work, they want to start with a purpose. The pair tied it all together in their Four R’s model for transitioning to Lean thinking: - Why are we doing this work? (Right Reasons)- What work would fit that purpose? (Right Work)- Who needs to be in the room to have those conversations? (Right People)- What is the last responsible moment for doing the work? (Right Time) Howard Sublett hosts. Get in touch with our guests: michael.p.callahan@accenture.com and nidhi.t.sharma@accenture.com And find our podcast host on Twitter: @howardsublett Podcast library: www.agileamped.com Connect with us on social media! Twitter: twitter.com/AgileAmpedFacebook: www.facebook.com/agileampedInstagram: www.instagram.com/agileamped/

The Project Management Office (PMO) has traditionally been responsible for providing governance over projects, programs and portfolios; ensuring projects are managed according the standards set forth by the PMO; and to provide reporting on progress to leadership. When Agile is introduced into an organization, along with new ways of tracking work, self-organizing teams and new ways of understanding priority, the value the PMO provides comes into question. In a recent blog post, LeadingAgile SVP and Executive Consultant Marty Bradley addressed the question “Should the PMO Go Away?” In this episode of LeadingAgile’s SoundNotes, Marty and Dave dig deeper on this topic and explore what PMO’s (and PMO Leaders) need to do in order to remain relevant to an organization transitioning to Agile. Show Notes 00:08 Podcast Begins 00:35 What does a LeadingAgile Executive Coach actually do 01:40 When the Executives say “Stop saying Agile.”, it’s actually a good thing. 3:05 Should the PMO go away? Who’s asking and why? 07:12 Why do we need a PMO and governance if the teams are supposed to be self organizing? 08:38 If we do not have trust, how can we have self-organization and Agility? 09:39 All night deployments and the impact of not trusting the team 10:43 When the people who “know better” create a system that fosters missed deadlines and failure, they create a very dysfunctional form of predictability 12:15 How the PMO can maintain its’ relevancy in an organization transitioning to Agile. 13:27 How do we maintain the necessary non-agile elements when we transition to Agile? 14:55 How can we have more empathy for the members of the PMO and the massive personal and career change they are facing in maintaining the stability of a traditional approach while supporting the change to Agile? 16:29 Changing the focus and the metrics used to track the work 17:10 The impact on Development Managers 18:12 Why would I want to eliminate the need for my own position (if we transition from waterfall to Agile) 18:42 Coping with transition: “This is my job,…I got a family…What am I supposed to do?” 19:55 Maintaining a balance between preserving the necessary domain knowledge and changing as fast as you can 20:29 What PMO Leaders need to know before the Agile transition team shows up - “Not everything needs to be perfect Agile.” 23:51 If I am in a PMO and I want to get up to speed and maintain my own relevancy, what do I need to learn? 25:10 “I’d look at my company and figure out what is value in my company?” How do you define value? 27:02 Finding your organization’s own definition of value 27:46 Closeout Contacting Marty Email: marty.bradley@leadingagile.com Twitter: https://twitter.com/AskCoachMarty Contacting Dave Email: dave.prior@leadingagile.com Twitter: https://twitter.com/mrsungo Related Links: Should the PMO Go Away? (Marty’s blog post mentioned in the interview) http://bit.ly/2jwshAS Cost of Delay http://bit.ly/2jVLfx4 Agile Governance at eVestment - A More Agile Approach to PMO http://bit.ly/2khDBhq Agile Governance - An interview with Liana Dore from Agile 2016 http://bit.ly/2kRXj6F Kanban http://bit.ly/1cXGeK9 Lean Startup http://bit.ly/1ky8H1h Don Reinertsen “The Principles of Product Development Flow” http://amzn.to/2jYlyOY Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/

The Software Process and Measurement Cast features my interview with Jeff Dalton.  Jeff returns to the Software Process and Measurement Cast to discuss the 12 attributes of successful Agile organizations. Jeff talks about the relatively small set of attributes that successful Agile organizations possess and exhibit. These attributes don’t occur by accident, but rather are a reflection of hard work and consistency of purpose.  We can all reflect and adopt these attributes in our pursuit of success. Jeff shows us how! Jeff’s Bio: Jeff Dalton is President of Broadsword, a Certified Lead Appraiser, CMMI Instructor, ScrumMaster and author of “agileCMMI,” Broadsword’s leading methodology for incremental and iterative process improvement, as well as many published articles and ebooks on performance innovation. Jeff has been selected Keynote Speaker at numerous conferences including the International Conference on CMMI in Lima, Peru, the PMI Great Lakes 2013 Symposium, the 2014 QUEST Conference and Expo, the CMMI SEPG Conference 2014, the CMMI Global Congress 2015, the PM Symposium Indianapolis 2015 and the PM Symposium Chicago 2015.  He has appeared multiple times at Agile Development West, Better Software, Agile Processes and Tools, AgileDC, and at Software Process Improvement Network (SPIN) and Agile Leadership Network (ALN) meetups throughout North America. Jeff served as the Chairman of the Partner Advisory Board at the Software Engineering Institute (SEI) and CMMI Institute from 2011-2014 during their transition period.  He has been president of Great Lakes Software Process Improvement Network, and is a recipient of the prestigious Software Engineering Institute’s SEI Member Award for Outstanding Representative for his work uniting the Agile and CMMI communities through his popular blog “Ask the CMMI Appraiser.” He holds degrees in Music and Computer Science and builds experimental airplanes in his spare time.  Jeff can be reached at appraiser@broadswordsolutions.com. Contact Data: Email: appraiser@broadswordsolutions.com. Twitter: @CMMIAppraiser Blog: http://askthecmmiappraiser.blogspot.com/ Web: http://www.broadswordsolutions.com/ also see: www.cmmi-tv.com Previous Appearances on the podcast: SPaMCAST 296 – Jeff Dalton, CMMI, Agile, Resiliency SPaMCAST 176 - Jeff Dalton, CMMI, Scrum and Agile Call to Action! Review the SPaMCAST on iTunes, Stitcher or your favorite podcatcher/player and then share the review! Help your friends find the Software Process and Measurement Cast. After all, friends help friends find great podcasts! Re-Read Saturday News Remember that the Re-Read Saturday of The Mythical Man-Month returns this week when we tackle the essay titled “The Other Face” Check out the new installment at Software Process and Measurement Blog.   Upcoming Events Agile Development Conference East November 8-13, 2015 Orlando, Florida http://adceast.techwell.com/ I will be speaking on November 12th on the topic of Agile Risk. Let me know if you are going and we will have a SPaMCAST Meetup. Next SPaMCAST The next Software Process and Measurement Cast returns to the topic of Agile Project Charters, tackling the concepts needed to scale a charter to an Agile project or program. When Agile projects scale up to handle larger efforts additional steps are often required. Additional steps can lead to bloat if you do not take care. We will also have a new installment of Jeremy Berriault’s QA Corner! We discussed the definition of test cases and why they are so important to delivering quality code! 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 for you or your team.” Support SPaMCAST by buying the book here. Available in English and Chinese.