Stakeholders and Product Owners
The following table records who our our key contact people and stakeholders are. It is intended to help identity who could be considered a product owner. A product owner is the voice of the customer, must ensure that the team delivers value to the business, must be a good communicator (out to other stakeholders and into the team). Their responsibilities include:
- Defining the features of the application.
- Prioritizing features of the application.
- Adjusting the features and priority as needed after each sprint or iteration.
- Accepting or rejecting work results.
- Keeping customers or users apprised of status and getting their feedback.
Some general thoughts:
- Given the breadth of WIP II this has been broken down by HLS area and sometimes more categories under these.
- For Faculty and School lets try to identify a faculty contact for now (to make the numbers more manageable), while retaining the option to move to school level contacts when we start working with each area.
- The contact person is intended to record the name and location/position of the best contact person we currently have (i.e. existing contact/relationship) for an areas, not necessarily every content editor.
- People can be listed more than once (later on we may produce another version of this oriented around the person)
- The current or best level for a contact person can differ (e.g. sometimes at faculty level and sometimes at school)
- Other stakeholders refer to (the name and location/position of) other people that ought to be consulted during WIP II work, especially if they are more suitable for the product owner role.
- For both the contact person and other stakeholder columns:
- If the person is suitable to be a product owner (definition below) place (PO) after their name.
- If the person is suitable to be on a reference group (probably of various product owners) place (RG) after their name
- Feel free to make any other changes or suggestions, as this approach is really only a suggestion to kick start the process.
Area | Sub area | Contact person | Other stakeholders |
---|---|---|---|
Course and subject information | Courses | ||
Subjects | |||
Programmes | |||
Staff information (currently out of scope but important) | |||
Faculty and school sites | Architecture and Design (2 schools) | ||
Education (2 schools) | |||
Engineering (1 school) | |||
Graduate Research (n/a) | |||
Humanities and Social Sciences (12 schools) | |||
Law (n/a) | |||
Science (5 schools) | |||
Toihuarewa (n/a) | |||
Victoria Business School (6 schools) | |||
Postgraduate information | |||
Research centres, institutes and chairs | |||
Student information | Related to learning | ||
Supporting student services | |||
Other | Strategy and planning | ||
Eduction, including training | |||
Reporting and analytics | |||
Project governance |