[Ho Chi Minh] Technical Product Owner

Role OverviewThe Technical Product Owner (TPO) for Platform/Common Services is a critical, bridge-building role responsible for driving the adoption, utilization, and enhancement of the enterprise-standard tools and technologies (COM services) across multiple Scrum teams. This role acts as the key liaison between the Architect Committee Subset (ACS) / Solution Architects (SAs) and the Scrum Team Proxy Product Owners (PPOs) to ensure technical governance aligns with business value delivery.Key Responsibilities1. Enterprise Tool Adoption & Technical NurturingFacilitate Technical Understanding: Collaborate closely with Solution Architects (SAs) and the ACS to ensure all Scrum teams (PPOs) fully understand the value, capabilities, and business applications of the enterprise-standard tools.Promote Governance & Consistency: Actively promote and facilitate the adoption of enterprise-standard tools and technologies to enhance consistency and efficiency across all teams.Track & Report Utilization: Partner with SAs to gather and distribute regular Business Utilization Reports (bi-weekly) for key common tools (e.g., DG/Data Modeling Appliance, Workflow, DAP, OCR, Operational Report, Notification) to the PPO community.Support & Training Coordination: Coordinate ACS/SA-led training sessions for Technical Architects (TAs) and serve as a first point of contact to gather and escalate technical matters to SAs when PPOs lack technical understanding.Technical PoC Support: Assist the ACS team by following up on technical Proof-of-Concepts (PoCs) and tasks, particularly in generating reporting and sharing documentation.2. Common Service Enhancement & Business ValueDrive Service Adoption: Follow up on the common services adoption rate and increase awareness through organized sharing sessions with Scrum teams.Gather & Prioritize Use Cases: Gather real business use cases from development teams and propose scalable enhancements to improve existing features or introduce new ones.Optimize Business Utilization: Collect business use cases and track progress against a checklist to enhance the overall Business Utilization Ratio of COM services.Strategic Opportunity Identification: Proactively check each team's business flow to identify potential use cases where enterprise tools can be applied, thereby adding value and efficiency.Collaborate for Buy-in: Work with Program Management to involve key stakeholders and enhance team awareness and collaboration regarding COM services adoption.