Exercise - Techniques

The MoSCoW technique prioritizes requirements by allocating an appropriate priority expressed in the following terms:
  • Must have
  • Should have
  • Could have
  • Would like to have in the future

Requirements defined as “Must have” and “Should have” should be implemented correctly or the solution will be rejected. “Could have” requirements are not necessary to satisfy the business needs established for the project, but increase delivery satisfaction. Requirements marked as “Would like to have” are less important, and considered as non-crucial needs that can be planned in the future and are not necessary now.

Consider the following list of expressed user needs for the new CRM system:

1. The application must support importing existing contact data in ASCII format (comma or tab delimited). The import process must be easy to use by a user with basic computer skills.

2. The application must have seamless integration between calendar scheduling functions and contact management functions.

3. The application must have integration with MS Word and the user’s default e-mail application. The integration must allow users to compose mail merge letters and group e-mail, sent to selected recipients in the application’s contact database. The application must allow contacts to be selected for e-mail or merging by category.

4. The application must be able to create and maintain up to 50 categories of contacts, which can be defined by each individual user.

5. Contact information must be able to contain common information as well as user-defined information.

6. Calendar functions must accommodate years between 1900 and 2100.

7. Users must be able to schedule appointments and link them to selected individuals in the address book.

8. Users must be able to set alarms for specific appointments. Alarms must be user-defined in terms of minutes before an appointment.

9. Users must be able to enter and maintain a list of tasks (e.g., a to-do list) and link those tasks to specific contacts.

10. Users must be able to dial the phone number of a contact through the application.

11. Users must be able to print contact information, appointments, calendars and to-do lists.

12. Users must be able to search contacts, appointments and to-do lists.

13. Users must be able to carry over unfinished To Do items from previous days.

14. The application must have ability to allow users to sync information with the cloud version of the application.

15. A web-based version of the application must be available to allow remote collaboration.

Apply the MoSCoW technique to prioritize them.

Last modified: Thursday, 1 May 2014, 2:02 PM