You start with a point of view about what makes a minimum viable product. When your product launches, it is your customer’s point of view that matters. You must understand which problems your customers care about solving, and what solutions are available to your customers today. You need to understand […]
Marketing / Product Management / Product Strategy
Posted on:
Important Customers – Comparing Products Part 5
A good product is one that solves valuable market problems. To be successful in the market, a product needs to solve the problems that the right customers are willing to pay to solve. To know if those customers are willing to pay, you need to understand how they perceive your […]
Prioritization / Product Management / Requirements / Requirements gathering
Posted on:
Important Problems – Comparing Products Part 4
If you understand the important market problems, you can make a good product. If you understand how important each problem is, for each group of customers, you can make a great product. If you’re new to this series, go back and start at the first article, we’ll wait for you […]
Product Management / Requirements / Requirements gathering
Posted on:
Market Problems – Comparing Products Part 3
Comparing products without an understanding of the important market problems by which to compare the products is a waste of time. This is the third in a series on comparing products – jump back to the introduction if you haven’t already read the previous articles. Go ahead, we’ll wait, then […]
Business Analysis / Interaction design / Product Management / UX
Posted on:
Cadence Versus Risk
I’ve been thinking about the software development process. Big, upfront, design and requirements. User research and analysis. Market insights, gained on exploration or over time. Release cadence – how quickly you get, and incorporate, feedback from your customers about your product. How quickly you react to your competitors’ reactions to […]
Agile / Business Analysis / Interaction design / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / Usability / Use Cases / UX
Posted on:
Use Cases for Iterative Development
Almost everything I’ve read about use cases focuses on describing what needs to be added to your product. Agile development says “get it working first, make it better second.” That means changing the way the software enables a user to do something they can already do. How do you manage […]
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-04-21]
A look back at the best from a year ago.
Agile / Software development
Posted on:
Agile Development Methodology Comparison
Agile project management has entered the mainstream – incremental delivery is now common and (should be) expected for any new software development project. Which agile development methodology should you use on your project? There are at more than ten to choose from. What makes them different? The risks that they try to address.
Agile / Process Improvement / Software development
Posted on:
Code Debt: Neither A Borrower…
Code Debt is the debt we incur when we write sloppy code. We might do this to rush something out the door, with the plan to refactor later. Agile methodologies focus on delivering functionality quickly. They also invoke a mantra of refactoring – “make it better next release.” This can create pressure to “get it done” that overwhelms the objective of “get it done right.” Taking on code debt like this is about as smart as using one credit card to pay off another one.