LeadingAgile SoundNotes: an Agile Podcast

John Tanner is going to be at Agile 2018 delivering his talk entitled: Agile Metrics - The GQM Approach. The session will take place on Wednesday, August 8 at 10:45 AM. If you're new to GQM, it stands for Goal - Question - Metrics—which has been John's key area of focus for quite some time. If you're working towards gaining clarity around what data to collect at the different levels of your organization—and what to do with the information those metrics provide—John's session is one you won't want to miss. In this episode of SoundNotes, John provides a quick preview of some of the topics he'll be covering during his session in San Diego and some of the new elements he's included based on using these techniques in the field. Agile 2018 LeadingAgile Presentations Mike Cottmeyer - Agile Transformation Explained- Tuesday, August 7 • 15:45 - 17:00 John Tanner  - Agile Metrics - The GQM Approach- Wednesday, August 8 • 10:45 - 12:00 Paul Argiry  - Addressing Your CFO's Concerns To An Enterprise-Wide Agile Transformation- Thursday, August 9 • 09:00 - 10:15 Contacting John LeadingAgile: https://www.leadingagile.com/guides/john-tanner/ LinkedIn: https://www.linkedin.com/in/tannerjs/ Twitter: https://twitter.com/tannerjs Email: john.tanner@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com Or, if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

Creating a Definition of Ready is one of the best ways to help your Team(s) make sure they're only committing to work they can actually get done. It's also one of the best ways for a Product Owner to make sure they're not going to waste valuable time in Sprint Planning by asking the Team to work on things that aren't in an actionable state. In this episode of SoundNotes, Rick Austin and Dave Prior discuss how to go about creating a Definition of Ready and why it's so critical to your Team's ability to deliver. They also cover some examples of the types of things you might want to include in your Definition of Ready. BACKGROUND INFO If you'd like some background on this topic before listening, check out the following: Why You Need A Definition of Ready w/ Dave Nicolette(podcast) Definition of Ready- by Rick Austin (blog post) CONTACTING RICK If you'd like to reach out to Rick for more information, here is his contact info: Email: rick@leadingagile.com Twitter: https://twitter.com/rickaustin LinkedIn: https://www.linkedin.com/in/rickdaustin/ Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/  

In this episode of SoundNotes, Mike Cottmeyer and Dave Prior discuss how organizational Transformation continues to evolve. The conversation offers a brief preview of some of the things Mike will be covering at his Agile 2018session: “Agile Transformation Explained”http://sched.co/EUF1 During the interview, Mike and Dave discuss how the skill sets needed to lead and shepherd those Transformations have grown to include much more than what we would have expected from an Agile coach several years ago. They also explore how we continue to refine our understanding of what happens during organizational Transformation and how we can better prepare our clients for the changes they will experience.   LeadingAgile at Agile 2018 Mike Cottmeyer’s session “Agile Transformation Explained”will take place on Tuesday, August 7 at 3:45 PM.  You can learn more about it here: http://sched.co/EUF1 Paul Argiry’s session “Addressing Your CFO’s Concerns to an Enterprise-Wide Agile Transformation”will take place on Thursday, August 9 at 9:00 AM. You can learn more about it here: http://sched.co/EU93 John Tanner’s session “Agile Metrics - The GQM Approach”will be held on Wednesday, August 8 at 10:45 AM. You can learn more about it here: http://sched.co/EUCr Contacting Mike If you’d like to contact Mike you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/mike-cottmeyer/ LinkedIn: https://www.linkedin.com/in/cottmeyer/ Twitter: https://twitter.com/mcottmeyer Email: mike@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

This episode of SoundNotes focuses on Definition of Ready. A few weeks ago, Dave Nicolette created a post in Field Notes that was the result of a current debate in the Agile community about whether having a Definition of Ready helps, or harms our ability to deliver value for the customer. The episode begins with Dave Nicolette explaining Definition of Ready within the context of the LeadingAgile model. After that, he and Dave Prior discuss/debate the the pros and cons of DoR from their respective backgrounds (Developer vs. PM). Links From The Podcast The LeadingAgile Compasswww.leadingagile.com/our-compass/ Dave Nicolette's Field Notes Post "Should Agile Teams Have a Definition of Ready?www.leadingagile.com/2018/05/should…tion-of-ready/ Mike Cohn's blog post "The Dangers of a Definition of Readywww.mountaingoatsoftware.com/blog/the-d…n-of-ready Jeff Sutherland's Definition of Ready post on Scrum Inc. with comments from Michael Jameswww.scruminc.com/definition-of-ready/ If you'd like to check out a sample Definition of Ready, here is one provided by Kenny Rubin.www.innolution.com/blog/definition-of-ready For more on Alexander Laufer's work on Uncertaintywww.tandfonline.com/doi/pdf/10.1080…67.1994.9726951 Or you can read Mike Cohn's explanation here.www.mountaingoatsoftware.com/articles/t…ncertainty RUN FORREST RUN!youtu.be/x2-MCPa_3rU?t=44s Contacting Dave Nicolette• LeadingAgile: www.leadingagile.com/guides/dave-nicolette/• Twitter: twitter.com/davenicolette• LinkedIn: www.linkedin.com/in/davenicolette/• Contacting Dave Prior If you’d like to contact Dave you can reach him at:• LeadingAgile: www.leadingagile.com/guides/dave-prior/• LinkedIn: www.linkedin.com/in/mrsungo• Twitter: twitter.com/mrsungo• Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at:www.leadingagile.com/our-gear/training/

