When I saw the McKinsey report on “developer productivity,” I shuddered. First, that makes no sense in a collaborative team. Second, there’s no way to measure such a thing as developer productivity, despite what McKinsey says. (I’m not linking to the report, because the advice is so bad.) Then I read Lorin Hochstein’s brilliant assessment […]
Product owners have many challenges: They need to keep at least two thoughts about the product: what it needs to be in the near future, and what the organization wants it to be in the (distant) future. Some product owners think they’re supposed to fill out a complete backlog, including all the UI designs for
Much of my LinkedIn and Twitter feeds have questionnaires with two or three choices. One of those choices contains the One Right Answer. All the other answers are Wrong. Or, a person poses a question that’s supposed to show that they—and they alone—know the answer to the question. (I ranted about one of those on
I started this series with the issues of trying to estimate/predict a specific backlog item quarters away, not even weeks away. (Even weeks away is iffy because the entropy is the default state for the world.) In Part 1, I suggested that the team can use cycle time, but even with cycle time, we need
In How to Predict When the Team Will Complete a Specific Backlog Item, Part 1, I said there was no way to accurately predict an estimate for a specific backlog item more than a month away. I did suggest several options if you want to go through the motions, but there’s no accurate answer to
Warning: Rant ahead. Today, I received several chirpy, happy, perky emails from either connections or LinkedIn’s email. They all said essentially the same thing: “Hello, friend. What’s making you happy or successful today?” I hate these emails. Just hate them. They feel fake to me and worse, they bring out the grumpy in me. And
Everyone’s got an email list these days. And thankfully, most people use email vendors of some sort. That’s because an email list is the most valuable marketing tool a business can have. Why? Because the email subscribers chose to be on that list. That’s permission-based marketing. Yet, some email tool vendors think you should “clean”
Tim, a C-Level leader, loves his skip-level meetings. He feels the meetings offer him a chance to connect with people he doesn’t normally see. They get to talk about whatever the other person wants. Sharon, a different C-Level leader, never conducts skip-level meetings. She feels that those meetings might cause her managers to feel unsafe,
About 20 years ago, I taught a project management workshop to IT people. Their products and services did not ship outside the building—their products and services enabled the organization to make money. During that workshop, the participants all had the same question, “How do we engage our stakeholders?” For years, I explained that the more
The news is full of this “quiet quitting” idea. Supposedly, employees are doing just what the work demands and no more. That sounds reasonable to me. (See the blog post, It’s Time to Clarify Work Boundaries and “Quiet Quitting.”) I don’t see why people should do “more” than a day’s worth of work in a day.