Approaches to Iterating

Recall that we at Cauvin, Inc. specialize in agile product management. Most agile methods incorporate iterations. With iterations, you develop and "release" the product many times before the final release to customers. In each time-boxed iteration, you refine the requirements, design, implementation, and tests for that "release" of the product. (I'll explore in a future entry how some agile methodologies plan the tests for the product before they design and implement.)

Yet sometimes it's not immediately obvious how to divide a product development effort into iterations. Here are some approaches that we use with our clients:

Verbal Description - Flesh out use cases and verbally walk through the customer experience with prospective customers.
Mock-Up - Compose a Powerpoint presentation or other user interface and use it to demonstrate the user experience to prospective customers.
Simulation - Create a simulated environment for testing your product and demonstrate your product working in that environment.
Use Cases per Iteration - Implement just a subset of the product's use cases and demonstrate them to prospective customers.
Use Case Versions per Iteration - Implement simplified versions of the use cases your product will ultimately satisfy. Demonstrate these working versions to prospective customers.

No matter which approaches you use to divide your product development effort into iterations, try to confront uncertainties and risks (in requirements and design) in early iterations.

Comments

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .

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 ...

Cauvin

Search This Blog