Engineering Culture by InfoQ

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Bernie Maloney of Persistent Systems about servant leadership and bringing out human potential. Why listen to this podcast: - Servant leadership is about creating a space through which other people can succeed and stepping back to let them do so. It matters because it requires empathy and compassion. - Organizations that don’t change to the new ways of working are being disrupted out of existence - Teams need to learn new ways of working, especially collaboration over individual specialization - There are no models and structures in place to help leaders make the jump to letting go and trusting their teams to do the work – this is new territory. More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2OcVejX You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2OcVejX

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Dave West, Chief Product Owner of Scrum.org about the state of Scrum, the latest revision to the Scrum Guide, the rise of Digital and the way Scrum.org maintains its courseware. Why listen to this podcast: • Scrum continues to be the dominant force in agile/digital/lean startup approaches • As complexity grows in our world the value of Scrum continues to grow • If you’re not doing Scrum per the book it doesn’t mean you’re “wrong”, just don’t call it Scrum • It’s not optional to improve how you work – it’s mandatory! • Scrum is fundamentally about dealing with complexity and improving productivity • Digital is about building organisations that are very different and able to take advantage of new technologies with new business models • Organisations need to move very strongly towards a product mindset and a product structured organisational architecture More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2xjpDDv You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2xjpDDv

In this podcast recorded at the Agile India conference Shane Hastie, Lead Editor for Culture & Methods, spoke to John Le Drew about solving technical problems by addressing the people issues. Why listen to this podcast: • Very diverse teams will naturally have conflict, but they still produce better outcomes despite the journey being more of a struggle to get there • Cognitive biases are real and are an evolutionary survival tactic and we need to be very mindful of them • We all like to think that we aren’t biased, but the imbalances in team formation and hiring practices are still perpetuated • We can’t reprogram our brains to remove biases, the way to overcome them is to be aware of them • If you address your people as unique human beings with individual needs and work out how to support them in the best way possible for their needs then you will get better outcomes More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2x79tfD You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2x79tfD

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Aurynn Shaw about how DevOps, Microservices and other “technical” approaches are in fact cultural constraints on technical ideas and what’s needed to make the culture sustainable. Key takeaways: * Running and testing a program on the developer desktop is not running the program * You must rethink the approach to building the software based on the way it will be deployed * DevOps isn’t about the tooling – it is about the context in which we find ourselves * Sustainable DevOps is about understanding the system that makes up the organisation ecosystem and what needs to change to enable the new ways of working * Design the system to help prevent dangerous actions rather than laying blame when something goes wrong * As a technologist you want to say “yes” – fix the systems around you that force you to say “no” * When examining the system we will discover that we’ve done things that we’re not happy about and must accept that they happened without apportioning blame

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Sanjeev Sharma, a Distinguished Engineer at IBM, on the challenges for large enterprises adopting DevOps at scale and what it really means to have a DevOps culture Why listen to this podcast: • There is no single “why” for adopting DevOps – each organisation is unique and the adoption approach should be based around what they are trying to optimize • DevOps is not a methodology – it is a set of guiding principles • As more and more parts of the business get to the higher levels of maturity you get to DevOps adoption at scale • The biggest challenge to adopting DevOps in a large enterprise is overcoming cultural inertia • The cultural impact of DevOps needs to be about building trust across silos in the organisation • There is a need for DevOps coaches who have skills that go deep into the operations areas, not just rebranded Agile coaches More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2wmiDEv You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2wmiDEv

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Johanna Rothman and Esther Derby about their memories of Gerald M. (Jerry) Weinberg who passed away on the 7th of August 2018. Why listen to this podcast: • Jerry Weinberg was a highly respected thinker and author • He was instrumental in defining some of the key elements of systems thinking and quality practices for software development • The rule of three – one option is a trap, two is a dilemma and three breaks logjam thinking to enable creativity • “It’s always a human problem” • Jerry inspired people to look at things in different ways • Jerry’s advice to anyone who wanted to be like him – become the best version of yourself More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2vSo7r7 You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2vSo7r7

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Michael Cote from Pivotal Labs about “programming the business” to enable support for automation and moving towards DevOps. Why listen to this podcast: • It’s possible to move from deploying on a yearly basis to a daily basis • Adopting a new process or approach often improves things dramatically, frequently because what was being done before was not effective rather than because of the effectiveness of the new way • Change the structures so teams are focused on products, not projects, ensure all the roles needed are in the team and that they are fully dedicated to working on the product • The rift in many organizations between “the business” and IT means that business people don’t expect the software to be agile and responsive to their needs • Businesses which were founded in the tech space are inherently agile and they run using these approaches all the time. The challenge is bringing “traditional” businesses down the same path More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2P3dud4 You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2P3dud4

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Dan Kreigh about his experiences as the lead structural analyst working on SpaceShipOne and his personal interest in designing and building a flying car. Why listen to this podcast: • Building SpaceShipOne was an iterative and incremental project • There are many parallels between the development of SpaceShipOne and an agile software product • Dan’s definition of a flying car is one that you can drive on the freeway and to the store, then drive to an airport and take off and fly to your next destination • There are a number of debates about the best designs for flying cars with multiple different approaches to addressing the challenges • Dan’s approach is to build a flying car which will fit in a home garage using well understood technologies and incremental development More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2KfKpYo You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2KfKpYo

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jeff Dalton about the challenges of agile adoption in large organizations and the need to teach agile leaders how to teach so they can lead the cultural shift that is needed Why listen to this podcast: • The marketing of agility is going far better than the actual on the ground adoption • When process-centric, low trust organisations adopt agile they bring that approach to their agile practices • The link between the soft skills and the hard technical practices of agile is what enables high quality and real agility, but many senior managers haven’t made the connection for themselves • There is no need for a new framework – the need is to enable leaders to leverage agility and teach that to other leaders and to their teams • The re-emergence of a focus on craftsmanship is a great thing, but it is not enough More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2LOc5bq You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2LOc5bq

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Edith Harbaugh of Launch Darkly on the way she and her cofounder have deliberately engineered their organisation’s culture Why listen to this podcast: • A good engineering culture is one where there is a lot of respect for different people and roles • Start by good intent on behalf of your colleagues – everyone is doing their best • Be open to continually learning – mistakes will happen, learn from them in a blame-free way • Another aspect of respect is ensuring meetings are purposeful, have the right people involved, have a clear agenda and stay on time • To build mastery it’s OK to be bad at something in the beginning and deliberately get better • Sharing the reason why the customer chooses the product, rather than how much was earned from the sale, is motivational More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2LewoiU You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2LewoiU