Joanie, a new VP Engineering, joined the company a couple of weeks ago. Her boss, the CEO, wants to know how long it will take engineering to finish all the projects. Joanie asked the various leaders these questions for every project in progress: When did you start this project? Are you still working on this […]
Acme, a software company, has a technical excellence problem. Its customers report more problems than the product teams do. Two managers, Cindy and David, want to bring specialized training in for product teams. (They want to help their teams learn to use Test-Driven Development, TDD, and Acceptance Test-Driven Development, ATDD. Cindy and David suspect that
The larger your product, the more likely you have components teams. I often see component teams because of the architecture of the product. In this first image, the Integrated System Program, the rest of the product uses the Platform of Common Services as components. Also, the teams find it tempting to think of the common
Did you ever work on a project that dragged on and on, slipping a week every week? Back in the day, we called those projects “death marches.” I never saw anyone literally die, but I saw too many divorces, abuse of drugs and alcohol, and very dissatisfied and unhappy employees and customers. Waterfall projects can
Some managers wanted to prevent Bad Things from happening in the organization, so they added policies or procedures. Now, these same managers want business agility. However, the policies and procedures increase friction and make it harder to get the Right Things done. It’s time to start removing some of those policies and procedures. The more
Many managers and teams talk about “average” durations for work. On average, how long does it take a team to finish a certain kind of work? However, average doesn’t quite explain why our work takes different durations. Instead of average, consider the word, “typical.” I’ve written about cycle time before. (It’s the time from when
Vasco and I had a wonderful discussion about the Modern Management Made Easy books on his Scrum Master podcast. Listen to BONUS: Modern Management trilogy by Johanna Rothman. We discussed why Scrum Masters and coaches might want to read these books. And how to use the information in the books. (Hint: to support and serve
Michael Mahlberg taught me something cool last week. We’re writing an article together. Part of the article is about forecasts. I was ranting and raving about how to help people see their confidence levels. He pointed me to this slideshare: Lightweight Kanban Metrics (in German). (Don’t worry about the language.) Go to slides 24, 25,
Several of my clients have intertwined problems. Everyone agrees they want innovation: Which products and services the organization offers. (The project portfolio) What features the product offers, or the problems the product solves. (The product roadmap) In the team, to solve the problems in a way that will attract users/buyers/customers. (The team’s backlog and how
Do you have any idea how long it takes you to make decisions? Or, to clear impediments? Or to report to your team or your boss about your action items? Each of those items is a deliverable. That means we might be able to measure the cycle time for each of these deliverables. Normally, we