Raffi Krikorian discusses the software engineering challenges met re-architecting Twitter and the cultural change impact that came with it.
Jim and Michele McCarthy discuss the Core Protocols that make a common platform for an organization’s culture design.
Jason Little discusses how to avoid an organizational change failure when introducing Agile by leveraging principles of Lean Startup and Customer Development.
Jim McCarthy keynotes on the importance of a proper agile culture within organizations, providing examples from his own experience.
Floyd Marinescu shares how the virtual teams behind InfoQ.com and QCon are run; Processes, tools, & mindset needed to succeed in a completely virtual work environment that delivers happiness and alignment. Each practice is explained in the context of how it fosters purpose, autonomy, mastery, and a sense of progress.
Greg Brockman shares Stripe's principles powering their software projects and the culture instilled to avoid the usual software engineering traps: failed rewrites, delayed timelines, etc.
Ted Tencza shares lessons learned innovating at Atlassian and Bigcommerce, including programs that worked (FedEx/ShipIt/Hackathons, 20% time) and programs that failed (dedicated Innovation Team).
Do Agile Methods Contain the Seeds of Their Own Destruction? (Safety and Our Ability to Learn from Failure)
Amr Elssamadisy explores the link between safety and success of agile methods, explaining what can be done to change the culture of an organization to create a base where agile methods can flourish.
Jim McCarthy discusses culture hacking, a distinct kind of culture engineering, expressing a particular hacker ethos, an ethos originating in the world of software hacking, promoting freedom, openness, and embodying rationality and design elegance.
Daniel Mezick explains how to deliver happiness through the intentional design and implementation of good-game mechanics inside your team. Work is BROKEN when it is not fun to play. In this session, we provide tools for playing an all-new game of engagement and team learning.
Gojko Adzic, Lukas Oberhuber discuss how the thinking around the role of tests and testing evolved, the problems the team faced and the decisions they took to overcome technical and cultural issues.
Ole Friis Østergaard discusses software development addictions: becoming aware of them, controlling them, getting rid of bad habits by admitting them and changing through practice.