When people first try scrum, or TDD (or any new process), they feel uncomfortable. We “know how to do” stuff, but then we’re asked to try on something new. Then our comfort zone alarm goes off. We feel constrained. Scrum puts limit on sprints, so we’ll need to actually help the testers finish testing our story.
Category Archives: Causing Change
When on the Scrum Master Podcast, I was asked a very important question: How do I get a systemic view of the organization. This is worth going deeply into. Let’s start with why this view is valuable. The more I work with teams, I find there’s a limit of change I can make. Or, rather, they can
At Agile Israel conference, I was recruited to a “Hit The Experts” panel on engineering practices. Ok, I didn’t put too much of a fight. Most of the questions were not of the engineering nature, though. One of the questions went like this: We’ve adapted the Spotify model, and now there’s no specialization, expectations from
So this came up a few days ago: “Why Scrum Should Basically Just Die In A Fire”. My first thought was: “Of course scrum is failing him, he’s not actually doing scrum.” Second thought was: “He doesn’t understand agile at all, does he?” Third thought was: “Gil, you’re an idiot.”. Because I have been saying
When software projects fail, we grow the divide between business and development. Let’s analyze a bit, shall we? Why is the divide growing? The divide is basically a metaphor for trust. Mostly, the two sides don’t trust, or sometimes understand, each other. Their goals don’t coincide, and are not communicated correctly. Add to that some
One of the questions I got in my Agile Practitioners talk startled me. Actually, it wasn’t the question that startled me, it was how I answered. I was talking about why you cannot say “our organization is going agile” while saying: “we’ll get our developers into that agile business in a year”. I know it
I’m a big fan of Manager Tools. I’ve been listening to the podcast and recommending it to anyone, manager or not, for the last five years. A recurring topic in the podcast is Manager Tools co-founder Mark Horstman’s laws: It’s all about people More communication is better. And there are more, and I invite you
We’re going agile! Note that it’s not with a capital A. And when we do it is with small steps. However, I think it is a step in the right direction. How did this miracle happen? I can take some of the credit, but it’s mostly letting people absorb the theory until it looks real.
Scott Hanselman is moving to Microsoft. I’ve been following Scott’s blog and podcast “Hanselminutes” over the last year. I wish him luck, and that we all benefit from his new position. Scott describes himself as a geek. When he saw a CD, he wanted to see how it works (a quote from the last podcast
My last post reminded me of another thing that came up during the last audit. The code review process was just beginning, but I already had forms as proof of the process taking place. The auditor looked at them and asked “why aren’t there names on the forms?”. I said proudly (as it was my