Steve Peha describes how culture can derail a seemingly perfect Agile project. He then details how we can see and incrementally modify cultures by focusing on agreements. Agreements govern how we work together; they govern individuals and their interactions. By deliberately focusing on making, keeping, confronting, and renegotiating agreements, we can change our culture to support Agile teams.
Cliff Click explains 0xdata's H20, a clustering and in-memory math and statistics solution (available for Hadoop and standalone), writing H20's memory representation and compression in Java, low latency Java vs GCs, and much more.
Gabby Benefield has spent much of the last three years working on a contracting model that is outcomes focused and allows customers and suppliers to overcome the barriers inherent in most contracts. The most common contracting models in use today (fixed scope or time-and-materials) actually increase risk in software development. She has worked with IT lawyer Susan Atkinson to develop an alternate
Aaron Bedra talks about web security and issues that affect e-commerce and online payments services.
Tim Lister talks about his keynote at the Agile 2013 conference, reflecting on his 40 years in the software industry, the new release of the book Peopleware, risk management in software projects and how teams form.
Bjarte Bogsnes talks about Beyond Budgeting and the challenges and approaches to implementing it in organizations as well as its history and acceptance in the Agile community.
Amr Elssamadisy, founder of Agile Culture New York and author of the book Agile Adoption Patterns, shares his thoughts on why safety is essential to Agile success. We know that learning is essential for successful agility, and teams learn best through failure – but failure is inherently unsafe. The key to success is in making things safe. Without safety you cannot learn effectively from failure.
Dan Mezick, author of the book The Culture Game, shares his insights on engagement as the fuel of successful and lasting Agile adoptions. Pulling examples from Open Spaces and the computer gaming industry, Dan explains how they both implement four basic rules: have a clear goal, a clear set of rules, a good feedback system, and support an opt-in participation strategy.
Darach Ennis explains the lessons learned from the Complex Event Processing community, reactive programming, the challenges of messaging on mobile platforms, OOP vs Functional and much more.
Gojko Adzic talks about the need to iterate and learn about business value before jumping into solutions. Impact Mapping helps visualize and learn which behavior changes impact business results. Those changes might not even require any kind of software delivery.
Alexander Osterwalder sits down to discuss the Business Model Canvas, how large organizations are using it today, and his thoughts on the Lean Canvas.
Kupe Kupersmith discusses his session on Improv at Agile 2012 and how it can help both teams and individuals communicate better.