Amazon.com started by selling books. Their initial use case was “Sell books online.” The vision was always “Sell everything” – hence the name. But they started with a simple use case and evolved it.
Product Management
Posted on:
Product Management Glass Ceiling Cracked
Pragmatic Marketing released their 2006 product manager survey results. At first glance, there appears to be a huge disparity in compensation between male and female product managers. When we look in more detail, the evidence does not support that conclusion.
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2005-12-10]
A look back at the best from a year ago.
Requirements / Requirements gathering / Software development
Posted on:
Prototype Fidelity
Prototyping is invaluable for getting feedback on a design. It is also great for getting validation of requirements. It can even be used as a means to document the requirements. What level of fidelity should be used when getting feedback? Jan Miksovsky provides some guidance from the real world.
CMMI / Process Improvement / Software development
Posted on:
Software Product Delivery – 20 Rules?
Rishikesh Tembe shared twenty rules for software product delivery last month. His rules are from the perspective of a former software developer. Some we like. Some, not so much.
Business Analysis / Requirements / Requirements gathering
Posted on:
Idea Seeding Better Than Brainstorming
Kevin Cheng and Tom Chi, at OK/Cancel have written an article sharing the creative process they use for creating their awesome strips. Idea seeding is the process where they use time constraints and design/refine cycles to improve their ability to create quality “product.” They also wonder about extending this approach to other areas where brainstorming is normally used.
Process Improvement / Requirements / Software development
Posted on:
Software Silver Bullet
“I believe the hard part of building software to be the specification, design, and testing of this conceptual construct,[…] If this is true, building software will always be hard. There is inherently no silver bullet.” – Frederick P. Brooks, Jr. 1987
Communication / Requirements / Writing
Posted on:
Logical Requirements
We talk about characteristics of good requirements, including completeness, correctness, and ambiguity. But how do we assure that our requirements are complete, correct, and unambiguous? Simple, Captain, with logic.
Foundation series / Requirements / Requirements gathering
Posted on:
Foundation Series: JAD Sessions
JAD is an acronym that stands for Joint Application Design. JAD sessions are collaborative meetings where the customers meet with developers to determine what the product needs to be or do.