Schneider Electric - Franklin, TN
posted 4 months ago
We are currently seeking a Technical Product Owner (TPO) to join our Digital Power organization focused on energy management and automation software along with hardware products that support the Digital Power business. The TPO will be focused mainly on the software and systems business but will be interacting with teams on hardware devices as well. The TPO will be responsible for leading a team of developers for a particular mission within the software platform. The TPO will focus on requirements definition translating business requirements to technical requirements to efficiently drive the development team. They will work closely with business owners, technical architects & system architects several product increments ahead to perform requirements discovery. The TPO will be working with developers to clearly communicate functional and non-functional requirements. The TPO will be the orchestrator of the backlog and work with stakeholders on work estimates and prioritization. The role involves leading and managing requirements development and analysis activities by working with stakeholders, developers, UX designers, QA analysts, and internal/external customers. The TPO will conduct gap analysis between application and stated customer requirements, collaborating with Architects and Developers to estimate project impact. They will work with the Offer Technical Lead to support the development of project plans, schedules, and resource needs. The TPO will support the squads on work decomposition, sequencing, and effort sizing, ensuring that risks are identified and communicated along with created actions for mitigation. Additionally, the TPO will lead the development team during design specification creation (Definition of Done) and utilize customer knowledge of power management systems to ensure consistent feature development across market segments such as Data Center, Industrial, and Healthcare. The TPO will leverage Agile framework and mindset in the offer creation process and document detailed functional & non-functional requirements, user stories, and acceptance criteria.