Henrik Kniberg, Crisp AB

Henrik Kniberg is a consultant and partner at Crisp in Stockholm www.crisp.se, specializing in Java and Agile software development. He enjoys helping companies succeed with both the technical and human sides of software development.

Henrik's interests and 12 years of experience cover most aspects of the art of software development including leadership, development, design, teaching, and testing. He is Certified ScrumMaster, member of the Agile Alliance, and teaches courses and seminars on TDD (test-driven development), Scrum, and various Java technology areas.

Ever since the first XP books and the agile manifesto appeared Henrik has embraced agile principals and learned how to apply them efficiently in different types of organizations. As co-founder and CTO of Goyada 1998-2003 he had ample opportunity to experiment with TDD (test-driven development) and other agile practices as a he built and managed a technical platform and a 30-person development team.

Henrik is author of Scrum and XP from the Trenches Scrum and XP from the Trenches, a popular book describing in detail how he helped a Swedish online gaming company out of a crisis by implementing agile and lean principles at all levels.

Tutorial: "Scrum and XP From the Trenches"

Track: Tutorial

Time: Friday 13:00 - 16:00

Location: SAS Suecia

Abstract:

How does Scrum and XP really work, on a day-to-day basis? What are the common pitfalls? How do you choose a sprint length? Where does acceptance testing fit in? How do you deal with multiple teams? How do you create and maintain a product backlog? How do Scrum and XP actually fit together? What is the best format for a sprint backlog?

There are no definite answers to these questions, as each organization is unique. This tutorial, based on the popular book with the same name, will help you along the way by providing detailed, concrete examples of day-to-day work with Scrum and XP.

I will go through some of the core practices and discuss lessons learned after 1.5 years of experimentation in a 40-person development team. For each practice I will tell you exactly how we worked, why, what other approaches we tried, and invite discussion to hear about your experiences. This is about hard-earned experience rather than theory.