Here are the slides from my session "10 ways to screw up with Scrum and XP", from the JFokus conference in Stockholm.

Many companies with existing legacy code bases bump into a huge impediment when they want to get agile: lack of test automation.

This article illustrates how to address this problem by creating a test automation backlog and implementing a few tests each sprint.

Test case	Risk	Manual test cost (man-hours)	Automation cost (story points)
Block account	high	5 hrs	0.5 sp
Validate transfer	high	3 hrs	5 sp
See transaction history	medium	3 hrs	1 sp
Sort query results	medium	2 hrs	8 sp
Deposit cash	high	1.5 hr	1 sp
Security alert	high	1 hr	13 sp
Add new user	low	0.5 hr	3 sp
Change skin	low	0.5 hr	20 sp

Read more...

As I mentioned in Failing with Scrum, Scrum is no silver bullet. It doesn't guarantee success, but it improves the odds.

Over the past few years I've been involved in dozens of Scrum projects, directly or indirectly. Interestingly enough, every single case that I can remember has been successful (maybe I just have selective memory...)! The client has been happy with the process and wants to continue using Scrum in future projects.

Here are some thoughts and conclusions about that.

Read more...

There are plenty of Scrum success stories out there, but not so many failure stories. That gives rise to a healthy scepticism. Where are the failure stories? Obviously there must be failures! Or?

Here's a "failure" story and some thoughts on what it means to fail with Scrum.

Read more...