Here's a thought In the context of a POD or SQUAD or a SOFTWARE TEAM a. A solution must be marketable, profitable, and affordable by the organization that creates it. Product manager should represent the Financial dimension of the product and help teams understand what will be viable. They contribute primarily by determining backlog priority for all work (e.g.) eng sustaining work, and new feature work). b. A solution must be desirable, usable, and useful. Design should represent the Usage dimension and help teams understand what will be usable. They contribute primarily by uncovering user needs in the opportunity space, visualizing concepts, and aligning user outcomes to the desired business targets. c. A solution must be buildable, functional, and consumable by its stack, integration partner environments, and according to ethical policies. Engineers should represent the Technology dimension and help teams understand what will be feasible. They contribute primarily by delivering production experiences. Together, if working in balance, the three should create value for all stakeholders. I believe the best diagrams show value creation at the center. And, it's important to note that ALL of these roles have related disciplines that contribute at a super squad level, but generally are not embedded.
![BabyChiefDoit - Wonderful Time (Official Music Video) [Shot By @Rxllo]](http://i.ytimg.com/vi/_Bfqt3zV2KE/mqdefault.jpg)
Finally, Sachin you're changing people lives! You should move into video ! Keep it up !
Thank you so much, Sachin Sir. 😀
Thank you Sachin. You have been sharing great stuffs from years, great to see you delving into video podcasts. Will be listening religiously. 😃
Here's a thought
In the context of a POD or SQUAD or a SOFTWARE TEAM
a. A solution must be marketable, profitable, and affordable by the organization that creates it. Product manager should represent the Financial dimension of the product and help teams understand what will be viable. They contribute primarily by determining backlog priority for all work (e.g.) eng sustaining work, and new feature work).
b. A solution must be desirable, usable, and useful. Design should represent the Usage dimension and help teams understand what will be usable. They contribute primarily by uncovering user needs in the opportunity space, visualizing concepts, and aligning user outcomes to the desired business targets.
c. A solution must be buildable, functional, and consumable by its stack, integration partner environments, and according to ethical policies. Engineers should represent the Technology dimension and help teams understand what will be feasible. They contribute primarily by delivering production experiences.
Together, if working in balance, the three should create value for all stakeholders. I believe the best diagrams show value creation at the center. And, it's important to note that ALL of these roles have related disciplines that contribute at a super squad level, but generally are not embedded.
I learned something new
I'm a Computer Science Engineer and new to the product management domain, what is the future of it with AI in the picture?
14:28 tl;dr