Paul Dolman-Darrall discusses incremental improvement: small changes headed towards the huge ambition of turning a whole company radical.
Barry O'Reilly discusses how to embrace a culture of continuous experimentation and learning, to adapt the organization’s design, and transform the business to an adaptable, resilient Lean Enterprise.
Linda Rising discusses the “agile mindset” - an attitude that equates failure and problems with opportunities for learning –, sharing practical suggestions to become even more agile.
Máté Nádasdi presents how Ustream uses unit testing and continuous integration for the front-end to ensure the website’s stability and growth.
Gojko Adzic shows how to convince people to embrace flexible scope, not only for startup environments but for big enterprise projects as well.
Katherine Kirk reflects through case study examples on what continuous improvement feels like on the ground and explores how it can be better by learning from other industries, research and real-life.
Ola Ellnestam shares lessons learned and DevOps practices along with the underlying values and principles used to implement continuous improvement and delivery at a large bank.
Chris Smith provides practical advice for sprint retrospectives, gathering information and identifying root causes of both problems and successes, and addressing issues from a different perspective.
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.
Dana Caulder discusses how to improve team communication and delivery, aligning processes and tooling for iterative improvement, processes to mitigate team member turnover and speed-up onboarding.
Astrid Claessen discusses retrospectives: the Derby and Larsen models, how gamestorming helps, and techniques explained through example by involving the audience.
Bill Yetman and Jeremy Pollack discuss using Agile techniques -start simple, get going, iterate- and the “measure everything” principle to create the architecture behind the Family History website.