...
- 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 | Work can be done generally be done by an INDIVIDUAL staff member or equivalent, within the context of existing assignments and responsibilities; no separate budgeting and resource allocation is usually done for this level; time is usually measured in DAYS
| Usually confined to a single TEAM with contacts into other parts of the organization and into business stakeholder groups; formal resource allocation is often involved, and an ad-hoc release team may be formed; projects in this category may involve software licenses and other materials and services budget items; time is usually measured in WEEKS
| May involve an entire ORGANIZATION of project teams, release teams, and transition teams, staff in many parts of the organizations, consultants, formal budgets usually accounted for as part of IS&T’s central budgeting process, significant licensing, materials and services, and capital budgets; time is usually measured in MONTHS or YEARS
|
Impact to the MIT Community |
|
|
|
Risk To IS&T | LOW impact confined to behind the scenes, internal areas of IS&T, and business support groups; little to no customer-facing impact
| LOCAL or bounded to small group, roles, or department; group of customers of service offering or product, while it may be significant in size, is usually within a specific domain with well-established communications channels; we know who uses product or service offering and how they will react to changes
| WIDE impact to large segments of the MIT community, often with incomplete understanding of precise impact and user base, and without complete communication channels into community segments; customers often rely on affected products and service offerings for their day-to-day work
|