At a conference not long ago, I overheard an attendee at a vendor booth ask if there was a way to exclude weekends from Lead Time reports. I politely asked them, “Why do you want to exclude weekends?” He said, “My team doesn’t work over the weekend, I don’t want that time counted against us.” I asked, “How is it that Lead Time metrics count against you?” He said, “It’s in my goals – it impacts my performance review.” This…
The DevOps Enterprise Summit once again exceeded my expectations. Swarming with witty smart people (who were also fun to hang with), an impressive hallway track emerged. Much learning transpired – below are my highlights in the order they occurred. A dedicated Dojo space for Learning Heather Mickman and Ross Clanton’s talk described Target’s large dedicated physical space for learning. Three kinds of learning opportunities occur in Target’s Dojo: Challenges: 30 day experiences to introduce and level up expertise on DevOps,…
We just hired a new person onto our Learning & Development team. The shift from three to four people caused me to have a serious think about improving our methods for prioritization. The expectation of increased workload may have prompted new thoughts. Maybe it was the beginning of a new year with new goals. Other factors may also have entered in—for instance, the broader subject matter requests our team received. And as additional requests flooded in, I realized that we…
It’s October. Monsters are appearing. Living dead zombies are lurking around looking for handouts. Similar to some projects at work, zombie projects are like the living dead. These are the low-value projects that are barely alive. They are starving for money, for resources and for people. They get no love. Projects starving for attention subtly schlep people’s time and energy away from higher value projects. If this is the case, kill them. Kill them so the more important work will be delivered…
The problem for a spouse who can build or fix just about anything is that the other spouse provides them with a long list of things to do. And for a number of reasons, it’s hard for them to say no. Reason #1 is that they like the person who asked. We do things for people we like. The same is true at the office. But getting things done doesn’t always start with yes. In this talk, I describe four…
I have facilitated a lean coffee http://leancoffee.org/ during day two of my Kanban for Ops workshops for over a year now. It’s been interesting to hear common themes surface across multiple countries from various industries. Typical topics include: How to deal with frequent organizational changes, kanban vs. scrumban vs. scrum, every team uses a different tool, distributed teams. At last weeks Atlanta workshop, we had the following: “Why bother at all with an electronic kanban board?” The consensus amongst many…
Thanks for watching. For information on future speaking events, checkout the speaking page.
Each September, I spend time investing in my own education. This year, Steve Holt suggested I register for the Cynefin practitioner foundation class from Cognitive Edge. The class sparked many aha moments for me, among which, the notion that short stories from multiple sources are much more relevant and powerful than studies reported by experts in their field. However, the biggest eye opener for me was when instructor Michael Chevedave said, “Don’t break down silos.” What?!?! Here I had been talking and writing about breaking down…
Last week’s Kanban for Devops training class in Portland produced some notably creative ideas towards visualization. Grawlixes, Slurm and the Dead Zone are three ideas worth spreading. Capturing interrupts using grawlixes (series of typographical symbols representing profanity in comic strips) shows work impacts in an amusing manner. Here’s how it works. Each time work is interrupted, add one grawlix to the ticket on the board. The longer the grawlix series on the ticket, the longer the lead time and (presumably)…
I did software configuration management for most of my career. I did builds and deployments and managed source code trees. I built out and maintained development, test and staging environments. My friends and family never really understood what I did for a living. But they knew from experience that if a release was happening that weekend, they might not see me until Monday morning. If The Phoenix Project had been around then, I could have just given them the book. It’s a novel…