I have been working in the DS field for several years and have worked with good POs and bad POs.
The good POs:
- Kept us on track to meet goals. Data scientists have a tendency to hole themselves up for weeks pursuing vast research goals. It is important to have regular and frequent checkins and achievable intermediate goals.
- Communicate findings, eta, objectives, SLAs, etc up and down the org. You don't have to be a statistical expert. But a good DS PO trusts us and works with us to compromise and find out how to get a MVP feature/product out the door.
Also, I've been cataloguing and mining a lot of online learning content links and extracting skills so this question interests me. Here are the resources that I can find when cross checking data science and project management:
- https://www.linkedin.com/learning/learning-data-science-using-agile-methodology
- https://www.coursera.org/learn/executive-data-science-capstone
- https://www.edx.org/course/data-science-method
- https://www.udacity.com/course/data-product-manager-nanodegree--nd030
Some of these are free some are not. I hope they help!