Gothenburg · Sweden
Business analyst and software architect at IBM, then program manager and application architect for a product family running on 7,500 installations across Scandinavia, and for the last ten years a Scrum Master.
Twenty years in the room with executives who want something vague and teams who have to build it. Most of that work sits in one gap: turning a business pressure into something a team can actually deliver against.
The book
From Why to Done
Scrum done right — delivered on time, every criterion met. And still nobody uses it, because nobody wrote down why. 244 pages on the chain from a business driver to a line of finished code, worked through one team's four Sprints.