If you are working at an organization that is applying Agile practices across the enterprise, chances are,  somewhere early on in the transformation a tool was selected to help the teams manage their work and hopefully provide management with some kind of visibility into the work being done. One of the unfortunate truths about the tools is that while they are capable of doing a lot of things, most companies do not invest the time in setting the tool up to work for them. This often leads to teams struggling with having to adjust their practices to meet the tool and management not getting the visibility it needs into how the work is going. It doesn’t have to be this way. The tools can add a lot of value, but you have to get them set up right for that to happen. In this episode of SoundNotes, Jessica Wolfe shares a story about how she was able to help one organization adjust the tool to provide the business with the information the CEO needed to understand how work was progressing across the portfolio and how it was tying back to the company’s strategic objectives. As they dig into the story, Jessica and Dave explore what kinds of information the tools are able to provide, and how that can help your organization understand what is happening at a level of detail that includes strategic value, financial metrics, risk and much more. She also manages to completely change Dave’s long mistrust of anything other than post-its and sharpies. Contacting Jessica If you’d like to contact Jessica you can reach her at: LeadingAgile: https://www.leadingagile.com/guides/jessica-wolfe/ LinkedIn: https://www.linkedin.com/in/thejessicawolfe/ Twitter: https://twitter.com/thejessicawolfe Email: jessica.wolfe@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com Send Us Your Questions If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com Upcoming Classes And if you are interested in taking one of our upcoming Certified Scrum Master or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

In this episode of SoundNotes, Dean Stevens and Dave Prior dig into Capability Mapping, how it works and why it is such an important part of the transforming your organization. Capability Mapping is a technique that can be used to quickly gain greater awareness of how an organization does what it does, what processes it uses to do what it does, and where there are opportunities to remove waste and optimize flow. During the interview you’ll hear Dean walk through the steps of identifying the processes an organization has in place, understanding the value each process provides, and finding ways to optimize these processes for better performance. This approach will also help identify gaps your organization may need to resolve in order to achieve its’ goals. Links from the Podcast For some background on capability mapping, check out this Harvard Business Review Article:https://hbr.org/2008/06/the-next-revolution-in-productivity Contacting Dean If you’d like to follow up with Dean directly, here is how to reach him: Web: https://www.leadingagile.com/guides/dean-stevens/ Twitter: https://twitter.com/leanopinions LinkedIn: https://www.linkedin.com/in/stevensdean/ Email: dean@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

For any organization moving to Agile, the question of how to handle tracking and reporting is going to present challenges. If you are moving from a traditional environment, there may be an expectation (dependency) on traditional forms of reporting. If you are starting out with an electronic tool, there may be a wide range of reporting options. Just because you an create a report, does not mean you should. If your audience doesn't know how to digest the information, you may create cognitive dissonance and (cue inner Yoda voice) dissonance leads to confusion leads to fear, fear leads to "help". #thatwassarcasm Derek Huether recently put up two blog entries that dig into come of the challenges that come with determining what to track and how to report on it.   In this episode of SoundNotes, Derek and Dave pick up the conversation but come at it from a different angle.  If your PMO is stuck the middle of some quasi-agile/waterfall environment and trying to figure out how to provide meaningful information to the folks upstairs, this podcast may be able to help. Links from the Podcast How to Define Metrics to Reach Better Business OutcomesAn Introduction to OKR: Objectives and Key ResultsContacting Derek If you’d like to contact Derek you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/derek-huether/LinkedIn: https://www.linkedin.com/in/derekhuether/Twitter: https://twitter.com/derekhuetherEmail: derek@leadingagile.comContacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/LinkedIn: https://www.linkedin.com/in/mrsungoTwitter: https://twitter.com/mrsungoEmail: dave.prior@leadingagile.comIf you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

