Communication Path
Communication paths for product changes and emergencies,…
- When do the owner, stakeholders, employees and students need to be notified?
- Path for back end issue - upgrades, bugs, ...
- Path for Interface issue - upgrades, bugs, ...
- Emergencies (major, minor)
|
|
Product Owner
The person who can make the ultimate decisions for the product - funding, road map, vision, governance and retirement.
- Please include name, email, phone, job title.
|
|
Stakeholders
A person or group of people who have an interest in the product and its success. Can influence product decisions. Are impacted (directly or indirectly) by the product. e.g. requester, department, developer, ASE, portfolio manager, product manager
- Please include name, email, phone, job title.
|
|
Audience
Who will use the product? (campus, online, pathway, Ensign, employees - more specific like - nursing students, specific department or course(s))
|
|
|
Purchasing
- Purchaser and requester information - name, email, phone
- Licensing (description of the license agreement - site license, per user, per computer, ...)
- How is the license renewed?
- Next renewal date?
- When should this product be reviewed again for purpose and outcome? Usually, this happens every 3-5 years.
- BYUI Purchasing Agent - name, email, phone
|
|
Other
- Product documentation (URL)
- Support and/or training documentation (URL)
- ASE - maintenance needs and yearly maintenance estimate
- Any custom code developed? (where can it be found)
- Is this ADA compliant (URL to their official vendor statement)
- Other
|
|
Data
- Give description of all data and how it interacts with the university systems.
- List all university systems used.
- Installation instructions - URL or direction how to find the instructions.
- Who is responsible for installation - please include email, phone, job title.
|
|