<<< Previous speaker next speaker >>>

Consltant and Partner Henrik Kniberg, Crisp AB

Consltant and Partner Henrik  Kniberg Henrik Kniberg is an agile coach at Crisp in Stockholm. He enjoys helping companies succeed with both the technical and human sides of software development.

During the past decade Henrik has been CTO of 3 Swedish IT companies and helped many more get started with Agile and Lean software development. As Certified Scrum Trainer Henrik does regular coaching and training together with Jeff Sutherland.

Henrik's book Scrum and XP from the Trenches has over 100,000 readers and is one of the most popular books on the topic. During the past year Henrik has won "best speaker" awards on two international conferences.

Presentation: "What's Hard About Becoming an Agile Software Developer?"

Time: Wednesday 11:30 - 12:20

Location: Lille Sal

Abstract: "Simple" is a word often used in agile software development. Terms like YAGNI and "do the simplest thing that can possibly work". It is easy to forget, however, that Simple is often Hard! So what's hard about becoming an agile software developer, where are the bumps in the ride? In this talk I'm going to go through some aspects of agile software development that many developers find to be hard, or even unpleasant initially.

Workshop: "Scrum and XP From the Trenches"

Track: Tutorial

Time: Thursday 09:00 - 12:00

Location: Musikhuset Nr. 421 + 423

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.