Almost every manager I know wants to know when a project will be done. Some managers decree when a project will be done. Some managers think they can decree both the date and the feature set. There is one other tiny small subset, those managers who ask, “When can you finish this set of ranked […]
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
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
“I want to move to agile. Or lean. I don’t know which. I just know I have to show progress more often. I want to be able to adapt to changing conditions. That means I have to choose between timeboxes or Kanban, right?”– a confused project manager, on the verge of adopting a more agile
The good news is that agile has name recognition. The bad news is that a number of organizations are trying to start agile in a big-bang way, especially on programs. Program management is hard enough without throwing a new approach to projects into the mix. Since so many of you are emailing me about this,
I’ve been working on agile program management and a colleague emailed me about his program. He’s having trouble seeing how to do agile on a large program. The customer wants to see a working system before they add the features, so the customer thinks the program need to provide “all” the architecture, with some hard-coded
One of the problems many people encounter when moving to agile is that they (literally) cannot imagine iterations shorter than 4 weeks. I rarely recommend an iteration as long as 4 weeks now, and if people insist on 3 weeks, suggest they find the root cause for the reason their iteration needs to be so