Is the current usage of MVP in context with other levels of "done"?

I have seen 2 definitions of done in agile systems:

   - Done for a user story is defined by acceptance criteria and is a bit
   more discrete
   - Done on a system/product level is more nuanced and managed at the org
   level.


Clinton Keith spoke at 2 of my previous organizations and described the
latter in detail.
BTW I really like his book on agile for games
<http://www.amazon.com/Agile-Development-Addison-Wesley-Signature-Series/dp/0321618521>

Having levels of done for a feature or organization encourages early
working prototypes. It also helps communicate final shippable products.

Keith claimed that Bioware used to use a scale something like this (I'm
summarizing from memory):

   - Prototype - pretty straight forward definition
   - Vertical slice - game specific step similar to a tracer round
   <http://www.requirementally.com/agile-dictionary-tracer-bullet/>
   - first playable - the first time a lay person can easily play and
   comment on a product
   - MVP - truly MVP, barely consumable by users
   - Competitive - meets or slightly exceeds competitors
   - BATMAN  - yes, all caps. this should be so cool it makes your head
   explode!



At Kixeye we, adopted something close to Bioware's version.

At Zynga, I had varying definitions depending on the game team but they
were on a similar scale.


At another company, I worked with execs and leads to establish these levels
of done:

   - Prototype - pretty straight forward
   - Alpha - the dev team and PO can sort of use it. It takes a lot of
   effort and possibly some dev tools
   - Beta - non-technical beta users can use it and give valuable feedback
   - MVP - truly MVP, barely consumable by users
   - MCP - Minimum Competitive Product


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.




On Mon, Jun 15, 2015 at 9:49 AM, Grace Gellerman <ggeller...@wikimedia.org>
wrote:

> +1 to what Max said.
>
> MVP is an industry standard.
>
> On Mon, Jun 15, 2015 at 9:23 AM, Max Binder <mbin...@wikimedia.org> wrote:
>
>> 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.
>>
>>
>> On Mon, Jun 15, 2015 at 9:14 AM, James Douglas <jdoug...@wikimedia.org>
>> wrote:
>>
>>> Joking aside, I'm not too concerned with the overloadedness of terms we
>>> use, as long as we have consensus on what they mean.
>>>
>>> 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".
>>>
>>> On Mon, Jun 15, 2015 at 9:10 AM, James Douglas <jdoug...@wikimedia.org>
>>> wrote:
>>>
>>>> Model View Presenter? :]
>>>>
>>>> On Mon, Jun 15, 2015 at 9:07 AM, Kevin Smith <ksm...@wikimedia.org>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> 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).
>>>>>
>>>>> Am I alone in preferring an acronym that isn't overloaded?
>>>>>
>>>>>
>>>>> Kevin Smith
>>>>> Agile Coach
>>>>> Wikimedia Foundation
>>>>>
>>>>>
>>>>>
>>>>> *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.*
>>>>>
>>>>> _______________________________________________
>>>>> teampractices mailing list
>>>>> teampractices@lists.wikimedia.org
>>>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> teampractices mailing list
>>> teampractices@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>
>>>
>>
>> _______________________________________________
>> teampractices mailing list
>> teampractices@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>
>>
>
> _______________________________________________
> teampractices mailing list
> teampractices@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
_______________________________________________
teampractices mailing list
teampractices@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/teampractices

Reply via email to