Product Management Acceptance

69 deploy-product-management

As a part of the release process, the experience is validated one last time to ensure that it gets approval from Product Management. This validation helps ensure that the value-driven objectives have been successfully achieved and are ready for deployment to production.

Explore More.

Related Mindset:

Continuous Delivery





A deployed experience within the staging environment


A validated experience which has passed the Product Management portion of the release process validation

Product Management Acceptance is a key step in the release management process.

Product Management is one of the key pieces of the Release Management team. A part of their overall responsibility is to ensure that they have validated the experience against the objectives that were agreed to during the PI Planning Session. If the process has been followed correctly, Product Management has seen this work through both the Sprint and Systems Demos. This final level of validation should be focused around validating the overall experience fully integrated within the staging environment.

Common Pitfalls

If significant changes arise through this validation, there are multiple systemic problems for the organization. These problems may be due to one or more of the following:

  • Delaying all validation until the release process: While this final validation is a needed step in the release process, it should not be the only point at which it is validated. Through the PI Planning event and the role of product owners within the Scrum teams, validation should occur throughout the process, from the Program segment through Deploy. Significant changes within the Deploy segment are costly, both in terms of money and time.
  • Product Owners out of sync with product management: One systemic problem can be tied to a disconnect between Product Management at the Program and Portfolio levels, from Product Owners on the scrum teams. While these individuals operate within different segments, there must be an ongoing conversation between these individuals to ensure this separation does not occur.
  • Incomplete participation in Sprint and System Demos: Another systemic problem can be tied to participation at key events. This includes Sprint Demos, Systems Demos, and also the PI Planning Event. Product Management will play a key role in all of these. Without the participation, fixes will be much more costly for the organization.