Scrum and XP – Beyond the trenches

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Here are the slides from my presentation "Scrum and XP – Beyond the trenches" at JFokus. Thanks for coming!

To those of you that weren’t at the presentation, the purpose of the presentation was:

  • Many of the solutions in ”Scrum and XP from the Trenches” turned out to be pretty much universally applicable
  • However, I’ve learned a lot since 2006 and there some things that I would have done differently if I could go back in time.
  • Purpose of this presentation is to share these insights with you.

I came up with 15 concrete recommendations that I believed would be very widely applicable. Based on the polls that we did during this presentation, the hypothesis seemed correct! Every single recommendation got 90-100% Green votes from the audience. Or maybe you were just trying to be nice… Well, anyway, thanks for your feedback!

Sample slides:

12 Comments

  • 1
    2011-02-17 - 09:55 | Permalink

    Some really great stuff Henrik.
    Captures many of the discussions we have had the last retrospectives.

    Keep up the good work.

  • 2
    David Samuelsson
    2011-02-17 - 01:00 | Permalink

    During the presentation i noticed i answered green on all except one. All suggestions sounded good, so it was hard to find one that didn’t sound good. As a happy moment i realized i was practicing some of the tips without anyone ever giving me advise to do so.

    It would be interesting to see though an prioritized list of the suggestions if you could only pick 5, which ones would you go for directly in case you was not practicing them yet?

    “limit all queues” right?

    Thanks for a good talk, keep at it!

  • 3
    2011-02-17 - 02:08 | Permalink

    I loved your presentation – I can’t wait to experiment with these recommendations. I found myself agreeing that most, if not all, make sense. Having so many of the recommendations being specific and actionable makes this very useful. Keep up the great work!

  • 4
    Anonymous
    2011-02-18 - 05:12 | Permalink

    I went through this but was not very clear which were those 15 recommendations.
    I went through all the slides.

    We currently use focus factor, but it is actually not helping much! Can i write in detail to you about it?

  • 5
    2011-02-23 - 08:56 | Permalink

    Wow this is great stuff. Can’t wait to see it in action in Agile Israel 2011

    Especially liked Kings and Servants which was new to me.

  • 6
    2011-02-24 - 10:49 | Permalink

    I’ll probably do some updates by the time I get to Israel.

  • 7
    2011-02-28 - 10:02 | Permalink

    Very valuable material. Some of your recommendations came to us naturally and for the rest I am looking forward to proposing them during next retrospective. Thanks for sharing all this.
    Loïc

  • 8
    Americo
    2011-04-19 - 01:47 | Permalink

    Hi Henrik, on your book you mentioned problems and how to avoid them. When I read it a doubt came out. Do you store the problems that you had in your sprints in a database? If yes, how do you have organized it? I´m working in a thesis about it. The subject is data minig over scrum artifacts, especially technical problems. I´ve searched a lot but unfortunatelly none of the groups I have interviewed and / or visited have it stored in some way. Most of them just wrote in a post-it and afterwards just threw away. Can you help me on it?

  • 9
    2011-04-19 - 05:12 | Permalink

    In Scrum we focus on solving problems rather than organizing them. Usually the only organization needed is to identify the top two or three impediments to be solved next.

  • 10
    Americo
    2011-07-07 - 01:12 | Permalink

    Ok, but my question goes a little bit deeper. I´m thinking about SCRUM on new projects and I´m convinced that it is the best framework to use. After deployment how we can do maintenance if we don´t have much documentation? In my company we don’t have maintenance teams and all the projects are done with third-party teams and we don’t have the certainity that the same team that did the development will be available to perform the maintenance. I’ve been researching about it but up to now I couldn’t find a way. How I can avoid this kind of problems thinking in scrum as a basis for all software development?

  • 11
    Clément VIAUD
    2011-06-23 - 10:04 | Permalink

    Hello, in “Scrum and XP – Beyond the trenches”, you mentionned that you developed a script to generate printable index cards directly from the product backlog. Could you please help me to find it in your blog?

    Regards

  • 12
    2011-06-23 - 02:16 | Permalink

    Yes, here it is: http://blog.crisp.se/henrikkniberg/2007/12/18/1197973740000.html

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.