Håkan Råberg and Jon Pither on introducing Clojure to an investment bank team having a large Java code, dealing with cultural differences, the lessons learned, and ways of dealing with legacy code.
Michael Margolis discusses how the outsider can play a positive role in the process of the team’s cultural change by sharing his own story, his life experience.
Eric Steven Raymond advices on building cultures within organizations drawing examples from the open source culture hacking he was part of.
Vickie Gray explains how to change an organization’s culture one person at a time using the Core Protocols developed at McCarthy BootCamp under the lead of Jim and Michele McCarthy.
Susan Standiford discusses the social psychology, culture and team dynamics challenges faced while moving RueLaLa to a new platform.
James Sutton presents why Kanban works well in software development and how it can improve the culture of a group using it. Sutton also touches complementary Lean ideas and tools.
Changing tools is easy when compared to changing people and processes. How can we cultivate an organization’s culture to identify and solve DevOps problems?
Experiences and lessons learned facing DevOps problems in the IT trenches (even if they weren’t calling it DevOps!). The good, the bad, the surprises, and ideas for the future.
"Being Agile" is a state of mind achieved when the practitioner has transcended Agile practice (phase three of agile according to Kent Beck). This presentation will show how following agile values, ideas, and practices lead the practitioner to the threshold of transcendence. We will also talk about how to take the final step: from "Doing Agile" to "Being Agile!"
The state of the art in political technology evolved radically 2004-2008. In 2004, software development in Democratic political campaigns consisted of a few rag-tag hackers taking shots in the dark and building applications. In 2008, political start-ups built innovative social applications that raised nearly 1/2 billion dollars, and elected a President.