One of the most important things you can do to help your team be successful is to ensure they have a Definition of Done. Once you have it, you need to revisit in in each Retrospective meeting to make any updates and you need to explain it to the Stakeholders in every Sprint Review. A Definition of Done is more than just Acceptance Criteria. These are the conditions that must be met for your organization to safely release work into the wild. This is especially critical if you are working in an environment where there is a difference between "done" and "shippable". In this episode of SoundNotes, Tim Wise and Dave Prior talk through why a Definition of Done is so critical to your team successfully delivering work, what level of detail you should include in your DoD, and how to create one. Links from the Podcast Why You Need A Vision Statement Contacting Tim Email: tim@leadingagile.com LeadingAgile: https://www.leadingagile.com/guides/tim-wise/ LinkedIn: https://www.linkedin.com/in/timwise/ Twitter: https://twitter.com/timswise Scrum Atlanta User Group: https://www.meetup.com/agile-38/ Contacting Dave Email: dave.prior@leadingagile.com LeadingAgile: http://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo/ Twitter: http://twitter.com/mrsungo Personal blog: http://drunkenpm.net 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: http://www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

For Development Teams transitioning to Agile one common challenge is breaking the work down into small vertical slices that can go from a Post-It Note to shippable product in 2-3 days. Most of the time, (there are always exceptions) the issue is not that the work cannot be broken down, but that the Development Team is accustomed to looking at the work in a more traditional way and they are not able to see how they could break it down into smaller actionable elements that can be developed independently and provide value and the opportunity to learn. If you're working with a team that is struggling with this, and you do not come from a technical background, the issue may be even more daunting. Without the in-depth knowledge of how the work might be executed, many people will feel ill-at-ease challenging the Dev Team's assertion that the work is just that big and can't be broken down. In this podcast, Tim Wise and Dave Prior take on the topic of what to do when the Development Team can't break down the work. They share how they've each approached this challenge with teams and offer some ideas about how you could help your team find a way to break the work down. Agile Day Atlanta http://agiledayatlanta.com Contacting Tim Email: tim@leadingagile.com LeadingAgile: https://www.leadingagile.com/guides/tim-wise/ LinkedIn: https://www.linkedin.com/in/timwise/ Twitter: https://twitter.com/timswise Scrum Atlanta User Group: https://www.meetup.com/agile-38/ Contacting Dave Email: dave.prior@leadingagile.com LeadingAgile: http://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo/ Twitter: http://twitter.com/mrsungo Personal blog: http://drunkenpm.net 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: http://www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

One of the common misconceptions about Agile is that there's no documentation. This simply isn't true. The second line of the Agile Manifesto reads: “Working software over comprehensive documentation” This doesn’t mean that we don’t have documentation. It just means that the folks who created the manifesto did not see the value in delivering the documentation at the expense of delivering working, tested software. In a recent Certified ScrumMaster class in NYC, one student raised an issue she was experiencing with her Development Team who is deeply committed to the “no documentation” camp. In this podcast, Dave Prior is joined by Anil Jaising (who helped to facilitate the New York class) to discuss the myth of no documentation, the truth about documentation in Agile, and how that can play out in a highly regulated/audited environment. Events Mentioned in the Podcast Big Apple Scrum Day: https://www.bigapplescrumday.org NYC Scrum User Group: https://www.meetup.com/NYC-Scrum-User-Group/ Contacting Anil Email: anil@nimblebydesign.com Twitter: https://twitter.com/aniljaising LinkedIn: https://www.linkedin.com/in/aniljaising/   Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

This week, at the 2018 North American Global Scrum Gathering, the Scrum Alliance and Scrum co-founder, Dr. Jeff Sutherland, announced the creation of a new joint venture to train, coach, and promote Scrum@Scale. Scrum@Scale is an extension of the Scrum Framework that is designed to deliver business Agility across an entire organization. Dave Prior had a chance to sit down with Jeff during the Scrum Gathering and ask some questions about his partnership with the Scrum Alliance, Scrum@Scale, and how it can help organizations achieve greater business Agility. Links from the Podcast If you’d like to read the press release on the joint venture, you can find it here: https://tinyurl.com/yc5z4w3p Here is a link to the Scrum@Scale Guide Here is a link to Jeff's latest book, "Scrum, The Art of Doing Twice The Work In Half The Time".   Contacting Dr. Jeff Sutherland If you’d like to contact Jeff you can reach him at: Scrum@Scale: https://www.scrumatscale.com Twitter: https://twitter.com/jeffsutherland Email: jeff@scruminc.com Jeff's books on Amazon: https://amzn.to/2H9ZePk Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

