You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

How To Prioritize A New Product Request

impact

  • how many customers will use it?
  • how often will customers use it?
  • what is the approximate cost to license?
    • what is the funding source?
  • are there viable distribution mechanisms?
  • what is the support expectation? 
    • are we resources correctly for the SLA?

requestor

  • who is making the request?
  • is the product in keeping with MITs mission?

risk

  • are there other alternatives currently offered?
  • are there other alternatives on the market that deserve investigation?
  • is the product in keeping with IS&Ts business model?
    • will it help move MIT forward in terms of value to the community?

 

Low Priority

Moderate Priority

High Priority

Requester

  • an individual staff or student
  • a small group of users (<20)
  • faculty
  • VIP staff and faculty
  • large student organization
  • entire department, lab or center

Impact to the MIT Community

  • users do not intend to use the product that often (<once per week)
  •  purpose is specifically for one class
  • very specific purpose, not a flexible tool that can meet a variety of needs
  • potential for expanded user base over time
  • will be used on an ongoing basis

Risk To IS&T




  • No labels