Product Ownership¶
The Product Owner (PO) for the TUMI datahub plays a pivotal role in shaping and managing the development of the platform to meet user needs and objectives. The PO is the face of the TUMI datahub to stakeholders and cares about "his/her product".
The main responsibilities of the PO are:
User Needs Analysis / SEO¶
The PO must continually gather feedback from users, stakeholders, and the community to understand their needs and expectations. This involves conducting surveys, interviews, and data analysis to identify requirements and prioritize features accordingly. The PO uses web analytics by Matomo to get insights about how users are using the TUMI datahub.
To start Web analytics:
Visit https://analytics.<my-city>.tumidata.org.
The PO plays a crucial role in optimizing the open data portal for search engines (SEO) to enhance discoverability and visibility. The aspects of SEO responsibilities cover Content Quality, external Harvesting, metadata optimization or sitemap submission to search engines (e.g. using Google Search Console).
Organizing Support¶
The PO is also responsible for organizing support. This encompasses establishing channels, crafting comprehensive documentation, offering training sessions, managing support teams, and monitoring support performance. the PO ensures users have access to resources and assistance, actively collect feedback, and foster user communities. By prioritizing user satisfaction and resolving issues efficiently, the Product Owner contributes to a positive user experience and continuous improvement of the open data portal.
Feature Prioritization¶
Based on user input and organizational goals, the PO is responsible for creating and maintaining a prioritized backlog of features and improvements. They must make informed decisions about which features should be developed next, considering factors like user value, impact, and technical feasibility. There are two types of features to handle:
- Data requests from users
- Feature requests from the data managers or users
Roadmap Planning¶
Developing a clear and achievable product roadmap that outlines the short-term and long-term vision for the open data portal. This involves setting strategic goals, defining milestones, and aligning development efforts with the overall mission of the portal.
Stakeholder Communication¶
The PO acts as a liaison between various stakeholders, including city administration, data providers, hosting and development partner GIZ and end-users. The PO ensures that everyone involved in the project is well-informed about the product's direction, progress, and any changes in requirements.
Iterative Development¶
Embracing an agile development approach, the PO collaborates closely with the development team to define user stories, clarify requirements, and provide continuous feedback. They must be available to answer questions, make quick decisions, and adapt to changing priorities as the project evolves.
in TUMI datahubs the development is originally done by GIZ but local development efforts can join to make the TUMI datahubs richer and better tailored to the requirements.
In summary, a PO for an open data portal is responsible for understanding user needs, setting priorities, defining the product vision, facilitating communication, and ensuring that the development process aligns with the portal's goals and objectives.