"Delivering Product"

In a previous entry, I mentioned that, when you use an agile product development process, you deliver "a working version of the product for review" at the end of each iteration. I mentioned in a later entry that Alistair Cockburn criticizes organizations that claim to use agile methods but don't deliver product at the end of their so-called iterations.

What does it mean to deliver a working version of your product to customers? What is the point of iterating if you "deliver product" after the first iteration?

The crux of the matter is that you should be able to demonstrate at the end of an iteration how a customer would use your product to address customer problems. So "working version" doesn't mean one that is ready for sale to the customer, but just one that is ready for demonstration. For a software product, that demonstration might include showing some hard-coded mock-ups in place of screens developers haven't yet implemented.

Comments

Scott Sehlhorst said…

The key here is that you deliver something which enables learning. That could be product to customers, betas or prototypes to select customers, or something to stakeholders.

Regardless, the litmus test is - did you learn something which caused you to change what you're doing (or how you're doing it)?

Thu Nov 20, 09:52:00 AM 2014

Roger L. Cauvin said…

Exactly. Learning and nimble adjustments based on what's learned.

As I mentioned in the previous blog entry, Agile Product Management developers can learn from discoveries during design and implementation. Perhaps more importantly, product managers can discover requirements they hadn't previously considered (particularly requirements corresponding to problems to avoid, not just problems to solve).

This learning can take place regardless of whether we deliver the product to internal or external stakeholders. The feedback or behavior of external stakeholders that are actual target users can in many cases be more reliable. But it's not always necessary.

With lean startup methods, we cast a wider net: a learning loop that encompasses the entire product strategy (including marketing and sales).

Thu Nov 20, 11:17:00 AM 2014

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

Cauvin

Search This Blog