Most people I know—even the people supposedly using agile approaches—have too much work to do. You have project work. In addition, you have support work, formal for customer support or sales, and informal for your colleagues. Let’s not forget the reports to write or file, time cards to fill out, or other periodic events. You […]
I’m almost at the end of the January Practical Product Owner workshop. One of the participants has a problem I’ve seen before. They have a backlog of work, and it’s all tasks. Not a story in sight. I understand how that happens. Here are some ways I’ve seen the tasks-not-stories problem occur: The technical people
In Manage Your Project Portfolio, I’m agnostic about who manages the project portfolio. I prefer that the managers responsible for the strategy make the project portfolio decisions. And, I recognize that the PMO often makes those decisions. I am doing a series of webinars with TransparentChoice. The first one is live. See How many “points” does
A couple of weeks ago, I spoke locally about Manage Your Project Portfolio. Part of the talk is about understanding when you need project portfolio management and flowing work through teams. One of the (very sharp) fellows in the audience asked this question: As you grow, don’t you need component teams? I thought that was
I have a new article up on projectmanagement.com, Continuous Agile Program Planning: Think Big, Plan Small. It’s about how to use rolling wave planning especially for an agile program. If you are a Product Owner or you are responsible for planning what when, and want to learn how to do this, join my PPO Workshop, starting
I’m teaching a Product Owner workshop this week, and I had an insight about a Minimum Viable Product. AN MVP has to fulfill these criteria: Minimum means it’s the smallest chunk of value that allows us to build, measure, and learn. (Yes, Eric Ries’ loop) Viable means the actors/users can use it. Product means you
The more I work with project portfolio teams and program managers, the more I understand one thing: Cost accounting makes little sense in the small for agile, maybe for all knowledge work. I should say that I often see cost accounting in the form of activity-based accounting. Each function contributes to some of the cost
I’m doing a Twitter chat November 3 at 4pm Eastern/8pm UK with David Daly. David posted the video of our conversation as prep for the Twitter chat. Today he tweeted this: “How do you optimize for features? That’s flow efficiency.” Yes, I said that. There were several Twitter rants about the use of the word
If you’ve been watching my writing (and speaking), you’ve noticed that I like both agile and lean. I like the cadence of milestones and demos that iteration-based agile provides. I like the limiting of work in progress and seeing the whole that lean provides. For me, both are necessary to deliver value. You might have
As I’m teaching my Practical Product Owner workshop, some POs are having trouble understanding how big a defect is. Sure, they want to have small(er) stories, but a defect isn’t done until it’s all fixed, and the team has decided if they need automated regression tests added to the smoke tests. So, here are three