Archive for category extreme programming

Dipping Your Toes Into Kanban

dipping your toes into kanbanThe following post was originally a guest article for Planbox and is the basis for my proposed Agile2011 Lightning Talk

Like me, you may have read about the growing popularity of kanban in the agile software development community. Perhaps its mysterious allure and intriguing pronunciation (kahn-bahn not kayun-bayun) have piqued your curiosity, yet you struggle with finding a pragmatic way to apply it to your current software development process?

Interestingly enough, the beauty of kanban is that you can apply it to your two week iterations… right now if you like without that much disruption. In fact, you may even find it so useful that you’ll find other ways to work the kanban mojo.

Let me explain… [Read More]

, , , ,

1 Comment

I hate pair programming (and your code and you)

“Are you pair programming?” our manager asked in his snarky tone, while using exaggerated double air quotes to emphasize his skepticism. He then walked away without waiting for a response…

This is merely one example of numerous instances I’ve experienced over the years from skeptics of pair programming… [Read More]

, , ,

30 Comments

SaMoLo in Retrospectives

SaMoLo, or the Same as, More of, Less of technique, is a fine tuning facilitation exercise with roots in early XP.

‘Same As’ are those traits that you value and don’t want to lose. Many traditional feedback methods end up glossing over these items and as a result the behaviors that should be reinforced, aren’t.

‘More Of’ are those traits that you want to encourage. It may be a newly acquired skill or the beginning of a behavior. Or it may be an area where something is lacking and you want to help ther person find a way of bridging the gap.

‘Less Of’ are those traits that have simply gone too far. They may be great traits, but eventually someone will ‘out Herods, Herod’ and things need to return to normal. – fairlygoodpractices.com

Thanks in part to Jeff Nielsen, I’ve discovered that SaMoLo can also be the sweet spot for easing new teams into iteration retrospectives.

  1. It is easy to remember
  2. More engaging than What worked? What didn’t?
  3. Takes 30 to 40 minutes
  4. Pairs well with other exercises

In a recent iteration retrospective I paired the SaMoLo technique with… [Read More]

, , ,

11 Comments