<div dir="ltr"><div>Is the current usage of MVP in context with other levels of "done"? <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I have seen 2 definitions of done in agile systems:</div><div class="gmail_extra"><ul><li>Done for a user story is defined by acceptance criteria and is a bit more discrete<br></li><li>Done on a system/product level is more nuanced and managed at the org level.<br></li></ul></div><div class="gmail_extra"><br></div><div class="gmail_extra">Clinton Keith spoke at 2 of my previous organizations and described the latter in detail.</div><div class="gmail_extra">BTW I really like his book on <a href="http://www.amazon.com/Agile-Development-Addison-Wesley-Signature-Series/dp/0321618521">agile for games</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">Having levels of done for a feature or organization encourages early working prototypes. It also helps communicate final shippable products. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Keith claimed that Bioware used to use a scale something like this (I'm summarizing from memory):</div><div class="gmail_extra"><ul><li>Prototype - pretty straight forward definition<br></li><li>Vertical slice - game specific step similar to a <a href="http://www.requirementally.com/agile-dictionary-tracer-bullet/">tracer round</a><br></li><li>first playable - the first time a lay person can easily play and comment on a product<br></li><li>MVP - truly MVP, barely consumable by users<br></li><li>Competitive - meets or slightly exceeds competitors<br></li><li>BATMAN - yes, all caps. this should be so cool it makes your head explode!<br></li></ul></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">At Kixeye we, adopted something close to Bioware's version. </div><div class="gmail_extra"><br></div><div class="gmail_extra">At Zynga, I had varying definitions depending on the game team but they were on a similar scale. </div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">At another company, I worked with execs and leads to establish these levels of done:</div><div class="gmail_extra"><ul><li>Prototype - pretty straight forward<br></li><li>Alpha - the dev team and PO can sort of use it. It takes a lot of effort and possibly some dev tools<br></li><li>Beta - non-technical beta users can use it and give valuable feedback<br></li><li>MVP - truly MVP, barely consumable by users<br></li><li>MCP - Minimum Competitive Product<br></li></ul><div><br></div></div><div class="gmail_extra">Keith stressed that an organization should define this on their own. The scale should be tied to examples of previous work. The org should also have fun with it and come up with some of their own terms. </div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 15, 2015 at 9:49 AM, Grace Gellerman <span dir="ltr"><<a href="mailto:ggellerman@wikimedia.org" target="_blank">ggellerman@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 to what Max said.<div><br></div><div>MVP is an industry standard.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 15, 2015 at 9:23 AM, Max Binder <span dir="ltr"><<a href="mailto:mbinder@wikimedia.org" target="_blank">mbinder@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">FWIW, in my (limited) experience, MVP is an industry term widely used, and I haven't encountered MMP. There is something to be said for unified industry lingo.<div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 15, 2015 at 9:14 AM, James Douglas <span dir="ltr"><<a href="mailto:jdouglas@wikimedia.org" target="_blank">jdouglas@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Joking aside, I'm not too concerned with the overloadedness of terms we use, as long as we have consensus on what they mean.<br><br></div>I'd be much more excited to define the thing that we're designating as MMP, i.e. "the bundle of features that satisfy user stories X, Y, and Z".<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 15, 2015 at 9:10 AM, James Douglas <span dir="ltr"><<a href="mailto:jdouglas@wikimedia.org" target="_blank">jdouglas@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Model View Presenter? :]<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Mon, Jun 15, 2015 at 9:07 AM, Kevin Smith <span dir="ltr"><<a href="mailto:ksmith@wikimedia.org" target="_blank">ksmith@wikimedia.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div>Hi all,<br><br></div>Kind of a small issue, but I find myself leaning toward MMP (Minimum Marketable Product) rather than MVP (Minimum Viable Product). Although I prefer "viable", and MVP is catchy, it is also confusing and ambiguous, thanks to MVP (Most Valuable Player). <br><br></div>Am I alone in preferring an acronym that isn't overloaded? <br><br clear="all"><div><div><div><div><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><br>Kevin Smith<br>Agile Coach<br>Wikimedia Foundation<br><br></font></span><br><font><font><i><font color="#888888">Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Help us make it a reality.<br></font></i></font></font></div></div></div></div></div></div></div>
</div></div></div></div></div>
<br></div></div><span>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>