tag:blogger.com,1999:blog-7879107.post112837917065587322..comments2023-12-08T01:42:31.590-06:00Comments on Cauvin: "Delivering Product"Roger L. Cauvinhttp://www.blogger.com/profile/08969779835314260680noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7879107.post-67906934303358348412014-11-20T11:17:02.058-06:002014-11-20T11:17:02.058-06:00Exactly. Learning and nimble adjustments based on ...Exactly. Learning and nimble adjustments based on what's learned.<br /><br />As I mentioned in the <a href="http://blog.cauvin.org/2005/06/agile-product-management.html" rel="nofollow">previous blog entry, Agile Product Management</a> 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 <i>avoid</i>, not just problems to solve).<br /><br />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.<br /><br />With lean startup methods, we cast a wider net: a learning loop that encompasses the entire product strategy (including marketing and sales).Roger L. Cauvinhttps://www.blogger.com/profile/08969779835314260680noreply@blogger.comtag:blogger.com,1999:blog-7879107.post-13069919957098047912014-11-20T09:52:15.358-06:002014-11-20T09:52:15.358-06:00The key here is that you deliver something which e...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.<br /><br />Regardless, the litmus test is - did you learn something which caused you to change what you're doing (or how you're doing it)?Scott Sehlhorsthttps://www.blogger.com/profile/07371365690039840768noreply@blogger.com