A few weeks ago Dave Nicolette put up a blog post in FieldNotes called "Putting the Journey Into Journeyman" (https://tinyurl.com/ybehorv7). I really enjoyed the post and wanted to ask Dave some additional questions about the idea of a Journeyman, how to reach that state, and what happens once you get there. In this episode of SoundNotes, Dave and I discuss what a Journeyman is, and what a Journeyman isn't. We discuss the skills LeadingAgile expects from a software Journeyman, how to know if you've reached this state, and what you should expect to happen after you get there and each one of the states that comes after Journeyman. (Oh Look!  A Squirell!) This podcast is also a great resource if you have been interviewing with LeadingAgile and you'd like to get a handle on the mindset of the folks who work here and what we expect of one another. If you'd like to check out Dave's original blog post, you can find it here: "Putting the Journey Into Journeyman" -https://tinyurl.com/ybehorv7  Contacting Dave Nicolette LeadingAgile: https://www.leadingagile.com/guides/dave-nicolette/ Twitter: https://twitter.com/davenicolette LinkedIn: https://www.linkedin.com/in/davenicolette/ Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

In almost every CSM or CSPO class that Dave teaches he gets asked to explain the difference between Scrum and Kanban. So, in this episode of SoundNotes, Jessica Wolfe, Derek Huether, and  Dave take turns responding to the question and detailing some of the main differences between two of the most popular approaches to Agile. If you'd like to reach out to Jessica, Derek or Dave for more—here's their contact info: Contacting Jessica If you’d like to contact Jessica you can reach her at: LeadingAgile: https://www.leadingagile.com/guides/jessica-wolfe/ LinkedIn: https://www.linkedin.com/in/jessica-wolfe-ab025a36/ Twitter: https://twitter.com/thejessicawolfe Email: jessica.wolfe@leadingagile.com Contacting Derek If you’d like to contact Derek you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/derek-huether/ LinkedIn: https://www.linkedin.com/in/derekhuether/ Twitter: https://twitter.com/derekhuether Email: derek@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

“Culture is just the boogeyman people use when they don't know how to articulate an organizational change management strategy that executives will buy into.” ~ Mike Cottmeyer In this episode of SoundNotes, LeadingAgile CEO, Mike Cottmeyer shares his thoughts on why we need to stop blaming culture when organizations are unable to adopt Agile. During the interview, Mike and Dave dig into the reasons why many of the organizations that struggle with Agile are dealing with deeply rooted mechanisms that extend far beyond culture. Unfortunately, one of the most common refrains in the Agile community is that the culture is the primary thing that must be addressed, and once that is solved, the rest will take care of itself. For many organizations that buy into the promise of Agile without having clarity on the organizational impediments they must overcome for Agile to be able to exist, maybe culture isn't the best place to start. If you'd like to read Mike's blog post on the topic, you can find it here: https://bit.ly/2pO8YU4 Contacting Mike If you’d like to contact Mike you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/mike-cottmeyer/ LinkedIn: https://www.linkedin.com/in/cottmeyer/ Twitter: https://twitter.com/mcottmeyer Email: mike@leadingagile.com Contacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/ LinkedIn: https://www.linkedin.com/in/mrsungo Twitter: https://twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you're interested in taking one of our upcoming Certified ScrumMaster or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/

This episode of SoundNotes features a question submitted by a student in one of Dave's recent CSPO classes. Maheesh’s question centers on how to apply Scrum on a project that involves BI reporting and ETL. Since Jessica Wolfe and Derek Huether both have far more experience in that type of work than Dave does, he asked them to help him respond to the question. Here's the question we got from Maheesh: “As a Product Owner for a BI reporting platform I typically get requests for new reports and this might entail bringing the data from a CRM platform or any other platform into the data warehouse so that that requires building ETL for that and developing the report on top of that. Which typically cannot be done within a two week Sprint. So how would I go about taking this requirement from the customer and converting into shippable user stories that can be delivered through a Scrum methodology?” If you'd like to reach out to Jessica, Derek or Dave for more, here is their contact info: Contacting Jessica If you’d like to contact Jessica you can reach her at: LeadingAgile: https://www.leadingagile.com/guides/jessica-wolfe/LinkedIn: https://www.linkedin.com/in/jessica-wolfe-ab025a36/Twitter: https://twitter.com/thejessicawolfeEmail: jessica.wolfe@leadingagile.comContacting Derek If you’d like to contact Derek you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/derek-huether/LinkedIn: https://www.linkedin.com/in/derekhuether/Twitter: https://twitter.com/derekhuetherEmail: derek@leadingagile.comContacting Dave If you’d like to contact Dave you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/dave-prior/LinkedIn: https://www.linkedin.com/in/mrsungoTwitter: https://twitter.com/mrsungoEmail: dave.prior@leadingagile.comIf you have a question you’d like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com And if you are interested in taking one of our upcoming Certified Scrum Master or Certified Scrum Product Owner classes, you can find all the details at https://www.leadingagile.com/our-gear/training/