Skip to main content

Extreme Product Management (XPM)

In the latest issue of productmarketing.com, Barbara Nelson and Stacey Mentzel wrote about extreme product management (XPM). I'm glad to see respected product management folks write about this topic.

Nelson and Mentzel spell out many of the reasons that developers have opted for agile development methods. Some of these reasons are reactions to poor product management, such as unreadable requirements documents and constantly-changing requirements. And the authors explore various ways that a product manager can work constructively with teams that practice agile development.

Nonetheless, I have a couple of issues with the article.

First, the article defines XPM as:

XPM is using the minimum process and creating the minimum artifacts to deliver products people want to buy.
I find this definition unfortunate. The choice of words "extreme product management" renders it an obvious analog to extreme programming (XP). While part of XP is to generate minimal formal artifacts, it is much more. XP involves the application of many practices, including writing tests first, small iterations instead of a waterfall approach, frequent integration, and frequent releases. Any definition of XPM that fails to incorporate these concepts is misleading.

Second, the article seems to endorse an "agile waterfall" approach:

With a solid roadmap in place and stable market requirements, we should be able to review and complete market and functional requirements at the start of a project. Then, Development can iterate through implementation and testing while Product Management is preparing for the next release cycle. Since Development reaches a point where the entire release is designed, they can set a good target date and free Product Management to focus on promotions and the next big thing.
This approach fails to engage the product manager in one of the most important lessons of agile: requirements are almost never stable or completely understood. Product managers must iterate on the requirements in the same manner as developers iterate on the implementation. The end of each iteration yields the product manager something of tremendous value - a demonstratable version of the product that can reveal gaps in the requirements.

The product manager shouldn't just hand off the market requirements to the development team and re-engage after development has finished its iterations. Instead, after eliciting and documenting an initial set of requirements, the product manager should engage, at a minimum, after each iteration. She should revisit and update the requirements to reflect new discoveries. She should also recalibrate the requirements to reflect more educated estimates of how long it will take to implement them.

Read more about how and why we at Cauvin, Inc. practice agile (though not necessarily "extreme") product management here.

UPDATE: You may read a followup on this topic here.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem