What Product Owner need to understand is technical debt
Generally teams take on different types of work that is
- building new features and fixing broken features that are product related. PO ideally want only new features and begrudgingly accepts defects.
- fixing poor code, outdated code that is hampering and slowing the team down in building value to the product. Developers feel they are working on 'bad' code and find new work demotivating as they have to work through pains. This is tech debt its best and Product Owners struggle to recognize this and see the importance.
- practice and build improvements. Introducing ALM tooling, build pipelines, automated testing take significant effort and much more than most people realize. Teams spend months on this. Product Owners don't realize that this takes work to customize for their product as they expect it to work out the box. The reality it's not plug and play and takes effort.
PO needs some education on technical debt and building products in an agile way.
The team should also start pushing back and as SM, highlight the fact the collective wisdom of the professionals and their right to choose the "best how" approach must be respected.
- building new features and fixing broken features that are product related. PO ideally want only new features and begrudgingly accepts defects.
- fixing poor code, outdated code that is hampering and slowing the team down in building value to the product. Developers feel they are working on 'bad' code and find new work demotivating as they have to work through pains. This is tech debt its best and Product Owners struggle to recognize this and see the importance.
- practice and build improvements. Introducing ALM tooling, build pipelines, automated testing take significant effort and much more than most people realize. Teams spend months on this. Product Owners don't realize that this takes work to customize for their product as they expect it to work out the box. The reality it's not plug and play and takes effort.
PO needs some education on technical debt and building products in an agile way.
The team should also start pushing back and as SM, highlight the fact the collective wisdom of the professionals and their right to choose the "best how" approach must be respected.
Comments
Post a Comment