Engineering Culture by InfoQ

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jim Rose of Circle CI about building a great engineering culture in a distributed, remote team. Why listen to this podcast: • Hiring engineers is a difficult task • Working in a completely remote organisation takes a particular type of person • It’s crucial that the engineering teams understand and empathise with their customers • You won’t find new and creative ways to solve problems unless you experiment and try new things, and some of those things won’t work • Ensure that your recruiting and hiring practices match the values of the company and that the onboarding process reinforces this • Ensure there is no “in vs out” – ensure everyone has the experience irrespective of where they are located More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2PB0oHh 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/2PB0oHh

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jeff Foster of Red Gate on their approach to continuous learning through 10% time, open space and running an internal conference. Why listen to this podcast: • The best software is software that people • The only secret to great engineering is simplicity • No matter how hard you try to enable people to take the 10% time, they take their deadlines to heart and the natural inclination is to focus on the work rather than the learning time • Teams should not focus on the backlog items they are completing, rather on the difference they are making for the end user of the product • Running a conference is tough, but by engaging the people in the event organisation it can be powerfully successful More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2zdk21C 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/2zdk21C

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Jutta Eckstein and John Buck about their new book: Company-wide Agility with Beyond Budgeting, Open Space and Sociocracy – BOSSA-Nova Why listen to this podcast: • The pressing question: if democracy is good, why aren’t businesses using it • The new book is a theoretical framework for organizations to help agile spread philosophy across whole organizations • Just using Agile company-wide is not enough • In the VUCA times we live in require that companies are able to make quick and fast decisions – sociocracy provides this ability • Beyond Budgeting provides guidance on how finance, accounting, HR and management needs to change in the new environment • Open Space is a great way to bring alignment and commitment into the organization More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2PNUOOp 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/2PNUOOp

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Fred George about the need to solve “fuzzy problems” and approaches to doing so. Why listen to this podcast: • Fuzzy problems are ones which don’t have precise answers but they are the places where most money is being made in the modern economy • Applying the thinking that works for traditional problems to fuzzy problems causes frustration because the underlying assumption that the problem will have a single solution is wrong • The rules for solving fuzzy problems are related to the speed of trying out ideas and learning rather and so competitive advantage accrues to fast delivery • Most organisations have a mix of traditional and fuzzy problems – segregate the teams and use the appropriate approach for the problem type • If you’re doing agile the same way in all your teams you’re probably not doing agile anymore More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2J1xBpg 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/2J1xBpg

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Todd Little, CEO of LeanKanban Inc about how organizations can use Kanban to identify bottlenecks and improve flow in their business processes. Why listen to this podcast: • Kanban is a more natural way of working for more experienced teams • Kanban tells you to start wherever you are at and make change incrementally • Only if you deeply understand your system can you deeply improve it • Kanban helps collaboration through allowing the team focus on where the work is and what we can do to get the work to flow through the system • Continuous improvement is the fundamental underlying idea of Kanban More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2OMVuq5 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/2OMVuq5

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Linda Rising about Daniel Kahneman’s work on Thinking Fast, Thinking Slow, overcoming bias in the employment process and resisting social pressure in decision making. Why listen to this podcast: • Daniel Kahneman’s book Thinking Fast Thinking Slow based on the research he did with Amos Tversky into how the human brain works, for which Kahneman win the 2011 Nobel Prize for Economics, is hard to read. Linda wants to make the ideas more accessible • One part is known as System One – the part that reacts quickly, never sleeps, where our cognitive biases reside and is the home of our expertise • The second part known as System Two is the conscious mind, somewhat associated with the prefrontal cortex, it is the part that sleeps and wakes and where considered decision making happens • In the hiring process, and other important decisions, it is vital to involve more than one person because awareness of the possibility of bias enables you to question each other’s decision-making process and invoke System Two to examine decisions more objectively • Social pressure results in biases being reinforced, but a single dissenting voice can and des change the direction of bad decision making More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2NgG8Fm 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/2NgG8Fm

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