Defining a product is a crucial when adopting Agile Product Operating Model (APOM) and replaces project as the fundamental unit of delivery.
Defining a product is complex for IT organizations with external or internal products.
Power, authority, and status impact how products were defined, so existing power and political dynamics need to be considered when defining the product model.
Another interesting topic that came up was whether or not a database used in many external and internal products should be considered a product in and of itself.
It is clear that this team's work provides value, has a boundary, and has encapsulated its services and features.
By showing clear accountabilities, stakeholders will know who does what, making governance and flow smoother.
The most exciting area of opportunity is whether this product provides a strategic advantage, and if so, it should be managed accordingly.
Moving from project to product requires looking at strategy, opportunity and legacy before deciding on the model.
As you move from project to product, you cannot take existing projects or initiatives and make them products.
The impact of the model on people's positions, authority or status must also be considered.