MDN/Projects/Development/Videos

If a picture is worth a thousand words, then surely a moving picture is worth a million words.

There are already several cases in which we are using videos to inform, to educate, and to advocate about the open Web (as well as Mozilla technologies like Firefox OS). However, each instance of this has to date been treated as a one-off, with videos placed on video hosting sites such as YouTube. We should have a standardized plan for managing these videos.

Note: This page is a work in progress; I will be trying to write it using the MoSCoW method.

Must haves

These items are absolutely critical. Must-have items should be treated as the absolute minimum viable product; if any one of the items in this section is not in the finished product, the project is considered a failure.

Should haves

Features considered "should haves" are those which, while still as important functionally as those in the must have list, can be delayed slightly in order to achieve a minimum viable product on schedule, and/or have workarounds that enable the product to be used without them for a short time until the features can be built as a follow-up to the initial launch.

Could haves

Those items on this list are less important than the features in the prior groups, but would be nice to have. These are often items that can add significant usability gains for marginal development cost.

Won't haves

These are items or capabilities that are outside the scope of this project, at least for the time being. They may in fact be functions we do wish to have, but they are the lowest-priority items, and should therefore be the first things to go if things have to be dropped in order to meet the project schedule. This list can also include genuinely low-priority or low-impact ideas.