Dan Lines, (@linknfg182, COO @LinearB_Inc) talks about asynchronous development for remote teams, managing business-level discussions,  bringing greater transparency and accountability to projects, and identifying early signs of developer burnout.  

SHOW: 490

SHOW SPONSOR LINKS:

• BMC Wants to Know if your business is on its A-Game
• BMC Autonomous Digital Enterprise
• Datadog Security Monitoring Homepage - Modern Monitoring and Analytics
• Try Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt.
• Onix - The Leading Cloud Solutions Provider
• Onix - Cloud data strategy workshop offer (FREE, $2000 value)

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW NOTES:

• LinearB Homepage
• Asynchronous Development for Remote Teams
• Asynchronous Development Manifesto
• Dev Interrupted podcast

Topic 1 - Welcome to the show. Tell us a little bit about your background, and what brought you to be so focused on developer productivity and team agility? 

Topic 2 - We want to talk about remote teams today, but before we get started, let’s talk about how much this past year has changed the day-to-day life of application development teams.

Topic 3 - You’ve spoken about Asynchronous Development (for Remote Teams) and how the pandemic sort of created the environment that has been evolving for years. Tell us about the concept and some of the things companies can do to embrace it?  

Topic 4 - LinearB is a tool/platform that gives teams visibility into what’s happening with projects (status/velocity), backlogs, bottlenecks, etc. How do you think about transparency and accountability for teams, since software projects can get fairly complex? 

Topic 5 - How much does it help in conversations with business leaders, who might not have as much understanding of how development teams work, to have the data trends right in front of them?

Topic 6 - You make a point that you can see “burnout” happening within teams or around individuals. What are some tips to reduce that, or address it in ways that it can lead to better long-term conditions within teams?

FEEDBACK?

• Email: show at thecloudcast dot net
• Twitter: @thecloudcastnet