As with many of you, sometimes my WIP (Work in Progress) is too high. When that occurs, I don’t use a backlog or create iterations. Instead, I use continuous flow. That’s because working in flow allows and creates ease in my development. This week, I want to finish these things: 5 presentations, one of which […]
A project portfolio manager contacted me via LinkedIn. The question: How can this portfolio team start to manage the project portfolio when the organization has 600 projects? Right now, the portfolio team is supposed to read the status decks for each of those 600, to understand each project’s status. How to start? That’s an impossible
My clients all have too much work to do. So they ask the product or project leaders to write a business case for each effort. The clients claim this information helps them decide which work to do and not do. However, everyone knows each business case is at least partially fiction. That’s because the writer
Fred, a client, asked how I could help him get more work out of his resources. I asked if he meant people. He said yes. So I asked if he focused more on what each person did or if he focused on the team’s work. “Each person.” I smiled and said, “I have a deal
A senior manager said, “We give our resources everything they could need: technology, tools, even some training. Why are they so slow?” I asked, “How many projects are they working on?” “Each resource has at least two projects so they stay productive and efficient.” These managers have created a resource efficiency culture, not a flow
We often think that finishing a story from the backlog is “just” tactical. However, the more often we deliver in short feedback loops, the more often we can make strategic decisions. Finishing a story creates a new decision point, for both the product and the corporate strategy. The more often we iterate strategically, the more
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
Up until a few months ago, my office was a disaster. I had a ton of old data: Paper in reverse chronological order on surfaces (most recent on top). Printed articles to read. Notes from previous workshops I wanted to integrate when I updated those workshops. Over the past year, as I realized the pandemic
Here’s a scenario I see in all kinds of businesses. Your team has product-focused work. And, the team also has “fast” response-required, ad hoc work: Production support, when something breaks. You need to fix this right away. Provide technical support when people have questions. The team needs to answer these questions on a “timely” basis.
Daniel Vacanti and Prateek Singh graciously invited* me to be on an episode of Drunk Agile: Episode 37 Johanna Rothman Part Deux More Bigger Aging. (*Invited is their term. I sent them an email, politely demanding they discuss aging. Is it possible to politely demand? I tried. Only they can tell you if I was