Author name: Johanna

I help you identify and solve the problems that prevent you from releasing systems, hiring the right people, deciding which project to work on next. I take a pragmatic approach: what will work best for you, now? Some people call me a focuser. Some call me an accelerator. When I work with people, first we define our goal together. Typically, it's to get a better product out the door faster. I work with my clients to help managers figure out how to do the managing better, and how the technical contributors can contribute better, not to create a by-the-book system. I work with you, your staff, and your current product development practices. Together, we learn what works well for you and what doesn't. I believe in changing only what needs to be changed at the current time, to maximize your success. We work together to develop a blueprint for the future, and to build in capacity to recognize and implement change.

MPD, portfolio management

Rethinking Component Teams for Flow

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 […]

management, MPD

Connecting with Humans

I just read Zappos is struggling with Holacracy because humans aren’t designed to operate like software. I’m not surprised. That’s because we are humans who work with other human people. I want to talk with people when I want to talk with them, not when some protocol tells me I must. It’s the same problem when

Articles

Continuous Agile Program Planning: Think Big, Plan Small

It seems as if the larger the agile program, the bigger the planning. Many organizations try to plan for an entire quarter at a time. They bring everyone on the program together in a large room (often a hotel ballroom) and attempt to plan the next quarter’s work. That kind of planning works for some

MPD, product ownership

Continuous Planning Article Posted

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

MPD, podcast

Lessons for the New Year

I don’t know if you retrospect on a regular basis. I do. (I know, you are so surprised!) Andy Kaufman asked me to share my biggest learning for his podcast. Take a listen to The Most Important Lesson You Learned Last Year. I’m pleased and proud to be in such good company. Thanks, Andy!

newsletter

New Year’s Tips for 2017

New Year’s Tips for 2017 Other people like to help you plan for resolutions. Well, I’m a bit contrary. I don’t buy this resolution business. I never succeed. (I’m not alone in that.) On the other hand, I like to integrate tips for my next year from my learnings from the previous year. I’ve been

agile, MPD

Consider Rolling Wave Roadmap and Backlog Planning

Many agile teams attempt to plan for an entire quarter at a time. Sometimes, that works quite well. You have deliverables, and everyone understands the order in which you need to deliver them. You use agile because you can receive feedback about the work as you proceed. You might make small adjustments, and you manage

MPD, product ownership

Consider Onions or Round Trip for an MVP

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

agile, MPD

Cost Accounting is a Problem for Agile (and Knowledge Work)

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

Scroll to Top