In a recent estimation workshop, one of the participants asked, “How do we estimate something we’ve never done before?” “Is it a feature or a project?” I asked. “A feature,” she said. “How do you do things now?” Based on her previous comments in the workshop, I suspected she was pretty good at what she […]
If you’ve been paying attention to agile at all, you’ve heard these terms: pairing and swarming. But what do they mean? What’s the difference? When you pair, two people work together to finish a piece of work. Traditionally, two developers paired. The “driver” wrote the piece of work. The other person, the “navigator,” observed the
We understand how to swarm around a feature as a collocated team. But how do you do that when you are part of a geographically distributed agile team? It depends on how you are distributed and across how many time zones. How are you distributed? Too many geographically distributed teams are separated by function. That
I’ve been working with Gil Broza on our teleclass series, Prevent Your Agile Titanic, both on marketing it and on its content. And it never fails, we have questions for each other almost every day. Sometimes I’m developing something and it looks “funny.” So I ask for review. Sometimes, as with the content, we discuss
I maintain the AYE web site as part of my responsibilities this year for the conference. I post the news, the new articles, and do the general updating. Monday, I posted one of Don Gray‘s articles, Shifting the Burden – Whose Monkey Is It? Except, Don and I had both made a mistake. Don
I was sitting on the couch was organizing a database last weekend, with daughter #2 sitting next to me. I was creating a script to go through each record removing a field’s contents and adding new contents to another field. Not a difficult thing to do. I created a loop, and daughter #2 said,
I’m teaching project management (and some hiring) workshops in Israel. I’ve caught up with timezones, so I may even be able to post this week. I attempted to explain why pair programming works to some skeptical project managers last week. I explained that in the best environments, a person can work 6 hours a
I’m working with Esther this week on the book. We’re editing (and continuing to pair-write and pair-edit). Today, one of the things we addressed were the comments dealing with the people we name in the book. We hadn’t done a good job drawing our readers in to care about the people. So we’re fixing
A reader sent me email with this question: “We have a group of four people (3 developers and a tester). We work on 4 products, releasing one about once a month (each product is released once a quarter). The developers are devoted to one product when they’re developing, but have to fix problems immediately if
Esther and I have been editing the management book this week. We’re pairing to edit also – one keyboard, one file, two heads. It’s exhausting and fun. Here are things I’ve learned this week: We don’t have the same default ways to write — and that’s ok. The manuscript is richer for us talking