I thing PM skills could be divided in 5 groups. – Kanban and Sprint Fundamentals (understand how product is developed) – How to make estimations and who to involve – Setting Up Analytics for Product with GA and GTM – Business Acumen (Product must understand the business he/she operates in) – Understand technical skills depending on product stack For these 5 groups we can add skills on the go depending on the project that product manager is working on.

Hey @irina_seng! I pursue the same goal, good luck on our path! I think the biggest questions people may get here is: is it obligatory for Product Managers to know how to write code and to what extent? So far I am concerned that this is a must for one simple reason: users usually want a lot of different stuff to be added in the product, and as a PM, you need to develop a good understanding of at what cost this or that thing can be implemented. One could rely on a lead developer to help with prioritizing features, but I think this skill is included in a "must-have" set for many teams as expectation for their Product Managers. This also answers the "to what extent" question. You should know enough to not require the assistance of your developers to answer the questions: "How long would this feature take to develop?" and "How exactly we could implement this?".