Research And Evaluate A Suitable Company
Apply MoSCoW to arrange the duties based on priorities of the task
the categories are typically understood as:
Requirements labeled as Must have are critical to the current delivery time box in order for it to be a success. If even one Must haverequirement is not included, the project delivery should be considered a failure (note: requirements can be downgraded from Must have, by agreement with all relevant stakeholders; for example, when new requirements are deemed more important). MUST can also be considered an acronym for the Minimum Usable SubseT.
Requirements labeled as Should have are important but not necessary for delivery in the current delivery timebox. While Should haverequirements can be as important as Must have, they are often not as time-critical or there may be another way to satisfy the requirement, so that it can be held back until a future delivery time box.
Requirements labeled as could have are desirable but not necessary, and could improve user experience or customer satisfaction for little development cost. These will typically be included if time and resources permit.
Won’t have (this time)
Requirements labeled as won’t have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, won’t have requirements are not planned into the schedule for the next delivery time box. Won’t haverequirements are either dropped or reconsidered for inclusion in a later time box. (Note: occasionally the term would like to have is used; however, that usage is incorrect, as this last priority is clearly stating something is outside the scope of delivery).