When I lead public workshops, I ask people what their experience with with agile is. In the past, if I asked people if they were experienced with agile, their answers were reliable. Now, not so much. People think if they can spell agile, they are agile. If they sometimes use timeboxes, they are agile. If […]
I’ve been writing through my travels. Today, Stickyminds published Not Ready for Agile? Start Your Journey with Release Trains. In February, Gantthead.com published Timebox or Kanban: A False Dichotomy. I would have let you know, but I was traveling and was unaware they published it! I write the columns ahead of time and don’t know
Shane Hastie and I taught our Working with Geographically Agile Teams workshop last week in Sydney. One of the questions that arose is “What tool do I use with a distributed team?” That same question is on the scrumdevelopment mailing list this week. Shane and I don’t know what is wrong with a whiteboard and
I love it when my readers challenge and question me. Thank you, Sam and Paulo for asking the equivalent of “Huh?” for Refactoring and Redesign are Different. You asked great questions. Let me see if I can answer. For me, the time issue is the lack of transparency about the time required to complete the
I’ve been working with people starting their transition to agile. They are all smart people—some of them scary-smart. And some of them are misusing some of the terminology. Some people are using the word “refactoring” to describe significant work, say, weeks or even months of effort of rework. Sorry, I call that redesign. To me,
I just finished the SDC conference in Wellington and am now in Sydney, ready to start SDC here tomorrow morning. One of the highlights for me was the experiential workshop Shane Hastie and I led about kanban Tuesday afternoon. We started with a backlog and a minimal board: not started, in process with a WIP
I’m in Las Vegas waiting to get on a plan to Los Angeles to go to New Zealand for SDC. I led a workshop yesterday for real estate project managers about how to define success and manage some of the early-in-the-project risks. We discussed issues such as the Hudson Bay start, context-free questions, release criteria,
Shane Hastie and I have been working across timezones in preparation for a workshop: Working Effectively With Distributed Agile Teams. I’m keynoting at SDC in a couple of weeks, and am looking forward to being back in Wellington and Sydney. First, Shane and I built a backlog in Google docs, so we could both see
For years, I have ranted against traffic lights as a way to discuss project status. That’s because on serial lifecycle projects, or on long projects, the traffic light was always yellow or red. And, because managers, especially senior managers expected the light to turn green by itself with no outside intervention. But Lisa Crispin noted
I still have estimation on the mind. I saw The Impact of Accidental Complexity on Estimates and I was wondering about the effect of management on bad code. Do managers sometimes force developers to write bad code by allowing technical debt? Jay’s third point implicates technical debt as a cause: Introducing technical debt increases accidental