Steve Adolph discusses his PhD research on communications in organisations, the importance of boundary spanners and how a large backlog becomes an impediment to product development flow. He talks about he importance of the ScrumMaster role, problems with Product Owners and where Business Analysis can add value.
Lachlan Heasman and Bernd Schiffer talk about Agile Coaching and how to define it and the skills required as well as their experiences along the way including Scrum PLoP, 42 things and Agile meetups.
Sandy Mamoli talks about being an Agile consultant, Agile adoption in New Zealand, the flavours of Agile Coaching as well as experiences in succeeding with Personal Kanban and her tool KanbanFor1.
Tim Berglund explains GitHub's approach to product owners and product development and how that can (or can not) translate to other companies.
Neil Killick discusses his background in Agile and his thoughts on estimation in Agile software projects, in particular the discussion around #noestimates.
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.
Deb Colden and Tami Carter discuss how they got involved with Innovation Games, how and why they've used them, and how they've dealt with remote participants in their game sessions.
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.
Mike Griffiths shares his journey on the creation of DSDM through to his more recent work with the PMI around the Agile Community of Practice and the PMBOK v5 Guide and Software Extension.
Peter Saddington discusses his work as an Agile Coach, his Agile Scout blog, his new book and his passion into research and tools around leveraging human capital and optimizing teams.