Loading...

MoSCoW for Requirement Prioritization

4,238 views

Loading...

Loading...

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Oct 18, 2014

Enroll at iZenBridge Online PMI-PBA® course
http://www.izenbridge.com/pmi-pba/onl...

Become a part of the latest discussions on PMI-PBA® Training, and PMI-PBA® Exam http://forum.izenbridge.com/viewforum...

The video covers, explanation of four Requirement Categorization:
o Must Have Features: Must Have features forms the minimum scope for the product to be useful and must be added before the product is launched.

o Should Have Features: The Should have features are not essential for the product launching but gives high value to the user and considered to be important. A good mix of Must Have and Should Have featured is a good idea where all the Must Have features are available. The priority of 'Should Have' features is determined from the Must Have Features. For example, some Must Have features need Should Have features to work well.

o Could Have Features: These are nice to have features, and these will be the first features to be removed from the scope if there is time or money constraints.

o Won’t Have Features: These features requested initially but excluded from the current scope and may be included in a future phase of development

Do drop us a comment /feedback so that we can bring more learning videos and presentation
to you.

Loading...

When autoplay is enabled, a suggested video will automatically play next.

Up next


to add this to Watch Later

Add to

Loading playlists...