Evolving Culture and Values. Understanding the Tradeoffs. Growth through Failure. The Importance of Leadership and Open Communication.
Pedram Keyani discusses the importance of evolving the culture and values of an organization, dealing with tradeoffs, learning from failure, proper leadership and open communication.
Kevlin Henney addresses the motivation, implications, pros and cons of a craftsmanship view of software development, as well as touching on other metaphors and their implied practices.
Dror Helper shares from his experience implementing Agile practices in his team, outlining the do and don'ts that can make all the difference. He addresses teams working in a non-agile environment.
Sergejus Barinovas discusses the challenges, failures and actual steps required to move an organization to continuous delivery and as follows - continuous happiness.
Andrew Stellman affirms that having great teams with a collaborative mindset takes more than great people, visionary leaders and good organizers, providing insights into what needs to be added.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
Christian Legnitto offers insight in some of the tools and processes used by Facebook for pushing new updates to their mobile apps.
Steve Rogalsky explains the basics of user story mapping based on real case studies, showing pictures depicting projects’ progress and how that influenced iterative development and process visualization.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
Dario Nardi shares key insights on how the brain works and suggestions on tapping the power of individuals’ talents in order to be put together at work.
Seb Rose explores the choices a team needs to make when considering which Agile test practices to adopt, urging teams to practice, practice, practice until they are happy with the way they code.
Michael Sahota discusses top 10 Agile gotchas: when release is ready, sprint meetings take too long, no retrospectives, people aren’t working together, getting new stories, stand-ups are boring, etc.